3. Operands#

3.1. Operand OPERATION#

♦ OPERATION = define the type of operation to be performed with this operator:

“AFFE”: creation of a result data structure from fields.

It is up to the user to ensure the consistency of the fields provided to create the data structure and to check that they are based on the same model.

“PERM_CHAM”: reorganization of fuel assemblies,

“PROL_RTZ”: extension of a \(\mathrm{1D}\) field on an axisymmetric structure,

“PREP_VARC”: calculating the temperature in the layers of a shell starting from:

a function map created from a temperature given by a NAPPE or FORMULEdu type:

\(\mathit{temp}=f(\mathit{inst},\mathit{epais})\); \(\mathit{temp}=f(\mathit{inst},\mathit{excent})\); \(\mathit{temp}=f(\mathit{inst},x,y,z)\)

where:

◦ \(\mathit{inst}\) is the time,

◦ \(\mathit{epais}\) the thickness of the shell in \([-h/\mathrm{2,}h/2]\),

◦ \(\mathit{excent}\) is the position in the layer taking into account the eccentricity of the shell in \([\mathit{excent}-h/\mathrm{2,}\mathit{excent}+h/2]\).

◦ \(x,y,z\) coordinates of the center of gravity of the layer.

of a temperature calculated by aster with a shell model

(TEMP_MIL/TEMP_INF/TEMP_SUP),

“ASSE”: creating a result data structure from several structures of

result data put end to end.

“KUCV”: creation of transitory evolutions of loads second member of

evol_char or dyna_transpar type produces matrices assembled by kinematic fields of speeds and/or displacements.

“CONV_RESU”: creation of transitory evolutions of loads second member of type

evol_char or dyna_transpar conversion and combination of transient results.

“CONV_CHAR”: creation of transitory evolutions of loads second member of type

dyna_transpar assemblies of space-time loads such as plane waves or nodal forces.

The resultant data structure may be reentering for operation AFFE. She is still there for PERM_CHAM

For OPERATION = 'AFFE', existing fields can be replaced according to the value of the access variable INST using the values entered behind the keywords PRECISIONet CRITERE. When an existing field is replaced, the code issues an alarm message, otherwise the fields are stored at the end of the data structure.

3.2. Operand TYPE_RESU#

♦ TYPE_RESU

Type of the result data structure created.

In the case of an evol_varc result and an evaluation of a function field (time and space), the coherence between the nature of the function field and the name of the field given under NOM_CHAM is checked. For example, if the function field is of type NOEU_NEUT_F, the field name should be NEUT.

3.3. Operand NOM_CHAM#

♦ NOM_CHAM

Symbolic name of the field to be assigned. This name should be consistent with the data structure that was changed or created. For example, it can take the value 'DEPL', 'VARI_ELGA', '', '', 'TEMP', 'FLUX_ELNO', 'IRRA', etc.

In the case of an evol_varc result and an evaluation of a function field (time and space) Code_Aster checks the consistency between the nature of the function field and the name of the field given under name_cham. For example, if the function field is of type NOEU_NEUT_F, the field name should be NEUT.

In the case of a “EVOL_CHAR” result, the fields that can be created are:

PRES	Pressure fields \((N/{m}^{2})\), component \(\mathit{PRES}\)
FVOL_3D	Volume force fields \((N/m\mathrm{³})\), components \(\mathit{FX}\), \(\mathit{FY}\), \(\mathit{FZ}\)
FVOL_2D	Volume force fields \((N/m\mathrm{³})\), components \(\mathit{FX}\), \(\mathit{FY}\)
FSUR_3D	Surface force fields \((N/{m}^{2})\), components \(\mathit{FX}\), \(\mathit{FY}\), \(\mathit{FZ}\)
FSUR_2D	Surface force fields \((N/{m}^{2})\), components \(\mathit{FX}\), \(\mathit{FY}\)
VITE_VENT	Fields at wind speed knots \((m/s)\), components \(\mathit{DX}\), \(\mathit{DY}\), \(\mathit{DZ}\)
T_ EXT	Outdoor temperature map, component \(\mathit{TEMP}\)
COEF_H	Exchange coefficient card, component \(H\)
FLUN	Normal flow map, component \(\mathit{FLUN}\)
FORC_NODA	Fields at nodes, components \(\mathit{FX}\), \(\mathit{FY}\), \(\mathit{FZ}\)

