Professional Documents
Culture Documents
0 Post-Processing
User’s guide
January 2008
2 Command list
3 BEFORE COMPUTATION
4 DURING COMPUTATION
5 AFTER COMPUTATION
6 Examples
The LMGC90 post-processing relies on a list of commands in the same way that the list of CHIC
commands used in the file COMMAND.DAT. The post-processing command are located in the
POSTPRO.DAT file in the DATBOX directory.
The LMGC90 post-processing relies on a list of commands in the same way that the list of CHIC
commands used in the file COMMAND.DAT. The post-processing command are located in the
POSTPRO.DAT file in the DATBOX directory.
The LMGC90 post-processing relies on a list of commands in the same way that the list of CHIC
commands used in the file COMMAND.DAT. The post-processing command are located in the
POSTPRO.DAT file in the DATBOX directory.
The LMGC90 post-processing relies on a list of commands in the same way that the list of CHIC
commands used in the file COMMAND.DAT. The post-processing command are located in the
POSTPRO.DAT file in the DATBOX directory.
The LMGC90 post-processing relies on a list of commands in the same way that the list of CHIC
commands used in the file COMMAND.DAT. The post-processing command are located in the
POSTPRO.DAT file in the DATBOX directory.
The LMGC90 post-processing relies on a list of commands in the same way that the list of CHIC
commands used in the file COMMAND.DAT. The post-processing command are located in the
POSTPRO.DAT file in the DATBOX directory.
The post-processing could be performed during the simulation or using the Vloc Rloc.OUT and
DOF.OUT output files.
If the post-processing will be performed during the simulation, the user needs to add some extra
commands in the file COMMAND.DAT:
If the post-processing will be performed during the simulation, the user needs to add some extra
commands in the file COMMAND.DAT:
START POSTPRO to store all commands which must be used and initialize the
post-processing structure.
If the post-processing will be performed during the simulation, the user needs to add some extra
commands in the file COMMAND.DAT:
START POSTPRO to store all commands which must be used and initialize the
post-processing structure.
POSTPRO DURING COMPUTATION to scan commands which must be executed during
the simulation process.
If the post-processing will be performed during the simulation, the user needs to add some extra
commands in the file COMMAND.DAT:
START POSTPRO to store all commands which must be used and initialize the
post-processing structure.
POSTPRO DURING COMPUTATION to scan commands which must be executed during
the simulation process.
POSTPRO AFTER COMPUTATION to scan commands which must executed after the
simulation
If the post-processing will be performed during the simulation, the user needs to add some extra
commands in the file COMMAND.DAT:
START POSTPRO to store all commands which must be used and initialize the
post-processing structure.
POSTPRO DURING COMPUTATION to scan commands which must be executed during
the simulation process.
POSTPRO AFTER COMPUTATION to scan commands which must executed after the
simulation
If the post-processing will be performed using output files, the user does not need to launch again
the simulation. The command file must be changed a minima,using the previous command and
the following ones:
If the post-processing will be performed during the simulation, the user needs to add some extra
commands in the file COMMAND.DAT:
START POSTPRO to store all commands which must be used and initialize the
post-processing structure.
POSTPRO DURING COMPUTATION to scan commands which must be executed during
the simulation process.
POSTPRO AFTER COMPUTATION to scan commands which must executed after the
simulation
If the post-processing will be performed using output files, the user does not need to launch again
the simulation. The command file must be changed a minima,using the previous command and
the following ones:
INIT POST DATA to init data and specify the first and last ID files to read (give on the lines
after the command).
If the post-processing will be performed during the simulation, the user needs to add some extra
commands in the file COMMAND.DAT:
START POSTPRO to store all commands which must be used and initialize the
post-processing structure.
POSTPRO DURING COMPUTATION to scan commands which must be executed during
the simulation process.
POSTPRO AFTER COMPUTATION to scan commands which must executed after the
simulation
If the post-processing will be performed using output files, the user does not need to launch again
the simulation. The command file must be changed a minima,using the previous command and
the following ones:
INIT POST DATA to init data and specify the first and last ID files to read (give on the lines
after the command).
UPDATE POST DATA to update the output file to read.
If the post-processing will be performed during the simulation, the user needs to add some extra
commands in the file COMMAND.DAT:
START POSTPRO to store all commands which must be used and initialize the
post-processing structure.
POSTPRO DURING COMPUTATION to scan commands which must be executed during
the simulation process.
POSTPRO AFTER COMPUTATION to scan commands which must executed after the
simulation
If the post-processing will be performed using output files, the user does not need to launch again
the simulation. The command file must be changed a minima,using the previous command and
the following ones:
INIT POST DATA to init data and specify the first and last ID files to read (give on the lines
after the command).
UPDATE POST DATA to update the output file to read.
In both cases, the resulting files are written in the POSTPRO directory.
In the case of the post treatment using output files, extra command must be used in the
COMMAND.DATfile to study specific area in the sample. The synopsis of the command is the
following:
CIRCULAR SELECTION
Xc
Yc
Radius
where (Xc,Yc) are the center of the selected area and Radius its radius.
In the case of the post treatment using output files, extra command must be used in the
COMMAND.DATfile to study specific area in the sample. The synopsis of the command is the
following:
CIRCULAR SELECTION
Xc
Yc
Radius
where (Xc,Yc) are the center of the selected area and Radius its radius.
It is possible to translate the selection during the post treatment.The synopsis of the command is
the following:
SELECTION TRANSLATION
dXc
dYc
where (dXc,dYc ar the increment of translation add between the analyze of two sets of output
files.
1 Introduction
2 Command list
3 BEFORE COMPUTATION
4 DURING COMPUTATION
5 AFTER COMPUTATION
6 Examples
BEFORE COMPUTATION
DURING COMPUTATION
AFTER COMPUTATION
Dist MAILx
1 Introduction
2 Command list
3 BEFORE COMPUTATION
4 DURING COMPUTATION
5 AFTER COMPUTATION
6 Examples
The command allows the definition of node sets. The command must be used when the
command Fint EVOLUTION, Dep EVOLUTION and are used.
The synopsis of the command in the POSTPRO.DAT file is the following:
1 Introduction
2 Command list
3 BEFORE COMPUTATION
4 DURING COMPUTATION
5 AFTER COMPUTATION
6 Examples
t, ux , uy , ω, vx , vy , ω̇ (1)
where t is the simulation time, ux and uy the displacements along the X and Y axis, ω the body
rotation, vx et vy the components of the velocity vector along X and Y while ω̇ denote the body
splin.
t, ux , uy , ω, vx , vy , ω̇ (1)
where t is the simulation time, ux and uy the displacements along the X and Y axis, ω the body
rotation, vx et vy the components of the velocity vector along X and Y while ω̇ denote the body
splin.
The synopsis of the command in the POSTPRO.DAT file is the following:
BODY TRACKING
STEP N
nb
ID 1
...
ID nb
where N denotes the command period, nb the number of tracking bodies and ID i the index of
the body in the RBDY2 list.
There is nb files BODY TRACKING XXXXX.DAT created where each file is identified by the
body index instead of the XXXXX characters.
The command allows to track the evolution of the coodination number according to different
definitions: np nc nt na
c0 = c+ = c− = c= (2)
nb nb nb nb
where np , nc , nt , na and nb denote respectively the mean number of rough contacts, the mean
number contacts in compression, the mean number contact in traction, the mean number of
active contacts and the number of bodies. Data are stored in files
BODY TRACKING XXXXX.DAT as:
t, c0 , c+ , c− , c (3)
The command allows to track the evolution of the coodination number according to different
definitions: np nc nt na
c0 = c+ = c− = c= (2)
nb nb nb nb
where np , nc , nt , na and nb denote respectively the mean number of rough contacts, the mean
number contacts in compression, the mean number contact in traction, the mean number of
active contacts and the number of bodies. Data are stored in files
BODY TRACKING XXXXX.DAT as:
t, c0 , c+ , c− , c (3)
COORDINATION NUMBER
STEP N
The command allows to track the evolution of the torque of contact forces of different bodies.
Data are stored in files TORQUE EVOLUTION XXXXX.DAT as:
t, Rx , Ry , Mz (4)
where t is the simulation time, Rx and Ry the components along X and Y, and Mz the
momemtum according to the Z direction.
The command allows to track the evolution of the torque of contact forces of different bodies.
Data are stored in files TORQUE EVOLUTION XXXXX.DAT as:
t, Rx , Ry , Mz (4)
where t is the simulation time, Rx and Ry the components along X and Y, and Mz the
momemtum according to the Z direction.
TORQUE EVOLUTION
STEP N
nb
ID 1
...
ID nb
where N denotes the command period, nb the number of tracking bodies and ID i the index of
the body in the RBDY2 list.
There is nb files TORQUE EVOLUTION XXXXX.DAT created where each file is identified by the
body index instead of the XXXXX characters.
where na denotes the number of active contact (non nul) and rnα the normal force associated to
contact α.
where na denotes the number of active contact (non nul) and rnα the normal force associated to
contact α.
Data are stored in two files. The first file is the file NORMAL CONTACT DISTRIBUTION.DAT
where the diagram data are stored as:
XG , YG , XW , YW , XS , YS (6)
where indices G , W and S refer respectively to global, weak and strong contact network.
The second file is the file P2THETA.DAT where the histogram data are stored as:
θi , NG , NW , NS (7)
where θi is the sector value (in radian) ranging from −π to π, NG , NW and NS the percent of
contact of the global, weak and strong contact network in the θi direction.
where N denotes the command period, nb the number of angular sectors of the upper part.
The command allows to track the evolution of the number of iterations, the last value of error
criteria (after convergence or not) and the contact number. Data are stored in file
SOLVER INFORMATIONS.DAT as:
t, Nit , 1 , 3 , 3 , nc (8)
where t is the simulation time, Nit the number of iterations, i (i=1,2,3) the last values of error
criteria and nc the number of contacts.
The command allows to track the evolution of the number of iterations, the last value of error
criteria (after convergence or not) and the contact number. Data are stored in file
SOLVER INFORMATIONS.DAT as:
t, Nit , 1 , 3 , 3 , nc (8)
where t is the simulation time, Nit the number of iterations, i (i=1,2,3) the last values of error
criteria and nc the number of contacts.
SOLVER INFORMATIONS
STEP N
The command allows to track the evolution of a contact between two RBDY2. Data are stored in
the file DOUBLET INTERACTIONS.DAT as:
t, g , g0 , rn , rt , vn , vt (9)
where t is the simulation time, g and g0 the distance between particles before and after
computation, rn et rt the normal and tangential forces, vn andvt the normal and tangential
relative velocity.
The command allows to track the evolution of a contact between two RBDY2. Data are stored in
the file DOUBLET INTERACTIONS.DAT as:
t, g , g0 , rn , rt , vn , vt (9)
where t is the simulation time, g and g0 the distance between particles before and after
computation, rn et rt the normal and tangential forces, vn andvt the normal and tangential
relative velocity.
DOUBLET INTERACTIONS
STEP N
ID1
ID2
where N denotes the command period, ID1 and ID2 the two body identifiant.
The command allows to make a snapshot of the mechanical sample. For each snapshot, data are
stored in a file SNAPSHOTXXXX.DAT where XXXX denotes the file index. Each file are
composed of 11 column and nb lignes, where nb is the number of bodies. Each line is structured
as:
X , Y , A, Vx , Vy , ω̇, σ11 , σ12 , σ21 , σ22 , c (10)
where X and Y denotes the body, A the body area, Vx and Vy the component of the velocity
along X and Y respectively, ω̇ the spin, σ the body stress tensor and c the coordination number.
The command allows to make a snapshot of the mechanical sample. For each snapshot, data are
stored in a file SNAPSHOTXXXX.DAT where XXXX denotes the file index. Each file are
composed of 11 column and nb lignes, where nb is the number of bodies. Each line is structured
as:
X , Y , A, Vx , Vy , ω̇, σ11 , σ12 , σ21 , σ22 , c (10)
where X and Y denotes the body, A the body area, Vx and Vy the component of the velocity
along X and Y respectively, ω̇ the spin, σ the body stress tensor and c the coordination number.
SNAPSHOT SAMPLE
STEP N
The command allows to make a snapshot of the thermal, electrical and mechanical sample. For
each snapshot, data are stored in a file SNAPSHOTXXXX.DAT where XXXX denotes the file
index. Each file are composed of 16 column and nb lignes, where nb is the number of bodies.
Each line is structured as:
where X and Y denotes the body, A the body area, Vx and Vy the component of the velocity
along X and Y respectively, ω̇ the spin, σ the body stress tensor, c the coordination number, T
the temperature, CT the thermal conductivity, E the electrical potential, CE the electrical
conductivity and β the wear componant (used in CZM law).
The command allows to make a snapshot of the thermal, electrical and mechanical sample. For
each snapshot, data are stored in a file SNAPSHOTXXXX.DAT where XXXX denotes the file
index. Each file are composed of 16 column and nb lignes, where nb is the number of bodies.
Each line is structured as:
where X and Y denotes the body, A the body area, Vx and Vy the component of the velocity
along X and Y respectively, ω̇ the spin, σ the body stress tensor, c the coordination number, T
the temperature, CT the thermal conductivity, E the electrical potential, CE the electrical
conductivity and β the wear componant (used in CZM law).
MP SNAPSHOT SAMPLE
STEP N
The command allows to determine the average velocity of a sample during the simulation process.
Data are stored in the file AVERAGE VELOCITY.DAT as:
¯ kV̄ k
t, V̄x , V̄y , ω̇, (12)
¯ mean splin and
where t is the simulation time, V̄x and V̄y the mean velocity along X and Y, ω̇
kV̄ k the euclidian norm of the mean velocity.
The command allows to determine the average velocity of a sample during the simulation process.
Data are stored in the file AVERAGE VELOCITY.DAT as:
¯ kV̄ k
t, V̄x , V̄y , ω̇, (12)
¯ mean splin and
where t is the simulation time, V̄x and V̄y the mean velocity along X and Y, ω̇
kV̄ k the euclidian norm of the mean velocity.
The command allows to track the evolution of the number of contacts according to their status
for dry contact law. Data are stored in the file DRY CONTACT NATURE.DAT as:
w s w s
t, Nno , NSlide , NSlide , NStick , NStick (13)
where t is the simulation time, Nno the number of non active contacts, w
NSlide
and s
NSlide
the
w
number of sliding contact for the weak and strong network respectively, and NStick s
and NStick the
number of sticking contacts for the weak and strong network respectively.
The command allows to track the evolution of the number of contacts according to their status
for dry contact law. Data are stored in the file DRY CONTACT NATURE.DAT as:
w s w s
t, Nno , NSlide , NSlide , NStick , NStick (13)
where t is the simulation time, Nno the number of non active contacts, and w
NSlidethe s
NSlide
w
number of sliding contact for the weak and strong network respectively, and NStick s
and NStick the
number of sticking contacts for the weak and strong network respectively.
The command allows to track the evolution of the number of contacts according to their status
for cohesive contact law. Data are stored in the file WET CONTACT NATURE.DAT as:
where t is the simulation time, NStick the number of sticking contacts, NSlide the number of
sliding contac et Nno the number of non active contacts.
The command allows to track the evolution of the number of contacts according to their status
for cohesive contact law. Data are stored in the file WET CONTACT NATURE.DAT as:
where t is the simulation time, NStick the number of sticking contacts, NSlide the number of
sliding contac et Nno the number of non active contacts.
where nb denotes the number of bodies, mi the mass of body i, Vi its velocity, Ii its inertia
momentum and ω̇i its spin. g denotes the gravity acceleration and q the body position.
where nb denotes the number of bodies, mi the mass of body i, Vi its velocity, Ii its inertia
momentum and ω̇i its spin. g denotes the gravity acceleration and q the body position.
t, Ec , Ep , ∆E, P, (16)
where t is the simulation time, Ec and Ep denote the kinetic and potential energy respectively,
∆E the energy variation and P the power of the system.
where nb denotes the number of bodies, mi the mass of body i, Vi its velocity, Ii its inertia
momentum and ω̇i its spin. g denotes the gravity acceleration and q the body position.
t, Ec , Ep , ∆E, P, (16)
where t is the simulation time, Ec and Ep denote the kinetic and potential energy respectively,
∆E the energy variation and P the power of the system. The synopsis of the command in the
POSTPRO.DAT file is the following:
KINETIC ENERGY
STEP N
t, Ec , Ep , ∆E, P (17)
where t is the simulation time, Ec and Ep denote the kinetic and potential energy respectively,
∆E the energy variation and P the power of the system.
t, Ec , Ep , ∆E, P (17)
where t is the simulation time, Ec and Ep denote the kinetic and potential energy respectively,
∆E the energy variation and P the power of the system.
KINETIC ENERGY
STEP N
ns ¡
S1
...
S ns
where N denotes the command period, ns the number of species, S i the different tracked
species. There is ns files XXXXX KINETIC ENERGY.DAT created where each file is identified by
the species name instead of the XXXXX characters.
where nc denotes the number of contacts and gα the gap associated to contact α.
Data are stored in the file VIOLATION EVOLUTION.DAT as:
0 0
t, Vmean , Vmean , Vmax , Vmax (19)
where t is the 0
simulation time, Vmean et Vmean the mean violations at the beginning and the end
of a time step 0
and Vmax et Vmax the maximal violations at the beginning and the end of a time
step.
where nc denotes the number of contacts and gα the gap associated to contact α.
Data are stored in the file VIOLATION EVOLUTION.DAT as:
0 0
t, Vmean , Vmean , Vmax , Vmax (19)
where t is the 0
simulation time, Vmean et Vmean the mean violations at the beginning and the end
of a time step 0
and Vmax et Vmax the maximal violations at the beginning and the end of a time
step.
VIOLATION EVOLUTION
STEP N
The command determines the number of simple contacts and the number of double contacts in a
polygon sample. Data are stored in the file PLPLx ANALYSIS.DAT as:
t, Ns , Nd (20)
where t is the simulation time, Ns the number of simple contacts and Nd the number of double
contacts.
The command determines the number of simple contacts and the number of double contacts in a
polygon sample. Data are stored in the file PLPLx ANALYSIS.DAT as:
t, Ns , Nd (20)
where t is the simulation time, Ns the number of simple contacts and Nd the number of double
contacts.
PLPLx ANALYSIS
STEP N
The command computes the number of contacts for which the tangential force rt is closed of the
sliding threshold µrn . To be taken into account, the tangential force of a contact must satisfied:
t, N, p (22)
where t is the simulation time, N the number of quasi sliding contacts and p the quasi sliding
contacts percent.
The command computes the number of contacts for which the tangential force rt is closed of the
sliding threshold µrn . To be taken into account, the tangential force of a contact must satisfied:
t, N, p (22)
where t is the simulation time, N the number of quasi sliding contacts and p the quasi sliding
contacts percent.
where N denotes the command period and P the part of the friction threshold in less (in percent).
The command allows the storage of electrical output during the simulation process. Data are
stored in the file ELECTRO EVOLUTION.DAT as:
t, iter , , I , R, U, V − , C̄ (23)
where t is the simulation time, iter the number of iterations for the resolution of the electrical
problem, the error value, I the electric current intensity, R the equivalent resistance, U the
electrical tension, V − the electrical potential of the exit node and C̄ the mean conductance.
The command allows the storage of electrical output during the simulation process. Data are
stored in the file ELECTRO EVOLUTION.DAT as:
t, iter , , I , R, U, V − , C̄ (23)
where t is the simulation time, iter the number of iterations for the resolution of the electrical
problem, the error value, I the electric current intensity, R the equivalent resistance, U the
electrical tension, V − the electrical potential of the exit node and C̄ the mean conductance.
The synopsis of the command in the POSTPRO.DAT file is the following:
ELECTRO EVOLUTION
STEP N
The command allows the storage of electrical output during the non linear simulation process.
Data are stored in the file NL ELECTRO EVOLUTION.DAT as:
where t is the simulation time, iter the number of iterations for the resolution of the non linear
electrical problem, the error value, No the number of oxyde layers, ∆No the number of electrical
status variations, P̄, P − et P + the mean, minimal and maximal electrical power, U the electrical
tension and I the electric current intensity.
The command allows the storage of electrical output during the non linear simulation process.
Data are stored in the file NL ELECTRO EVOLUTION.DAT as:
where t is the simulation time, iter the number of iterations for the resolution of the non linear
electrical problem, the error value, No the number of oxyde layers, ∆No the number of electrical
status variations, P̄, P − et P + the mean, minimal and maximal electrical power, U the electrical
tension and I the electric current intensity.
NL ELECTRO EVOLUTION
STEP N
On normalise ensuite par la norme de la force moyenne (resp. la force normale moyenne). Les
données sont stockées sous forme de tableau dans les fichiers
CONTACT FORCE DISTRIBUTION0000.DAT où chaque ligne correspond à un incrément sur
l’échelle de force normée et où les colonnes se décomposent en:
où Vr correspond à la valeur sur l’échelle des forces normées, Nr au nombre de contacts
correspondants à cette valeur, Vrn à la valeur sur l’échelle normée des forces normales et Nrn au
nombre de contacts correspondants à cette valeur.
On normalise ensuite par la norme de la force moyenne (resp. la force normale moyenne). Les
données sont stockées sous forme de tableau dans les fichiers
CONTACT FORCE DISTRIBUTION0000.DAT où chaque ligne correspond à un incrément sur
l’échelle de force normée et où les colonnes se décomposent en:
où Vr correspond à la valeur sur l’échelle des forces normées, Nr au nombre de contacts
correspondants à cette valeur, Vrn à la valeur sur l’échelle normée des forces normales et Nrn au
nombre de contacts correspondants à cette valeur.
where N denotes the command period and sa the force scale discretization.
The command allows to track the number of contact status that changed during the force
computation phase. The global, weak and strong network are checked. Data are stored in the file
NETWORK EVOLUTION.DAT as:
t, NG , NW , NS (26)
where t is the simulation time, NG ,NW and NS respectively the number of contact for which the
status change in the global, weak and strong network.
The command allows to track the number of contact status that changed during the force
computation phase. The global, weak and strong network are checked. Data are stored in the file
NETWORK EVOLUTION.DAT as:
t, NG , NW , NS (26)
where t is the simulation time, NG ,NW and NS respectively the number of contact for which the
status change in the global, weak and strong network.
NETWORK EVOLUTION
STEP N
where N denotes the command period.
The command allows to track the forces acting on a node set of a deformable body defined using
the command NEW MECAx SETS. Data are stored in the file Fint XXX.DAT as:
where t is the simulation time, Rcx and Rcy the twocomponents of the contact forces, Fint,x and
Fint,y the two components of the internal forces, Finer ,x and Finer ,y the two components of the
inertial forces and finally Rx and Ry the sum of all forces. The number of file Fint XXX.DAT is
equal to the number of mechanical set defined using the command NEW MECAx SETS. XXX
characters are replaced by the index of the mechanical set in the global list.
The command allows to track the forces acting on a node set of a deformable body defined using
the command NEW MECAx SETS. Data are stored in the file Fint XXX.DAT as:
where t is the simulation time, Rcx and Rcy the twocomponents of the contact forces, Fint,x and
Fint,y the two components of the internal forces, Finer ,x and Finer ,y the two components of the
inertial forces and finally Rx and Ry the sum of all forces. The number of file Fint XXX.DAT is
equal to the number of mechanical set defined using the command NEW MECAx SETS. XXX
characters are replaced by the index of the mechanical set in the global list.
Fint EVOLUTION
STEP N
where N denotes the command period.
The command allows to track the mean displacement and the mean velocity of a node set of a
deformable body defined using the command NEW MECAx SETS. Data are stored in the file
Dep XXX.DAT as:
t, ux , uy , vx , vy (28)
where t is the simulation time, ux and uy the mean displacements along the X and Y axes and,
vx and vy the mean velocities along the X and Y axes. The number of file Dep XXX.DAT is
equal to the number of mechanical set defined using the command NEW MECAx SETS. XXX
characters are replaced by the index of the mechanical set in the global list.
The command allows to track the mean displacement and the mean velocity of a node set of a
deformable body defined using the command NEW MECAx SETS. Data are stored in the file
Dep XXX.DAT as:
t, ux , uy , vx , vy (28)
where t is the simulation time, ux and uy the mean displacements along the X and Y axes and,
vx and vy the mean velocities along the X and Y axes. The number of file Dep XXX.DAT is
equal to the number of mechanical set defined using the command NEW MECAx SETS. XXX
characters are replaced by the index of the mechanical set in the global list.
Dep EVOLUTION
STEP N
where N denotes the command period.
1 Introduction
2 Command list
3 BEFORE COMPUTATION
4 DURING COMPUTATION
5 AFTER COMPUTATION
6 Examples
Dist MAILx
STEP N
where N denotes the command period.
1 Introduction
2 Command list
3 BEFORE COMPUTATION
4 DURING COMPUTATION
5 AFTER COMPUTATION
6 Examples
Postpro file example
LMGC90 post treatment
#23456789012345678901234567890:
BODY TRACKING :
STEP 1 :
1 :
54 :
TORQUE EVOLUTION :
STEP 1 :
1 :
56 :
SOLVER INFORMATIONS :
STEP 1 :
DISSIPATED ENERGY :
STEP 1 :
VIOLATION EVOLUTION :
STEP 1 :
END :
# # :
#Example of COMMAND.DAT for post treatment START POSTPRO :
#January 2008 # :
# INIT POST DATA :
#23456789012345678901234567890: 1 :
# : 20 :
TIME STEP : ##############################:
0.1D-04 : #
THETA : post loop :
1.D0 : # :
# : ECHO ON :
READ BODIES : # :
READ BEHAVIOURS : UPDATE POST DATA :
READ INI DOF : # :
READ INI Vloc Rloc : READ INI DOF :
READ DRIVEN DOF : READ INI Vloc Rloc :
# : # :
COMPUTE STRESS : WRITE OUTPUT GMV STEP 1 :
COMPUTE AVERAGE VELOCITY : POSTPRO DURING COMPUTATION :
COMPUTE DISPLACEMENT : # :
REFERENCE RADIUS : REPETE 100 FOIS :
0.005 : DEPUIS post loop :
INIT GMV : # :
WRITE OUTPUT GMV : FIN DU PROGRAMME :
# : # :
COMPUTE BOX : FIN DU FICHIER :
COMPUTE MASS : ##############################: