4. Operands#

4.1. Operand TYPE_COEUR_N#

Name of the starting heart type.

4.2. Operand NB_ASSEMBLAGE_N#

In the case of a “LIGNEXXX” starting core (with XXX =”900”, “1300” or “N4”), allows you to specify the length of the starting line

4.3. Operand TYPE_COEUR_NP1#

Name of the type of arrival heart.

4.4. Operand NB_ASSEMBLAGE_NP1#

In the case of an arrival core of the type “LIGNEXXX” (with XXX =”900”, “1300” or “N4”), allows you to specify the length of the finish line

4.5. Operand TABLE_N#

An ordered list of tables containing the information of the assemblies (name, position and design mainly) in the starting cores. If an assembly (identified by name) is in several tables, the result used will be the last one that appears in the list. It is therefore necessary to order the list of TABLE_N and RESU_N from the oldest to the most recent. For example

TABLE_N = (tab_ CHO101, tab_ CHO102),

RESU_N = (resu_ CHO101, resu_ CHO102)

4.6. Operand RESU_N#

Ordered list of results on the starting hearts (the list must be of the same length as TABLE_N and TABLE_N and RESU_N must be in the same order)

4.7. Operand TABLE_NP1#

Table containing the information of the assemblies in the core of arrival

Attention: it is essential that the information concerning an assembly be consistent in the departure and arrival tables (for example, an assembly with the same name in the departure and arrival tables must also have the same design in these tables)

4.8. Operand MAILLAGE_NP1#

Mesh corresponding to the description of the arrival core.