3.4. Operand COMPORTEMENT#

The syntax for this keyword that is common to several commands is described in document [U4.51.11]. This keyword must be entered in the case of non-linear mechanics because it is used to repeat the calculation in STAT_NON_LINE and DYNA_NON_LINE to check the compatibility of behaviors (number of internal variables in particular).

During operation AFFEdans the case of non-linear mechanics,

without reuse, a new result data structure will be created with the behavior entered. If COMPORTEMENTn is not specified, the behavior taken by default is elastic (COMPORTEMENT =” ELAS “) in small deformations (RELATION =” PETIT”).
Use reuse to add or replace fields in the result. If COMPORTEMENTest is entered, you replace your behavior map for all the moments; otherwise, you keep the behavior for the existing moment and you recover the behavior of the previous moment for the moment non-existent (elastic in small deformations without previous moment).

At the end of operation AFFE, we check, for each moment, the coherence between its behavior map and the number of internal variables (see keyword VERI_VARI). Despite the inconsistencies, authorized cases allow this field (VARI_ELGA) to be used again in a non-linear calculation, and the calculation should go well (automatic correction in the operator).

3.5. Operand VERI_VARI#

◊ VERI_VARI = /” OUI “[DEFAUT]

This keyword is used to check the consistency between the size of VARI_ELGA fields and the definition of non-linear behavior.

If there are differences, alarms are issued.

3.6. Operands EXCIT#

For a result from the CREA_RESU command to be usable by other commands, it is necessary to build and fill in the data structure by specifying the associated loads. The keyword factor EXCIT is used for TYPE_RESU: EVOL_ELAS, EVOL_NOLI, and EVOL_THER. Refer to the respective documents U4.51.01, U4.51.01, U4.51.03 and U4.54.01.

3.7. Keyword CHAM_GD#

3.7.1. Operand CHAM_GD#

♦ CHAM_GD = chno

chno is:

either a function fiel_no created by the crea_champ command [U4.72.04] and in this case we evaluate the function for each node and for each moment defined behind list_inst or inst we create a real fiel_no,
either a fiel_no or a real cham_elem created by the crea_champ command (word AFFE or EXTR) and this field is duplicated as many times as the list of moments defined behind LIST_INST or INST requires it.

3.7.2. Operands MODELE, CHAM_MATER, CARA_ELEM, CHARGE#

These optional operands are used to allow the filling of result data structures. This filling is essential in the case where the CREA_RESU command is called by MACRO_ELAS_MULT to then use the post-processing commands that will look for this information in the data structure.

◊ MODELE = me,

The name of the model whose elements are being calculated.

◊ CHAM_MATER = chmat,

The name of the material field.

◊ CARA_ELEM = character,

Name of the characteristics of the structural elements (beam, shell, discrete,…) if they are used in the model. When OPERATION takes the value PREP_VARC, we get the components EPAIS and COQU_NCOU from it.

◊ CHARGE = tank,

Name of a char_meca concept produced by AFFE_CHAR_MECAou by by AFFE_CHAR_MECA_F [:ref:`U4.44.01 <U4.44.01>`] from the mo model. We can also give the name of a "kinematic load" (type char_cine_meca) resulting from the operators AFFE_CHAR_CINEou AFFE_CHAR_CINE_F [:external:ref:`U4.44.03 <U4.44.03>`].

3.7.3. Operands LIST_INST/LIST_FREQ/NUME_INIT/NUME_FIN#

