Page 1 of 1

Problem while opening the results

Posted: Tue Mar 24, 2015 1:21 am
by Golnaz Alipour
Hello,
I wrote a Finite Element program in Fortran and I want to see the results of gauss points in GID. I made the MSH file (.msh) and RES file (.res) the same as the formats in the Customization Manual. I can simply open the .msh file and I can see the mesh. However, I get an error about the res. file (please see the picture attached).
GID error.jpg
GID error.jpg (255.8 KiB) Viewed 5529 times
I want to see the results of 71 parameters; hence my .res text file has 71 columns in the values part. The error says that I should have 72 arguments. I thought that may be I should add another column containing the number of nodes in it. But it did not work. I got another error which said that now I should have 71 arguments!

I will be Thankful if you could please help me.

Best regards,
Golnaz

Re: Problem while opening the results

Posted: Tue Mar 24, 2015 11:42 am
by escolano
Attach a zip file with your example, mesh and results. (can "upload an attachment" in your forum answer)

Re: Problem while opening the results

Posted: Thu Mar 26, 2015 10:08 pm
by Golnaz Alipour
Thank you for reply.
I attached a brief description of my example , .msh file , and .res file to this post.
Thank you so much again.
Best regards,
Golnaz

Re: Problem while opening the results

Posted: Fri Mar 27, 2015 2:06 pm
by anna
Hi,
The results format it's not correct.
You only have to put the number of the element once and then all the results values, in this case for each Gauss point. You don't have to include the number of the Gauss point.
Please find here the definition:
http://www.gidhome.com/component/manual ... sult_group
At the end of the page you can find an example.

I also attach your .res file simplified with only 10 elements, where you can see the correct format.

Regards,

Re: Problem while opening the results

Posted: Sun Mar 29, 2015 10:54 pm
by Golnaz Alipour
Dear Anna,
Thanks ever so much for your guidance.
I amended the results file and the problem was fixed.
Best regards,
Golnaz