Data structure content EVOL_NOLI
====

Data structure EVOL_NOLI contains the list of fields archived during the calculation (according to
the various keyword options ARCHIVAGE). By default, it contains, for each moment,
the list of the following fields:


*   DEPL: field (at the nodes) of movements;

*   SIEF_ELGA: field (at Gauss points) of the constraints;

*   VARI_ELGA: field (at Gauss points) of the internal variables;

*   COMPORTEMENT: behavior map. This map contains behavioral information
    non-linear used, it is not readable when printed in MED format.

Depending on some calculation options, other fields will be present:


*   CONT_NOEU: field (at the nodes) for contact and friction information (see
    [:ref:`U4.44.11 <U4.44.11>`] for more details on the content of this field);

*   CONT_ELEM: field (to the elements) for the contact friction information for the method
    LAC (see [:ref:`U4.44.11 <U4.44.11>`] for more details on the content of this field);

*   INDC_ELEM: field (at the Gauss sub-points) of the contact statuses for the case XFEM with contact;

*   COHE_ELEM: field (at Gauss sub-points) of the cohesion parameter for the case XFEM with
    RELATION =' CZM ';

*   SECO_ELEM: field (at Gauss sub-points) of the friction statuses for the case XFEM with
    contact and friction;

*   STRX_ELGA: field (at Gauss points) relating to structural elements;

*   HHO_CELL and HHO_FACE: fields specific to the HHO method (see :ref:`r3.06.14 <r3.06.14>`).

In addition to these fields, the data structure also contains parameters. At each
instant, we store at least:

.. csv-table::

    "**Name**", "**Origin Keyword**", "**Description**", "**Type**"
    "INST ", "", "Calculation time value", "R"
    "EXCIT "," EXCIT ", "Cargo Information", "K24"
    "MODELE "," MODELE ", "Model", "K8"
    "CARAELEM "," CARA_ELEM ", "Basic characteristics", "K8"
    "CHAMPMAT "," CHAM_MATER ", "Material field", "K8"
    "PARM_THETA "," PARM_THETA ", "Behavioral law integration parameter", "R"
    "ITER_GLOB ", "", "Total number of Newton iterations", "I"
    "CHAR_MINI ", "", "Minimum load reached during the time step", "R"
    "ETA_PILOTAGE ", "", "Control Parameter", "R"

When looking for instability modes (with STAT_NON_LINE or DYNA_NON_LINE) or modes
vibratory (with DYNA_NON_LINE only), we store the corresponding field of movement and the
critical load value or frequency.

.. csv-table::

    "**Name**", "**Origin Keyword**", "**Description**", "**Type**"
    "CHAR_CRIT "," CRIT_STABavec
    TYPE = 'FLAMBEMENT'", "Critical buckling mode loading", "R"
    "MODE_FLAMB "," CRIT_STABavec
    TYPE = 'FLAMBEMENT'", "Buckle mode", "Field type DEPL"
    "CHAR_STAB "," CRIT_STABavec
    TYPE = 'STABILITE'", "Instability value", "R"
    "MODE_STAB "," CRIT_STABavec
    TYPE = 'STABILITE'", "Instability mode", "Field type DEPL"
    "FREQ "," MODE_VIBR ", "Vibration mode frequency (just available in DYNA_NON_LINE)", "R"
    "DEPL_VIBR "," MODE_VIBR ", "Vibration mode (just available in DYNA_NON_LINE)", "Field type DEPL"

    "**Name**", "**Origin Keyword**", "**Description**", "**Type**"
    "CHAR_CRIT "," CRIT_STAB with
    TYPE = 'FLAMBEMENT'", "Critical buckling mode loading", "R"
    "MODE_FLAMB "," CRIT_STAB with
    TYPE = 'FLAMBEMENT'", "Buckle mode", "Field type DEPL"
    "CHAR_STAB "," CRIT_STAB with
    TYPE = 'STABILITE'", "Instability value", "R"
    "MODE_STAB "," CRIT_STAB with
    TYPE = 'STABILITE'", "Instability mode", "Field type DEPL"
    "FREQ "," MODE_VIBR ", "Vibration mode frequency (just available in DYNA_NON_LINE)", "R"
    "DEPL_VIBR "," MODE_VIBR ", "Vibration mode (just available in DYNA_NON_LINE)", "Field type DEPL"