1. Code_Aster command syntax reminders#

The command language and its supervisor are fully described in document [U1.03.01]. Here we recall some notions about the syntax of Code_Aster commands.

In Code_Aster, by the generic term of commands, we mean both operators, procedures and command language macro commands. An operator provides a product concept typed (by the operator) and named by the user. A procedure does not generate a product concept, it performs actions such as impressions or resource allocations.

In the example below, we recall the vocabulary that is used in the description of the commands.

_images/Shape1.gif

Terminology Aster

An operand is therefore the set made up of a keyword and its argument. However, in command documentation, the operands of an operator or procedure are often referred to by the name of their keyword. For example: RHO, a simple keyword, or ELAS, a factor keyword.

The term product concept is generic for all operators, it is the result of the operator’s work.

Here in example DEFI_MATERIAU, the data structure of the master type (material) was created, named beton by the user. It groups together the names (keyword E, NU, RHO) and the values (arguments 3.4E10, 0.25, 2500.) of the mechanical elastic characteristics (keyword factor ELAS) of the material.

The concept term result type applies to the outputs of calculation operators, that is to say fields of physical quantities (displacements, temperatures, stresses, forces, modes, etc…) on the nodes or on the meshes at different times or for different frequencies.

The resulting concept generally includes subtypes.