List of reals produced by DEFI_LIST_REEL [U4.34.01].

◊ NUME_FIN = nutcase

The calculation times are those defined in the litps concept taken between the nini and the nine times in the instant number. In the absence of the NUME_FIN keyword, it is the size of the real list that is taken into account.

3.7.4. Operands INST#

♦ INST = the link

List of reals: list of times for which the function_no field will be evaluated, or the real_no field will be assigned.

Note:

The order number created in the concept result is either retrieved from the value of the access variable INSTlorsque it is present, or assigned to the immediately higher maximum value.

3.7.5. Operands FREQ#

In the case MODE_MECA/MODE_MECA_C:

◊ FREQ = freq

Frequency value.

This operand is optional, it allows, in the case of a reentering concept, to be able to declare another field for the same mode number (NUME_MODE) without having to provide the frequency.

Note that if the user declares a field (for example EFGE_ELNO) for a NUME_MODE for which another field already exists with an associated frequency (for example DEPL) and if he enters operand FREQ with a different value, the concept cannot be treated by COMB_SISM_MODAL.

In other cases:

♦ FREQ = lfreq

List of reals: list of frequencies for which the function_no field will be evaluated, or the real_no field will be assigned.

Note:

The order number created in the concept result is either retrieved from the value of the access variable FREQlorsque it is present, or assigned to the immediately higher maximum value.

3.7.6. Operands PRECISION/CRITERE#

These operands make it possible to refine access by real time or frequency access variables.

I PRECISION =//prec [R]

/0.0 or 1.0D-3 or 1.0D-6 [DEFAUT]

This keyword indicates that we are looking for all fields whose time (respectively the frequency) of which is in the « inst ± prec » interval (confer CRITERE).

In the case where OPERATION = “AFFE”, the default value prec is set to 0.0 to avoid overwriting a field whose value at the moment is close to the one being treated. the instant provided is not used to retrieve a field from the data structure, it is an attribute that must be associated with the field that is stored. In general, the fields that are stored all correspond to different times.

In the very rare case where the user wants to overwrite one of the fields contained in the data structure, he should use the PRECISION keyword. An alarm message then indicates the name of the fields concerned with their storage times, and the precision provided by the user:

I CRITERE =/'RELATIF' [DEFAUT]

/”ABSOLU”

“RELATIF”: the search interval is: [inst (1 - prec), inst (1 + prec)]

“ABSOLU”: the search interval is: [inst - prec, inst + prec].

3.7.7. Operands NUME_MODE/TYPE_MODE#

In the case MODE_MECA/MODE_MECA_C:

♦ NUME_MODE = number

An integer designating the mode number in the case TYPE_RESU =” MODE_MECA “.

In case FOURIER_ELAS:

◊ NUME_MODE = num

Integer designating the Fourier harmonic number of the field stored in a fourier_elas concept.

◊ TYPE_MODE =/'SYME'

/”ANTI” /”TOUS”

Defines the type of stored Fourier mode.

“SYME”:	symmetric harmonic
“ANTI”:	antisymmetric harmonic
“TOUS”:	symmetric and antisymmetric harmonic

3.7.8. Operand AXE#

Available in case MODE_MECA/MODE_MECA_C only:

◊ AXE =/'X'

/”Y” /”Z”

Allows you to define a direction for a given order number so that the output concept can be provided to the MODE_CORR operand of COMB_SISM_MODAL [U4.84.01].

3.7.9. Operand NOM_CAS#

♦ NOM_CAS = name

Character string defining the field access variable stored in a mult_elas concept.

3.7.10. Operands MATR_RIGI/MATR_MASS#

In case TYPE_RESU =” MODE_MECA “,” DYNA_HARMO “, or” DYNA_TRANS “:

◊ MATR_RIGI = matr_k

Stiffness matrix corresponding to the stored fields.

◊ MATR_MASS = matr_m

Mass matrix corresponding to the stored fields.