Code_Aster
®
Version
8.1
Titrate:
Utilities for the Structures of data
Date:
01/12/05
Author (S):
J. PELLET
Key
:
D6.07.05-B
Page
:
1/10
Data-processing manual of Description
D6.07 booklet: - HT-66/05/003/A
Organization (S):
EDF-R & D/AMA
Data-processing manual of Description
D6.07 booklet: -
Document: D6.07.05
Utilities for the Structures of data
Summary:
One presents in this document some utilities of operative general interest on structures of data:
copy, destruction, existence, impression.
The utility
DISMOI
is used to extract “scalar” information (1 entirety or 1 text) in a Structure of
Data.
Code_Aster
®
Version
8.1
Titrate:
Utilities for the Structures of data
Date:
01/12/05
Author (S):
J. PELLET
Key
:
D6.07.05-B
Page
:
2/10
Data-processing manual of Description
D6.07 booklet: - HT-66/05/003/A
1 Routine
COPISD
SUBROUTINE COPISD
(TYPESD, BASES, SD1, SD2)
drank:
to duplicate a structure of data (SD1) under another name (SD2).
SD2 will have the same contents as SD1.
IN TYPESD
K *
type of the 2 structures of data SD1 and SD2.
types allowed today:
“CHAMP_GD”, “FUNCTION”, “CHAM_NO_S', “CHAM_ELEM_S', “TABLE”,
“RESULT”, “VARI_COM”, “CORRESP_2_MAILLA”, “MESH”
IN K1 BASE
“G”/“V”/“It: name of the base where SD2 will be created
IN
JXIN
SD1 K *
name of the SD
SD1
IN
JXOUT
SD2 K *
name of the SD
SD2
2 Routine
IDENSD
LOGICAL FUNCTION IDENSD
(TYPESD, SD1, SD2)
drank:
to test the identity of the contents of 2 structures of data
SD1
and
SD2
IN TYPESD
K *
type of the 2 structures of data to be compared.
type allowed today:
“PROF_CHNO”
IN
JXIN
SD1 K *
name of the SD
SD1
IN
JXIN
SD2 K *
name of the SD
SD2
OUT IDENSD L
.
TRUE
. : 2 SD
SD1
and
SD2
are identical
.
FALSE
. : 2 SD
SD1
and
SD2
are different
3 Routine
EXISD
SUBROUTINE EXISD
(TYPESD, NOMSD, IRET)
drank:
to answer the question: “there exists a structure of data of the type
TYPSD
and of
name
NOMSD? “
.
IN TYPESD
K *
type of the structure of data to be tested.
types allowed today:
“FIELD”, “CHAM_NO_S', “CHAM_ELEM_S', “TABLE”, “RESULT”,
“CARD”, “RESUELEM”, “CHAM_NO”, “CHAM_ELEM”, “MESH”,
“MODEL”, “LIGREL”, “FUNCTION”, “MATR_ASSE”, “NUME_DDL”
IN
JXIN
NOMSD K *
name of the SD to be tested
OUT IRET
I
0: the structure of data does not exist
1: the structure of data exists
Code_Aster
®
Version
8.1
Titrate:
Utilities for the Structures of data
Date:
01/12/05
Author (S):
J. PELLET
Key
:
D6.07.05-B
Page
:
3/10
Data-processing manual of Description
D6.07 booklet: - HT-66/05/003/A
4 Routine
DETRSD
SUBROUTINE DETRSD
(TYPESD, NOMSD)
drank:
to destroy a structure of data of the type
TYPSD
and of name
NOMSD
.
I.e. to destroy all the objects JEVEUX which make it up.
IN TYPESD
K *
type of the structure of data to be tested.
types allowed today:
“NUME_DDL” “PROF_CHNO”
“MATR_ASSE” “VECT_ASSE”
“MATR_ELEM” “VECT_ELEM”
“VARI_COM” “FUNCTION”
“TABLE” “DEFI_CONT” “RESO_CONT”
“SOLVEUR” “CORRESP_2_MAILLA” “CLOUD”
“CHAM_NO_S' “CHAM_ELEM_S' “LIGREL”
“CHAM_NO” “CHAM_ELEM” “CARD”
“CHAMP_GD” “RESULT” “MESH”
IN
JXIN
NOMSD K *
name of the SD to be destroyed
5 Routine
IMPRSD
SUBROUTINE IMPRSD
(TYPESD, NOMSD, FICH, TITLE/TITER)
drank:
to print “lisiblement” a structure of data
IN TYPESD
K *
type of the structure of data to be tested.
types allowed today:
“FIELD” “CHAMP_S'
IN
JXIN
NOMSD K *
name of the SD to be printed
IN FICH K *
name of the file for the impression:
“MESSAGE”
,
“RESULT”
,…
IN TITLE/TITER K *
titrate given to the impression.
6 Routine
UTIMSD
SUBROUTINE UTIMSD
(FICH, LEVEL, LATTR, LCONT, SCH1, IPOS, BASES)
drank:
to print “dirtily” a structure of data.
i.e. to print the “rough” contents of the objects JEVEUX which compose it.
Actually, one does not treat really structures of data: all are sought
the objects JEVEUX whose name contains a certain character string.
But it is that in general, all the objects of a SD have names starting
consequently channel.
IN FICH K *
name of the file for the impression:
“MESSAGE”
,
“RESULT”
,…
IN LEVEL
I
desired level of impression:
0: impression of the only name of the objects.
1: for the collections, one will print only the 10 1st objects.
2: all the objects of collection are printed
- 1: one prints a “summary” of the objects: only one line per object.
IN LATTR L
.
TRUE
. : one prints the attributes of objects JEVEUX
.
FALSE
. : one does not print the attributes of objects JEVEUX
IN LCONT L
.
TRUE
. : one prints the values of objects JEVEUX
.
FALSE
. : one does not print the values of objects JEVEUX
IN SCH1 K *
character string allowing to select the objects to be printed.
Code_Aster
®
Version
8.1
Titrate:
Utilities for the Structures of data
Date:
01/12/05
Author (S):
J. PELLET
Key
:
D6.07.05-B
Page
:
4/10
Data-processing manual of Description
D6.07 booklet: - HT-66/05/003/A
The statement of this channel is very important (its length), because it
condition the number of found objects.
if
SCH1=' TOTO'
but that
SCH1
is declared
K19
, only the objects will be printed
starting with
“LOUSE”
follow-up of 15 white.
IN IPOS I
position to which one will seek the 1st character of
SCH1
.
IN K1 BASE
name of the base JEVEUX on which one seeks the objects.
“G”, “V”,…
if '': one seeks on all the open bases.
Exemple1:
CAL UTIMSD (“RESULT”, 2, .FALSE., .TRUE., FIELD (1:19), 1, “V”)
fact the “dump” of the named field
FIELD
and which is on the VOLATILE basis. The attributes are not printed
objects JEVEUX.
Exemple2:
CAL UTIMSD (“RESULT”, 0, .FALSE., .FALSE., “.DESC”, 20, '')
writing the name of all the objects whose name contains the channel '.
DESC'
in position 20.
7 Routine
DISMOI
7.1 Principle
This routine must avoid multiplying the sequences of programming necessary to recover
information (entirety or text) in a Structure of Data (SD).
Example:
·
the name of the mesh associated with one
field
,
·
the number of equations of one
nume_ddl
,
·
…
It is to some extent a form of “
JELIRA
“on the SD.
To recover the name (
MA
) of the mesh associated with the field (
CH
), one will make:
CAL
DISMOI (“F”, “NOM_MAILLA”, “CH”, “FIELD”, IBID, MA, IER)
Note:
·
One can extend this routine to “objects” which are not really SD. It is enough that
one can name the object and associate a type to him. It is for example the case of
sizes
,
type_elem
and
phenomenon
,
·
certain SD are not really named because they are single. It is for example
the case of the catalog of finite elements (
“&CATA”
cf [D4.04.01]) in this case the name of
the object is unutilised.
Code_Aster
®
Version
8.1
Titrate:
Utilities for the Structures of data
Date:
01/12/05
Author (S):
J. PELLET
Key
:
D6.07.05-B
Page
:
5/10
Data-processing manual of Description
D6.07 booklet: - HT-66/05/003/A
7.2 Syntax
of call
cal DISMOI (C_M, question, nom_SD, type_SD, rep_i, rep_c, ier)
CM
K1
character of identification of the type of message which is transmitted to
UTMESS
(
“F”
allows to stop the execution in the event of error),
question K *
key word specifying the request,
nom_SD
K *
name of a SD,
type_SD K *
key word specifying the type of the structure of data:
nom_SD
,
rep_i
I
answer (when the answer is whole),
rep_c
K *
answer (when the answer is a character string),
ier
I
code return of error,
ier = 0 whole is well
ier
impossible request.
In a “normal” use (out of the routines of “title/titer”): one puts a question which must have one
answer. One makes then:
cal
DISMOI (“F”, question, nom_SD, type_SD, rep_i, rep_c, ibid)
and one does not test
Ibid
.
If the request fails, the stop is brutal
(“F”)
but that translated a programming error.
7.3
List types recognized by
DISMOI
Name of the type
Length
Routine
“CARD” K19
DISMCA
“CATALOG” K0
DISMCT
“CHAM_ELEM” or “RESUELEM”
K19
DISMCE
“CHAM_MATER” K8
DISMCM
“CHAM_NO” K19
DISMCN
“FIELD” K19
DISMCP
“LOAD” K8
DISMCH
“SIZE” K8
DISMGD
“UNKNOWN” K19
DISMIC
“INTERF_DYNA” K14
DISMLI
“LIGREL” K19
DISMLG
“MACR_ELEM_STAT” K8
DISMML
“MESH” K8
DISMMA
“MATR_ASSE” K19
DISMMS
“MATR_ELEM” or “VECT_ELEM” K8
DISMME
“MODEL” K8
DISMMO
“NUME_EQUA” K19
DISMNE
“NUME_DDL” K14
DISMNU
“PHENOMENON” K16
DISMPH
“RESULT” K8
DISMRS
“TYPE_ELEM” K16
DISMTE
“TYPE_MAILLE” K8
DISMTM
Code_Aster
®
Version
8.1
Titrate:
Utilities for the Structures of data
Date:
01/12/05
Author (S):
J. PELLET
Key
:
D6.07.05-B
Page
:
6/10
Data-processing manual of Description
D6.07 booklet: - HT-66/05/003/A
Note:
·
the length of the names of typified objects kN is indicative: the routine
DISMOI
supplements (or
truncate) the name given by the user according to the associated type,
·
the name of the routines
DISMXX
associated the various types is given (into 3
ème
column)
to allow programmers to add new possibilities,
·
Regulate: Losque one uses
DISMOI
, it is always necessary to call
DISMOI
and never them
specific routines
DISMXX
.
7.4
List possible questions
In the table below, one gives for each question:
·
the heading of the question (text in capital letters between quotes),
·
the type of the result of the question:
I, K3, K8,…
,
·
an explanation of the answer possible.
“BESOIN_MATER”
K3
“YES”/“NOT”
if it
MODEL
require one
CHAM_MATER
“CALC_RIGI”
K3
“YES”/“NOT”
Allows to know if one type_element can calculate “rigidity” (and thus if it is
a “main” element of modeling and not an element of “edge”)
“CARA_ELEM” K8
name of
CARA_ELEM
subjacent.
``: there is not
CARA_ELEM
subjacent.
“CHAM_MATER” K8
name of
CHAM_MATER
subjacent.
``: there is not
CHAM_MATER
subjacent.
“COEF_MULT” I
value of the “multiplying” coefficient of the number of values of
CHAM_ELEM
(for
the variables intern)
“DIM_GEOM” I
2/3:
dimension of the problem: 2D or 3D.
on the types:
type_elem
,
ligrel
,
model
the answer can be:
1: all them
type_elem
subjacent are 1D (X)
2: all them
type_elem
subjacent are 2D (X, Y)
3: all them
type_elem
subjacent are 3D (X, Y, Z)
if it coexists several
type_elem
of different size:
120: mix 1D and 2D
023: mix 2D and 3D
103: mix 1D and 3D
123: mix 1D, 2D and 3D
if there are static substructures,
one adds 1000 while waiting
to know their real dimensions (1,2, or 3)
who cannot be found today.
on the type
mesh
:
the answer is:
2: the mesh aster read is of type “
COOR_2D
“
3: the mesh aster read is of type “
COOR_3D
“
This value is that read in the file of mesh:
COOR_2D
or
COOR_3D
.
Caution: it is not because
COOR_3D
that the mesh is really 3D.
“ELAS_F_HYDR”
K3
“YES”/'NOT
if it
CHAM_MATER
use for its behavior
ELAS_XXX
at least a function
hydration
Code_Aster
®
Version
8.1
Titrate:
Utilities for the Structures of data
Date:
01/12/05
Author (S):
J. PELLET
Key
:
D6.07.05-B
Page
:
7/10
Data-processing manual of Description
D6.07 booklet: - HT-66/05/003/A
“ELAS_F_SECH”
K3
“YES”/'NOT
if it
CHAM_MATER
use for its behavior
ELAS_XXX
at least a function
drying
“ELAS_F_TEMP”
K3
“YES”/'NOT
if it
CHAM_MATER
use for its behavior
ELAS_XXX
at least a function
temperature
“ELEM_VOLU_QUAD”
K3
“YES”/“NOT”/“MEL”:
“YES”
: All elements of
MODEL
are mechanical, voluminal and
quadratic.
“NOT”
: All elements of
MODEL
are mechanical, voluminal and linear.
“MEL”
: There are elements of
MODEL
mechanics, voluminal linear and
the other quadratic ones.
“EXI_AMOR_ALPHA” K3 “YES”
/
'NOT
if it
cham_mater
refers has at least a material which has
CMP
“
AMOR_ALPHA
“
“EXI_AMOR_HYST”
K3
“YES”/“NOT”
if it
cham_mater
refers has at least a material which has it “
CMP
“
“
AMOR_HYST
“
“EXI_COQ1D' K3
“YES”/“NOT”
if it
MODEL
contains finite elements of modelings
COQU_C_PLAN
or
COQU_D_PLAN
or
COQU_AXIS
“EXI_COQ 3D”
K3
“YES”/“NOT”
if it
MODEL
contains finite elements of modelings
COQU_3D
“EXI_ELEM” K3
“YES”/“NOT”
if it
MODEL
finite elements (it contains can only contain
static substructures)
“EXI_ELTVOL” K3
“YES”/“NOT”
if it
MODEL
contains “voluminal” elements
“EXI_HYDRAT” K4
“NOT”
: the mechanical load does not contain a hydration
“EVOL”
: the mechanical load contains one
evol_ther
of hydration
“CHGD”
: the mechanical load contains a field of hydration
“EXI_PLAQUE” K3
“YES”/“NOT”
if it
MODEL
contains elements of plate: modelings
DST
/
DKT
or
Q4G
“EXI_POUX” K3
“YES”/“NOT”
if it
MODEL
contains elements of beam “to the LICE”.
“EXI_RDM” K3
“YES”/“NOT”
if it
MODEL
contains elements of R.D. Mr. (beam, plate or
hull)
“EXI_SECHAG” K4
“NOT”
: the mechanical load does not contain drying
“EVOL”
: the mechanical load contains one
evol_ther
of drying
“CHGD”
: the mechanical load contains a field of drying
“EXI_TEMPER” K4
“NOT”
: the mechanical load does not contain a temperature
“EVOL”
: the mechanical load contains one
evol_ther
of temperature
“CHGD”
: the mechanical load contains a field of temperature
“EXI_THM_CT” K3
“YES”/“NOT”
if it
MODEL
contains elements of modelings
XXX_THM_CT
“EXI_THM_VR” K3
“YES”/“NOT”
if it
MODEL
contains elements of modelings
XXX_THM_VR
“EXI_TUYAU” K3
“YES”/“NOT”
if it
MODEL
elements “pipe contains”
“MODELING” K16
name of
MODELING
associated one
MODEL
.
If there are several
MODELINGS
in
MODEL
, the answer is
''
“NB_CHAMP_MAX” I
raising number of the sequence numbers of a SD
RESULT
.
“NB_CHAMP_UTI” I
numbers sequence numbers used of a SD
RESULT
.
“NB_CMP_MAX” I
raising component count of one
SIZE
.
“NB_DDLACT” I
numbers
DDLS
credits = a number of
DDLS
physics minus the number of
stresses kinematics.
“NB_EC” I
a number of entireties necessary to code a size:
nb_ec =
nb_cmp_max/30
“NB_EQUA” I
a number of equations of a linear system.
“NB_GREL” I
numbers “
GRELS
“in
LIGREL
.
“NB_MA_MAILLA” I
numbers
MESHS
MESH
.
“NB_MA_SUP” I
numbers
MESHS
additional of
LIGREL
.
Code_Aster
®
Version
8.1
Titrate:
Utilities for the Structures of data
Date:
01/12/05
Author (S):
J. PELLET
Key
:
D6.07.05-B
Page
:
8/10
Data-processing manual of Description
D6.07 booklet: - HT-66/05/003/A
“NB_NL_MAILLA” I
numbers
NODES
LAGRANGE of
MESH
. this number can be nonnull if
the mesh contains
SUPER_MAILLES
.
“NB_NO_MAILLA” I
numbers
NODES
MESH
.
“NB_NO_MAX” I
raising number of
NODES
TYPE_MAILLES
.
“NB_NO_SS_MAX” I
numbers maximum nodes for one
SUPER_MAILLE
MESH
.
“NB_NO_SUP” I
numbers
NODES
additional of
LIGREL
.
“NB_SM_MAILLA” I
numbers
SUPER_MAILLES
MESH
.
“NB_SS_ACTI” I
a number of active substructures in one
MODEL
.
“NB_TYPE_MA” I
numbers
TYPE_MAILLES
in the catalog.
“NBNO_TYPMAIL” I
a number of nodes of one
type_maille
“NOM_GD” K8
name of
SIZE
.
“NOM_GD_SI” K8
name of
SIZE
simple partner.
“NOM_LIGREL” K19
name of
LIGREL
.
“NOM_MAILLA” K8
name of
MESH
.
“NOM_MODE_CYCL” K8
name of
MODE_CYCL
.
“NOM_MODELE” K8
name of
MODEL
.
“NOM_NUME_DDL” K14
name of
NUME_DDL
.
“NOM_OPTION” K16
name of
OPTION
(catalogs) calculation.
“NOM_TYPMAIL” K8
name of one
type_maille
“NU_CMP_LAGR” I
number of the component “
LAGR
“in one
SIZE
.
“NUM_GD” I
number of
SIZE
.
“NUM_GD_SI” I
number of
SIZE
simple partner.
“NUM_TYPMAIL” I
number of one
type_maille
“NUME_EQUA” K19
name of the SD
NUME_EQUA
associated.
“PARA_INST” K3
“YES”
: if
CARD
is a card of
FUNCTIONS
depending on time
'': if not
“PHENOMENON” K16
name of
PHENOMENON
associate one
MODEL
.
PHENOMENON
is single in one
MODEL
)
“PROF_CHNO” K19
name of
PROF_CHNO
subjacent.
“SUR_OPTION” K16
name of the option “user” who “chapeaute” possibly the real option (i.e of
catalog) associated A the object. ex:
“CHAR_MECA”
for
“CHAR_MECA_PESA_R”
“THER_F_INST” K3
“YES”/“NOT”
if it
cham_mater
use for its behavior
THER_XXX
with
less one function of time
“STANDARD” K16
type of a concept of which one knows nothing ('
INCONNU'
):
'FUNCTION
,
“CHAM_ELEM”
,
'TABLE '', “EVOL_ELAS”,…
“TYPE_CHAMP” K4
type of the field
“CART”: CARD
“RESL”: RESUELEM
“NOEU”: CHAM_NO
“ELGA”: CHAM_ELEM
at the points of GAUSS
“ELNO”: CHAM_ELEM
with the nodes
“TYPE_CHARGE” K7
type of one
CHARGE
“MECA_RE”
: real mechanics (
AFFE_CHAR_MECA
)
“MECA_FO”
: mechanics function (
AFFE_CHAR_MECA_F
)
“THER_RE”
: thermics real (
AFFE_CHAR_THER
)
“THER_FO”
: thermics function (
AFFE_CHAR_THER_F
)
“ACOU_RE”
: real accoustics (
AFFE_CHAR_ACOU
)
“ACOU_FO”
: accoustics function (
AFFE_CHAR_ACOU_F
)
“TYPE_MATRICE” K7
type of the matrices
“SYMETRI”
: all the matrices are symmetrical
“NON_SYM”
: there is at least a nonsymmetrical matrix.
'': the subjacent size is not of type “stamps”
“TYPE_RESU” K16
type of one
RESULT
:
“EVOL_THER”
,
“EVOL_ELAS”
,
EVOL_NOLI'
,…. or
“FIELD”
Code_Aster
®
Version
8.1
Titrate:
Utilities for the Structures of data
Date:
01/12/05
Author (S):
J. PELLET
Key
:
D6.07.05-B
Page
:
9/10
Data-processing manual of Description
D6.07 booklet: - HT-66/05/003/A
“TYPE_SCA” K3
scalar type
“R”: real * 8
“I”: integer
“It: complex * 16
“K8”: character * 8
“K16”: character * 16
“TYPE_SUPERVIS”
K16
type what would give the supervisor to one
SD
:
“CHAM_NO_DEPL_R”
,
“CHAM_ELEM_EPSI_R”
,…
“TYPE_TYPMAIL” K4
type of one
type_maille
:
/“POIN”/“LIGN”/“SURFING”
or
“VOLU”
“Z_CST”
K3
“YES”
/
“NOT”
“YES”
: if all nodes of
MESH
have the same one exactly “
Z
“(3
ème
co-ordinate)
“NOT”
: if not
7.5
Count cross of the possibilities
In the table below, one gives for each type of Structure of Data:
·
the theoretical length of the names of the objects of this type,
·
the list of the questions which one can put on this type.
“CARD”
K19
“NOM_GD”
“NOM_MAILLA”
“PARA_INST”
“TYPE_CHAMP”
“CATALOG” K0
“NB_NO_MAX”
“NB_TYPE_MA”
“FIELD”
K19
“NOM_GD”
“NOM_LIGREL”
“NOM_MAILLA”
“NOM_MODELE”
“NOM_OPTION”
“NUM_GD”
“TYPE_CHAMP”
“TYPE_SUPERVIS”
“CHAM_ELEM”
or “RESUELEM”
K19
“COEF_MULT”
“NOM_GD”
“NOM_LIGREL”
“NOM_MODELE”
“NOM_OPTION”
“NOM_MAILLA”
“TYPE_MATRICE” “TYPE_SCA” “TYPE_CHAMP”
“TYPE_SUPERVIS”
“CHAM_MATER” K8
“ELAS_F_TEMP”
“ELAS_F_HYDR”
“ELAS_F_SECH”
“EXI_AMOR_ALPHA” “EXI_AMOR_HYST”
“THER_F_INST”
“CHAM_NO” K19
“NB_EQUA”
“NOM_MAILLA”
“NOM_NUME_DDL”
“NUM_GD”
“PROF_CHNO”
“TYPE_CHAMP”
“TYPE_SUPERVIS” “NOM_GD”
“LOAD” K8
“EXI_TEMPER”
“EXI_HYDRAT”
“EXI_SECHAG”
“NOM_LIGREL”
“NOM_MAILLA”
“NOM_MODELE”
“PHENOMENON”
“TYPE_CHARGE”
“SIZE” K8
“NB_CMP_MAX”
“NB_EC”
“NOM_GD_SI”
“NUM_GD”
“NUM_GD_SI”
“NU_CMP_LAGR”
“TYPE_MATRICE”
“TYPE_SCA”
“UNKNOWN” K19
“STANDARD”
“INTERF_DYNA”
K14
“NB_CMP_MAX”
“NB_EC” “NOM_MAILLA”
“NOM_MODE_CYCL” “NOM_NUME_DDL”
“NUM_GD”
“LIGREL”
K19
“DIM_GEOM” “EXI_ELEM” “NB_GREL”
“NB_MA_SUP”
“NB_NO_MAILLA”
“NB_NO_SUP”
“NB_SS_ACTI”
“NOM_MAILLA”
“NOM_MODELE”
“PHENOMENON”
“NB_MA_MAILLA”
“MACR_ELEM_STAT” K8
“NOM_MAILLA”
“NOM_MODELE” “NOM_NUME_DDL”
“MESH” K8
“DIM_GEOM”
“NB_MA_MAILLA”
“NB_NL_MAILLA”
“NB_NO_MAILLA” “NB_NO_SS_MAX” “NB_SM_MAILLA”
“Z_CST”
“MATR_ASSE” K19
“CARA_ELEM”
“CHAM_MATER”
“NB_EQUA”
“NOM_GD_SI”
“NOM_MAILLA” “NOM_MODELE”
“NOM_NUME_DDL”
“NUM_GD_SI” “PHENOMENON”
“SUR_OPTION”
“TYPE_MATRICE”
Code_Aster
®
Version
8.1
Titrate:
Utilities for the Structures of data
Date:
01/12/05
Author (S):
J. PELLET
Key
:
D6.07.05-B
Page
:
10/10
Data-processing manual of Description
D6.07 booklet: - HT-66/05/003/A
“MATR_ELEM”
or “VECT_ELEM”
K8 “CARA_ELEM”
“CHAM_MATER”
“NB_SS_ACTI”
“NOM_MAILLA”
“NOM_MODELE” “PHENOMENON”
“SUR_OPTION”
“TYPE_MATRICE”
“MODEL” K8
“BESOIN_MATER”
“DIM_GEOM”
“ELEM_VOLU_QUAD”
“EXI_COQ1D'
“EXI_COQ 3D”
“EXI_ELEM”
“EXI_PLAQUE”
“EXI_POUX” “EXI_RDM”
“EXI_THM_CT”
“EXI_TUYAU”
“EXI_ELTVOL”
“EXI_THM_VR”
“MODELING”
“NB_MA_MAILLA”
“NB_NL_MAILLA” “NB_NO_MAILLA” “NB_NO_SS_MAX”
“NB_SM_MAILLA” “NB_SS_ACTI”
“NOM_LIGREL”
“NOM_MAILLA”
“PHENOMENON”
“Z_CST”
“NUME_DDL” K14
“NB_EQUA”
“NOM_GD”
“NOM_MODELE”
“NUM_GD_SI” “PHENOMENON” “NOM_MAILLA”
“PROF_CHNO”
“NUME_EQUA” K19
“NOM_MAILLA”
“PHENOMENON” K8
“NOM_GD”
“NUM_GD”
“RESULT” K8
“NB_CHAMP_MAX”
“NOM_MAILLA”
“TYPE_RESU”
“TYPE_ELEM”
K16
“DIM_GEOM” “MODELING”
“PHENOMENON”
“TYPE_TYPMAIL” “NBNO_TYPMAIL”
“NOM_TYPMAIL”
“NUM_TYPMAIL” “CALC_RIGI”
“TYPE_MAILLE” K8
“NBNO_TYPMAIL”
“NUM_TYPMAIL”
“TYPE_TYPMAIL”