I am performing a large deformation analysis which is nonlinear. So I will
have displacement at different steps, say from 1-10 with the 10th step being
the final deformed shape of the body.
How do I prepare the post process file for proper animation of deformation
in GiD?
\
Should I print the nodal coordinates or the displacements at each
step (in vector result header)? I want to investigate how the body deforms
in the post processor
\
Since there can be many time steps with significant amount of
nodes, the .post file can be quite big. Is that of any concern for
post-processing by GiD? For e.g. I am looking at ‘x’ and ‘y’ values for
about 8000 nodes with about 10-20 steps.
I am asking these issues before hand, so that I can code accordingly.
Each result of the .post.res results file has a ‘time step’ field to store a real number (e.g. time or step number).
For each time step you must write a result with the ‘displacement’ of the nodes (the difference between the final and initial position)
Then you can show an animation along the time in postprocess using the Window-Animation… tool
8000 nodes with 20 time steps is a moderated size result, you can handle it with GiD without problems.
It is recommended to write the .post.res in binary format to have smaller files and to be read faster. Using our gidpost library swap from ASCII to binary compressed is easy :
invoke the GiD_OpenPostMeshFile command with the parameter GiD_PostBinary instead GiD_PostAscii
Enrique
----- Original Message -----
From: Shriram
To: gidlist at gatxan.cimne.upc.edu
Sent: Tuesday, February 16, 2010 12:37 AM
Subject: [GiDlist] Making Animations
Hi,
I am performing a large deformation analysis which is nonlinear. So I will have displacement at different steps, say from 1-10 with the 10th step being the final deformed shape of the body.
How do I prepare the post process file for proper animation of deformation in GiD?
\
Should I print the nodal coordinates or the displacements at each step (in vector result header)? I want to investigate how the body deforms in the post processor
\
Since there can be many time steps with significant amount of nodes, the .post file can be quite big. Is that of any concern for post-processing by GiD? For e.g. I am looking at 'x' and 'y' values for about 8000 nodes with about 10-20 steps.
I am asking these issues before hand, so that I can code accordingly.