4. Operands#

4.1. Keyword IMPR_MACRO#

Allow or not allow displays produced by macros in the message file. Reading message files can be a pain when they contain all echoes of sub-commands generated by the macro itself. By default, only the echo commands explicitly called by the user in their command set will appear.

4.2. Keyword LANG#

It allows you to choose the language in which to display the messages sent by the code.

If the keyword is not filled in, environment variables determine the language of the messages (reference: < http://www.gnu.org/software/gettext/manual/gettext.html>`gettext manual`_). For example, you can define in the file ~/.bashrc: export LANG =fr_FR. UTF -8.

The encoding (UTF -8 or ISO -8859-1) allows accented characters to be displayed correctly.

The LANG keyword expects a two-letter value, for example “FR” (for French) or “EN” (for English).

When a language is chosen (whether by the environment or LANG), you still have to that the translated messages file (.mo file) be available. This file is expected under this name:

$ASTER_ROOT/share/locale/<lang>/LC_MESSAGES/aster_<version>.mo

where $ ASTER_ROOT is the main installation directory (e.g. /aster or /opt/aster), lang is the lowercase name of the language (e.g. en, fr, de…) and version is the name of the version used (e.g. stable, testing, unstable).

If the translation file cannot be read, French is used.

note

Even if the translation file exists, when a message has not been translated, it is displayed in French (the language in which the messages are written in the source code).

4.3. Keyword BASE#

The functionality of this keyword is to redefine the values of file parameters. direct access associated with « databases » in case you do not want to use those set by default.

Values by default for parameters associated with databases.

GLOBALE

NMAX_ENRE

62914

LONG_ENRE

100 Words

LONG_REPE

2000

VOLATILE

NMAX_ENRE

62914

LONG_ENRE

100 Words

LONG_REPE

2000

The word is worth 8 bytes on a 64-bit platform, 4 bytes on a 32-bit platform.

On Linux 64, with the default values, procedure DEBUT will allocate a direct access file of at most 62914 records of 100 Kwords (the K is equal to 1024) for the “GLOBALE” database.

note

The actual size of the file is dynamic; it depends on the volume of information at store effectively. Information is stored in files that do not exceed 12 GB each. It is possible to change this value by passing an argument on the command line. of the executable behind the keyword --max_base=size where size is a value Actual measured in MB. For the Global Database, which can be saved and re-used as calculation data, the initial maximum size in POURSUITE is kept as it is if the parameter --max_base is not used, but can be redefined as needed in this manner. In practice, this option is not useful, as the maximum size is 2 TB.

4.3.1. Operand FICHIER#

Symbolic name of the base under consideration.

4.3.2. Operands LONG_ENRE/NMAX_ENRE/LONG_REPE#

Definition of database parameters (direct access files).

LONG_ENRE is the length of the records in Kwords of the direct access files used.

note

Memory manager JEVEUX uses this setting to determine two types of objects: the large objects that will be divided into as many records as necessary, and the small items that will be accumulated in a pad of the size of a recording before being unloaded.

NMAX_ENRE is the number of records by default, this value is determined from of LONG_ENRE and an operating parameter on the Linux 64 reference platform set to 2 TB for the maximum total size of a database, if this value has not been changed by using the ``–max_base** keyword on the executable command line.

note

The two operands LONG_ENRE and NMAX_ENRE should be used with care, misuse that may lead to the sudden termination of the program by saturation of direct access files. The consistency between maximum file size and the value resulting from the product of the two parameters LONG_ENRE and NMAX_ENRE is checked at the start of execution.

LONG_REPE is the initial length of the directory (maximum number of objects addressable by JEVEUX), it is managed dynamically by the memory manager, which extends the size of the directory. and any associated system objects as and when required.

note

The choice by the user to modify these various parameters determines how Definitive some characteristics of the GLOBALE database that can no longer be modified in POURSUITE.

4.4. Keyword CODE#

This keyword is for non-regression test command files only. managed with the source code.

4.4.1. Operand NIV_PUB_WEB#

Publication level indicator. INTRANET means the test is only distributable on the internal network. INTERNET indicates that the test can be broadcast as is on the external network.

4.5. Keyword ERREUR#

Allows you to change the behavior of the code in the event of an error<F>.

4.5.1. Operand ERREUR_F#

If an error occurs, the code stops the command set from running normally.

By default, an exception is then raised (for the detailed definition of a Python exception, refer to the Python documentation or that of the supervisor, cf. [U1.03.01]). In this case, the code executes the command FIN (cf. [U4.11.02]) which then closes the database in order to allow the possible continuation of the calculation. Note that, although the initial error is said to be « fatal » (<F>), the diagnosis is <S>_ ERROR since the exception is « recovered » by FIN. This database will then be copied by the study manager. This is the behavior when ERREUR_F =” EXCEPTION “.

<F>If ERREUR_F =” ABORT “, this means that the code is explicitly asked to stop the execution of the command set permanently in case of a fatal error (). The command FIN is not executed, the database is therefore not closed correctly, it is not copied and no resumption of the calculation is possible.

notes

For the execution of test cases by developers, stopping by ABORT is automatic and by default. This is activated by the presence of the keyword factor CODE (unless ERREUR_Fprécise is something else).

In case of lack of time CPU, memory, for all type errors <S>and exceptions, the behavior is as described when ERREUR_F =” EXCEPTION “.

4.6. Keyword IGNORE_ALARM#

Allows the user to remove the display of certain alarms (whose origin they know) in order to more easily identify other alarms that may appear.

When executing command FIN, a summary table of the alarms emitted during execution (and the number of occurrences) is always displayed. Alarms ignored by the user are preceded by “*” to distinguish them (and they appear even if they were not issued).

Alarms are designated based on the nomenclature between the characters < et >, for example: IGNORE_ALARME = (“MED_2”, “SUPERVIS_40”,…).

4.7. Keyword DEBUG#

Debug option (reserved for developers and code maintenance).

4.7.1. Operand JXVERI#

Allows you to check the integrity of memory segments between two consecutive command executions. By default the execution is carried out without « DEBUG ». This option is always activated in the presence of the CODE keyword.

4.7.2. Operand ENVIMA#

Allows you to display the values of the parameters defined in the routine ENVIMA characterizing the machine [D6.01.01].

4.7.3. Operand JEVEUX#

Allows you to activate the debug mode of operation of the memory manager JEVEUX: undeferred disk uploads and assignment of value segments to an undefined value [D6.02.01].

4.7.4. Operand SDVERI#

The use of this keyword is intended for developers. Attention, this feature may cause a significant additional cost during execution.

This keyword triggers the verification of the data structures produced by the operators. It is used as part of code development procedures in non-regression testing. If the CODE keyword is present, this keyword takes the value “OUI” by default.

4.8. Keyword MESURE_TEMPS#

The MESURE_TEMPS keyword allows you to choose the level of detail of the prints of time CPU that will be displayed in the message file by the commands performing elementary calculations, the resolution of linear systems, the unloading of objects on disk or the communications MPI.

4.8.1. Operand NIVE_DETAIL#

◊ NIVE_DETAIL = 0 no impressions.
                    = 1 prints by default.
                    = 2 more detailed impressions:
                    = 3 more detailed prints and printing
                           incremental for each time step.

By default, at the end of each command, we will print a line of the type:

#1 .resolution.des.linearies.Systems.CPU. (USER + SYST/SYST/ELAPS): 7.52 0.79 11.22

#2 .elementary.calculations.and.assemblies CPU. (USER + SYST/SYST/ELAPS): 15.07 0.70 15.77


#1 .resolution.des.systemes.Linear CPU (USER + SYST/SYST/ELAPS): 7.72 0.82 8.72

#1 .1.Numbering, .connectivity of .the CPU matrix (USER + SYST/SYST/ELAPS): 0.21 0.02 0.31

#1 .2.factorization.Symbolic CPU (USER + SYST//SYST/ELAPS): 0.58 0.05 1.28

#1 .3.factorization.numeric. (or.precond.) CPU (USER + SYST/SYST/ELAPS): 6.78 0.73 7.71

#1 .4.Resolution CPU (USER + SYST//SYST/ELAPS): 0.15 0.02 0.35

#2 .elementary.calculations.and.assemblies CPU (USER + SYST/SYST/ELAPS): 28.87 0.64 29.47

#2 .1.routine.Calculation CPU (USER + SYST//SYST/ELAPS): 26.61 0.56 26.61

#2 .1.1.routines.te00ij CPU (USER + SYST//SYST/ELAPS): 24.58 0.07 25.78

#2 .2.Assemblies CPU (USER + SYST//SYST/ELAPS): 2.26 0.08 3.36

#2 .2.1.Assembly.matrices CPU (USER + SYST//SYST/ELAPS): 2.02 0.06 3.12

#2 .2.2.assemblage.seconds.Members CPU (USER + SYST/SYST/ELAPS): 0.24 0.02 0.37

During parallel calculations (MPI), the time spent in communications is also displayed:

#4 Communications MPI CPU (USER + SYST//SYST/ELAPS): 12.67 0.50 12.68

4.8.2. Operand MOYENNE#

The MOYENNE keyword allows you to control the display of additional statistics exclusively for parallel calculations. This is the average of the measurements over all the processors as well as the standard deviation of these measurements.

Each time displayed is then completed as follows:

#1 Solving linear.systems CPU (USER + SYST/SYST/ELAPS): 0.29 0.00 0.35
(average... diff.. procs) CPU (USER + SYST/SYST/ELAPS): 0.30 0.00 0.47
(standard deviation.diff.. procs) CPU (USER + + SYST/SYST/ELAPS): 0.01 0.00 0.05

4.9. Keyword MEMOIRE#

The allocation of the various data structures is a dynamic allocation, The user indicates the resource limits when launching the executable in the access interface.

4.9.1. Operand TAILLE_GROUP_ELEM#

This parameter gives the maximum number of finite elements of the same type that will be grouped in a group of items.

This parameter influences memory performance and CPU of elementary calculations and assemblies.

When increasing tgrel, you generally need to save time CPU. On the other hand, the JEVEUX objects are bigger, which may require more memory.

4.9.2. Operand TAILLE_BLOC#

This parameter gives the block size of the factored matrices for solver LDLT. This size is given in kilor8 (1 kilor8 = 1024 real). This parameter affects the number of input/output operations and therefore on the assembly and resolution time. By default, this value is set to 800 kiloR8, which is 8 records by default. on the direct access file associated with the JEVEUX database.

4.10. Keyword CATALOGUE#

This keyword is reserved for developers, it is used during the compilation operation catalogs of elements to obtain the file in base form JEVEUX.

4.10.1. Operand FICHIER#

Can only take the value “CATAELEM”.

4.10.2. Operand UNITE#

The logical unit number associated with item catalogs. In the procedures of To build the catalog of elements, we use 4 as a value. The fort.4 file is obtained from the contents of the source directory using a python procedure.

4.11. Keyword RESERVE_CPU#

Allows you to reserve a part of the CPU time allocated to the job to finish the execution cleanly in case of stoppage due to lack of time CPU detected by a command. This mechanism is only useful in the case of batch execution. The value of this reserve can be indicated in absolute value or in the form of by a percentage of the total CPU time.

When the CODE keyword is present, that is to say for all the tests, a time reserve CPU of 10 seconds is systematically imposed if the VALE keyword is absent.

At the end of the execution, it may be necessary to perform compression operations before transferring the results files or the Global Database, which are sometimes very expensive,.

4.11.1. Operand VALE#

This is the value expressed in seconds subtracted from the total time CPU, over which some global commands are based to properly stop the execution.

4.11.2. Operand POURCENTAGE#

Percentage subtracted from the total CPU time, on which some global commands are based to properly stop execution.

4.12. Keyword RESERVE_MEMOIRE#

Allows you to reserve a part of the memory allocated to the job for objects other than the internal Jeveux objects (those whose size cannot be precisely measured). This mechanism is only useful in the case of batch execution. The value of this reserve can be indicated in absolute value or in the form of of a percentage of the memory requested initially.

4.12.1. Operand VALE#

This is the value expressed in MB (1024 KB, i.e. 1024 x 1024 bytes) that will be subtracted from the amount of memory requested initially.

4.12.2. Operand POURCENTAGE#

Percentage of the memory requested initially that will be allocated to the reserve and therefore not available for Jeveux objects.