GiD forum

Dear GIDLIST

For postprocess in GID 12.0, when I output time evolution of one result at a point defined by input coordinates in the deformed mesh, there output more than one graph.
This problem doesn't exist for versions older than (including) G10.0.
Could somebody find solution for that?

Thanks
gchen

Hello gchen,

This should be a fixed problem in the newer versions.
Have you tried with the last developer version?
If the problem persist, please attach an example and explain the steps that you follow.

Best regards,

Dear Anna

Thanks for your reply!
I am using GID 12.0.7 which seems to be very new version.
I attach one example named "2DPS_TH_BH.gid.7z", please check!
After you load the postprocess file, if you output the temperature profile from (0,1.25) to (0,10), you will see the plot like Figure 1 in the other attached file "T-Y.doc".
If I do the same thing using GID 8.0, GID9.0, Gid 10.0, the plot looks like Figure 2 in the file "T-Y.doc".

Look forward to your reply!
gchen

Another file mentioned in my previous reply is attached here.

Another file mentioned in my previous reply is attached here with name "T-Y.7z".

Ok, now I've understood your problem.

I've tried the same steps in older versions, 9.0 and 10.0 and I'm not getting the desired graph (the second image in T-Y.docx). I'm always getting 2 graphs but this is not an error because the defined line between the 2 points lies in 2 surfaces sets, so you get 1 graph for each surface set.

To get the second graph you had created the line graph with values (1.25, 0) and (10,0) instead of (0,1.25) and (0,10). In this case, the defined line only lies in one surface set, so you get only one graph.

I agree with Anna that the same bug appear in old GiD 9 and 10 versions that I have tested,
but the problem is not that the cut lies in two surface sets!!

It seems a bug of GiD that is doing wrongly the cut between the specified coordinates (0,1.25) to (0,10)
The cut that is drawn in screen don't start in (0.1.25) , is starts apparently near y=-4.37 !!

We must fix it in next official and developer GiD versions.

Dear Anne and Escolano

Thanks for your reply!
You are right, the same problem appears in GID9.0, and sorry for the mistake!

gchen