.. _d7.01.02-catalog:

Macro-order catalog
==============================

Here is the skeleton to be completed from the ``code_aster/cata/cata/commands/conv_mail_med.py`` catalog:

.. code-block:: python

    from.commons import*
    from.. language.DataStructure import*
    from.. language.Syntax import*


    CONV_MAIL_MED = MACRO (
        name=" CONV_MAIL_MED ",
        op= OPS ("code_aster.macrocommands.conv_mail_med_ops.conv_mail_med_ops"),
        sd_prod= ... ,
        reentrant= ... ,
        fr=tr ("Convert a ASTER, GMSH, or GIBI mesh to the MED format. "),
        UNITE_IN = ... ,
        FORMAT_IN = ... ,
        UNITE_OUT = ... ,
        INFO = ... ,
    )


.. _d7.01.02-catalog-descr:

Catalog description
------------------------

``op`` defines the path that will be used to import and launch the function
main order. The last element is the name of the function, the rest
allows you to import the file. The equivalent would be:

.. code-block:: python

    from code_aster.macrocommands.conv_mail_med_ops import conv_mail_med_ops

The macro commands are also embedded with an "executor" (cf. :ref:`d7.01.01-executecmd`),
specific since it is ``executeMacro`` instead of ``executeCommand``.
There is nothing to write for a new macro command.

The other arguments are the same as those for :ref:`commande <d7.01.01-catalog-descr>`.


.. _d7.01.02-cata-todo:

Keywords to add
~~~~~~~~~~~~~~~~~~~~~

UNITE_IN is a mandatory simple keyword. It is necessary to define the expected type.

FORMAT_IN is a simple, optional keyword that should only accept one of the three
values' ASTER ',' GIBI ',' ',' GMSH ', set to' ASTER 'by default.

UNITE_OUT is a mandatory simple keyword. We will look in the catalog of
The IMPR_RESU command the by default value used in MED format.