.. _U2.10.02-exemples-d-utilisation:

Examples of use
====

< https://thelfer.github.io/tfel/web/gallery.html>More examples are provided in the `gallery of #dnt_bmnaehoomgeggegkjgcbndfkeilinmmkpfe`_.

Test cases :ref:`mfron01 <V1.03.126>`, :ref:`mfron02 <V1.03.127>`, :ref:`mfron03 <V1.03.128>`, :ref:`mfron05 <V1.03.130>` and :ref:`mfron06 <V1.03.132>` allow you to check the keyword RELATION =' MFRONT ', with a file MFront provided as test data.

Note:
    < https://thelfer.github.io/tfel/web/index.html> < https://tfel.sourceforge.net>Tutorials and information about the interface between **code_aster** and MFront from the `new site #dnt_nleccnljgfdikbmfpfogclbjahmmfpnm`_ and `the older`_ describe the old one`_ describe the old way **code_aster** communicated with MFront. < https://thelfer.github.io/mgis/web/index.html>Since version 16.3.13, **code_aster** no longer uses the historical interface (option ``--interface=aster`` in the command line MFront) but the generic interface (option ``--interface=generic``) via its support called `#dnt_mekigjgdppfhkphjaiajbchPJOMHCGIN`_.

    In particular, the option "-- @AsterGenerateMtestFileOnFailure =true`` is no longer available during the compilation of the Mfront file. It allowed to automatically retrieve simulation data from **code_aster** on a hardware point (``*.mtest`` file) when the integration failed on this one. The current interface does have an equivalent directive (``-- @Generate MTestFileOnFailure =true``) but its use is useless and should be avoided because on the one hand, the calculation will take much more time (writing a file ``*.mtest`` different at each Gauss point for each calculation), memory space (with the risk of **code_aster** error by saturation, impossible to open or write to a file), and other Besides, all these ``*.mtest`` files will be removed from the temporary directory at the end of the**code_aster** calculation.