GiD forum

Thank you for your detailed explanations. We are interested in the description of the .geo-file because usually we are not using GiD as a preprocessor. GiD uses even for very simple geometries trimmed surfaces. From the computational point of view trimmed NURBS surfaces have a few disadvantages, so ...

Hello, we have take an brief look into the isogeometric post-procesing. Is there any documentation about the .geo file? If we refine the Nurbs description in our FE code we have to write the files ourselves, we assume. Is there also a possibility (or plans) to visualize stresses, i.e. gauss point re...

Thank you!!
It now works with verison 12.1.5d.

Regards
Malte

Thanks for your help.
Attached is the complete project directory, including the binary result file.

Thank you for the reply! We have no changed the extension of he binmary output file to *.post.res, but still it does not work: The output file <modelname>.post.res exists inside the GiD project directory and when I toggle to postprocess I get the following outoput in GiD: Initializing postprocess......

Hi, when changing to postprocessing, GiD tries to find and open the postprocess information for the current project. But only the *.post.res file is considered. I am using binary format in a *.post.bin file and get an error message: Results file ...\...\...\Platte.gid\Platte.post.res' not found No r...

Hello Jorge,

thank you very much for your quick bug fix.
To me it seems like both issues are resolved now.

Regards
Malte

We know that the memory lost is only a few bytes, but we are trying to get a clean valgrind output for our own code to be able to detect memory problems more easily. Doing so we found the small leak in GiDpost.

Thanks a lot for fixing this. Looking forward to the new version.
Malte

Hello, we assume that there is a small memory leak in the GiDpost library in the context of opening and closing the ASCII files. Valgrind's leak-check reports two lost blocks: 48 bytes in 1 blocks are definitely lost in loss record 1 of 2 at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck...

Hi,

the latest version of the fixed GiDpost (2.3) still contains some output to standard output that interferes with the output of our code.

When will you release a clean version of GiDpost officially?

Regards
Malte