1. Principle of the test#
This test is a computer test. It is used to validate the programming of the processing of the keyword ETAT_INIT and more particularly the vrcomp.f routine.
To define the initial state of a non-linear calculation, the user has two options:
or it indicates an evol_noli data structure and a « moment » in this evol_noli (keywords EVOL_NOLI + INST)
or it gives 3 « isolated » displacement fields, constraints and internal variables (keywords DEPL, SIGM and VARI)
The programming is different to deal with these two cases. That’s why we’re testing them both.
The test emits the following two errors:
! ————————————————————————!
! <EXCEPTION> <CALCULEL5_42>!
! !
! incompatible behaviors: VMIS_CINE_LINE and VMIS_ISOT_TRAC for the M1 mesh!
! ————————————————————————!
! —————————————————————————————-!
! <EXCEPTION> <CALCULEL3_49>!
! !
! Usage error:!
! You want to « continue » a non-linear calculation (STAT_NON_LINE or DYNA_NON_LINE).!
! To do this, you specify an initial state (keyword ETAT_INIT/VARI =chvari).!
! For the calculation of the 1st time step, the internal variables field used for the start of the step!
! is « chvari ».!
! For the element carried by the mesh M 1, this field of internal variables does not have the same number of!
! internal variables (7) than the number expected by the behavior chosen for the calculation (2).!
! !
! So there is a change in behavior for the M1 mesh!
! The code only accepts changes in behavior in a few very specific cases:!
! - LEMAITRE <-> VMIS_ISOT_XXXX!
! - ELAS <-> XXXX!
! It does not seem like you are in this situation. The execution is stopped.!
! !
! Risks & advice:!
! Check the affected behavior on this mesh.!
! —————————————————————————————-!