3. Application environment#

3.2. Development aid#

The errors encountered and detected by the software package cause an error message to be printed, and in some cases close the databases opened by the application. The software package then prints the state of the memory it manages and the catalogs of all open classes.

Note:

JEVEUX uses its own message printing routines different from those of Code_Aster to avoid dynamically recursive calls.

All JEVEUX objects, saved beforehand, are recoverable in a later run.

3.3. The Code_Aster environment#

Two databases can be used within the Code_Aster application:

base “GLOBALE”

associated with class” G “

base “VOLATILE”

associated with class” V “

The actual size of the file is dynamic; it depends on the volume of information to be stored effectively. This size is limited by operating conditions and a parameter defined among the values characterizing the platform. On the 64-bit Linux reference platform, the initial size is set to 48GB. This value is used to size 2 objects used by the memory manager, it will be changed automatically during execution if necessary. It is possible to change this value by passing an argument on the executable command line behind the keyword « ‑max_base size » where size is a real value measured in MB.

On 32-bit platforms, the initial size is set to 2.047 GB (2,147,483,647), but the code handles multiple files to go beyond this limit when the « ‑max_base » setting is changed.

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 « ‑max_base » parameter is not used, but can be redefined as needed in this way.

Automatic resizing is implemented when writing to associated files, based on a filling criterion set at 50% of the number of records, the JJAGOD utility is called to resize system objects $$ USADI and $$ ACCE that depend directly on the maximum size of the files used.

Note:

A third name base “BASEELEM “is used to store and review the compiled catalog of items.

Error message printings are performed by message printing utilities with the following conventions:

  • programming error (incorrect use of JEVEUX): class” S “message with immediate stop;

  • operating error (access to a non-existent object,…): class” F “message with an attempt to close open databases.

Code_Aster error message printing utilities can sometimes be used to communicate with the Supervisor and to properly stop the code by validating the concepts created. The names of printing units specified when calling the printing routines (JEIMPO, JEIMPR,…) are as follows:

  • RESULTAT: calculation results,

  • MESSAGE: driving messages and error messages.