3. Operands#

The FIN command saves all the concepts calculated during execution in the file glob.1 (and possibly glob.2,… if necessary), as well as all the Python objects from the execution context in pickle files. These items will be available for a POURSUITE calculation.

If the user did not ask to copy the database after the calculation (there is no base in the study’s .export file), FIN will do nothing.

note

Python class, function, and type objects are not saved in file pick.codeaster.objects.

When FIN has finished its work, Python continues to analyze the instructions that follow, which will certainly fail if they use code_aster objects.

The developer can use « FIN (exit=True) » to force exit the Python interpreter.

3.1. Keyword RETASSAGE#

Causes the “GLOBALE” database to be reset before writing to the associated file. This makes it possible to keep smaller databases (rid of objects associated with concepts destroyed by the user).

This resetting is carried out as follows by the command:

  • closure of the bases,

  • opening the “GLOBALE” base,

  • opening a “VOLATILE” base,

  • copy, record not empty by record not empty from base “GLOBALE” on base “VOLATILE”,

  • rename by the code of this database “VOLATILE” to save as if it were the classic “GLOBALE” database.

The GLOBALE database consists of one or more binary files organized in the form of fixed-length records. During the destruction operations, the associated records are declared free and can possibly be reused during execution. At the end of execution, there may be unoccupied records that contribute to the final size of the file. The resetting operation therefore consists in reusing this space by reorganizing the recordings. It is an operation that can result in a lot of disk reading and writing.

During a classic parallel execution (MPI), « centralized » mode, each instance of the GLOBALE database is processed, which multiplies the inputs/outputs. In distributed mode, each instance manages its own inputs/outputs according to its needs.

3.2. Keyword INFO_RESU#

Causes information relating to the content of all the result data structures stored in the GLOBALE database to be printed in the file MESSAGE.

Note:

Using this keyword can significantly increase the execution time of command FIN and produce very large output files. For this reason, it is not enabled by default.

3.3. Keyword INFO_BASE#

This keyword allows you to print the list of objects present in the global database as well as their size in the file MESSAGE. When the database is saved, printing is done automatically. If not, you can activate this keyword to display the list.