3. Operands#
3.1. Operand FORMAT#
◊ FORMAT = 'MED'
Choice of the format of the file containing the field to be read.
Note:
Only the format MEDest operational today. However, with the combination of LIRE_TABLE then CREA_CHAMP/EXTR_TABLE * you can read a field stored in a table in the format ASTER
3.2. Operand TYPE_CHAM#
♦ TYPE_CHAM =/'NOEU_TEMP_R',
/”NOEU_DEPL_R”, /”ELGA_SIEF_R”, /etc…
This refers to the type of concept to be produced. The type name is constructed with the usual Code_Aster logic. The first four characters are “NOEU”, “ELEM”, “”, “ELNO”, “ELGA”, or “CART”. Then we find “_”. The following sequence defines the field type: “TEMP”, “”, “DEPL”, “SIEF”, etc… The name ends in “_R”, “_F”, or “_C” depending on the computer type of the values.
Example: “NOEU_TEMP_R”, “NOEU_DEPL_R”, “”, “ELGA_SIEF_R “etc…
Attention:
There is no consistency check! You can very well create a temperature concept by rereading a field that was a displacement when the file was written.
Note:
It may happen that values read from the file are not affected in the final field. For example, if we read a pressure field on TETRA4 elements when it must be assigned to edge meshes (because that is its nature), we will be notified by this type of alarm:
<A><LIRE_RESU> <LRCEME>
VALEURS NON AFFECTEES DANS THE CHAMP: 3699
VALEURS LUES DANS THE FICHIER * : 3699
3.3. Operand MAILLAGE#
♦ MAILLAGE = my
Name of the ASTER mesh on which the field to be read will be expressed.
3.4. Operand NOM_MED#
♦ NOM_MED = named
Name according to convention MED of the field to be read in the file. It is a 32-character string.
3.5. Operand MODELE#
◊ MODELE = mo
Name of the ASTER model on which the field to be read will be expressed. This operand is mandatory if the field to be read is an « element-wise » field (TYPE_CHAM =” ELxx_yyyy “)
3.6. Operand PROL_ZERO#
◊ PROL_ZERO = 'NON'/'OUI'
When creating a field « by elements », the structure of this field is imposed by Aster. For example, if a « ELNO » constraint field is created on a 3D model, all element nodes must have the components SIXX, SIYY,…, SIYZ. If the field MED you are reading does not have all the values expected by Aster, you must « invent » these missing values. The « invented » value will be 0. if PROL_ZERO =” OUI “, it will be « NaN » (Not a Number) if PROL_ZERO =” NON”
3.7. Selecting the time parameter NUME_ORDRE, NUME_PT, INST,, CRITERE, PRECISION#
If the field was written to the file without reference to a time parameter, nothing is to be mentioned in this read command. If not, you must specify what moment it is. This is done by designating an order number, a time step or a value of an archiving moment. Refer to document [U4.71.00] for details on these keywords.
3.8. Operand NOM_CMP_IDEM or NOM_CMP and NOM_CMP_MED#
The user must put NOM_CMP_IDEM or NOM_CMP in his command file.
3.8.1. Operand NOM_CMP_IDEM#
◊/NOM_CMP_IDEM = 'OUI'
Indicates that the components whose same name appears in the list of components of the field in the sense of Code_Aster must be read in the file MED.
3.8.2. Operands NOM_CMP, NOM_CMP_MED#
◊/♦ NOM_CMP = lcmp,
♦ NOM_CMP_MED = lcmpmed,
These two lists should be of the same length. We read the components listed in lcmpmed in the file MED, then we assign them to the components in the sense of Code_Aster, of the same rank in the lcmp list.
3.9. Operand NOM_MAIL_MED#
◊ NOM_MAIL_MED = nomamed
If this operand is absent, we look for the field linked to the first mesh in the file. This is what happens when the file contains only one mesh.
If the file contains several meshes, we specify here which one is associated with the field we want to read.
3.10. Operand UNITE#
◊ UNITE = unity
Logical unit number of the file, corresponds to the value provided in astk or using the DEFI_FICHIER command.
3.11. Operand INFO#
◊ INFO =/1, [DEFAUT]
/2,
If INFO is 2, some debugging impressions take place.
Otherwise nothing happens