Page 1 of 1

Mutiple .post.res files

Posted: Thu Oct 20, 2022 8:21 pm
by augustobopsinborges
Hello there!

I'm working with a pre-existent F.E. code and we use GiD for pre- and post-processing (GiD 14.*).

The last collegue working on this code has written it so that multiple .post.res files are generated during analysis (all files have the same information, changing only the results for the respective time step). One file named '<model's_name>.post.res' is generated with the final results and during the analysis several files with an ordering name (e.g. 00001.post.res, 00002.post.res, and so on) are generated.

I can easily open the post-processing results from '<model's_name>.post.res', even automatically by switching to postprecess environment, but not from the others. I have tried different approached, but I just can't find a way.

I would like to know how can I open those multiple .post.res files, in order to see the multiple time steps recorded. Can you help me?

Re: Mutiple .post.res files

Posted: Fri Oct 21, 2022 10:08 am
by escolano
You can open several files in post with the menu
Files->Open multiple
and select the files you want

and it is possible to write by the solver a file <modelname>.post.lst
with the list of files to be read (and then swapping from pre to post will load automatically all results)
https://gidsimulation.atlassian.net/wik ... e.post.lst

Re: Mutiple .post.res files

Posted: Tue Mar 12, 2024 7:48 pm
by Daniel
Hi.

I am having the same problem. I have written multiple .post.res files and also the .post.lst file like this:
Multiple
mesh_1.post.res
mesh_2.post.res
...
and so on. However, GiD gives a message like "couldn't find mesh_1.post.res.msh" for every file in .post.lst.
I appreciate any help.

Re: Mutiple .post.res files

Posted: Wed Mar 13, 2024 1:08 pm
by escolano
And where are you defining the mesh where the result must be represented?
It is defined in preprocess (<modelname>.msh) and used also for postprocess?
or it is stored in one or more additional files in postprocess? or is stored inside the same files as the results?
then maybe you must add these postprocess mesh files to the collection of names of the .post.lst file

Maybe you can attach a zip with a small example