1. .export files#

The.export files associated with Code_Aster test cases contain the runtime parameters usually provided by the astk interface and the various files and data directories used. Only one parameter per line is provided. These various parameters are not positional, the name obeys a convention and makes it possible to distinguish the different values. Here is the list of possible keywords:

The run-time parameters are described in the following form:

P*parameter_nameparameter_value*

  • time_limit: time in seconds of the work submitted, this value is passed on the command line.

  • memory_limit: memory for Aster calculation. It should be specified in MB.

  • testlist: list where the test belongs. Each test must belong to one of the two sequential or parallel lists, and one of the two verification or validation lists. For the tests in the validation list, they must also mention the project concerned: code, performance, seism, fracture (non-exhaustive list).

  • mpi_nbCPU: total number of processors for parallelism MPI.

  • mpi_nbnode: number of nodes for parallelism MPI (where the nproc_mpi processors will be distributed).

  • ncpus: number of processors for OpenMP parallelism.

  • max_base: initial limit on the size of the bases used during the calculation, the associated value must be indicated in MB. If necessary, it will be automatically resized during the calculation.

  • expected_diag: expected diagnosis for test cases that are deliberately in error (we check that the test stops with a diagnosis of the same severity).

The data files required to pass the test are described in the form:

F*extensionfilename* D*logical_unit_number*

The data directories required to pass the test are described in the form:

R*extension_directory_name* D 0