Code_Aster ®
Version
8.1
Titrate:
Utilities for Structures of data
Date:
01/12/05
Author (S):
J. Key PELLET
:
D6.07.05-B Page
: 1/10
Organization (S): EDF-R & D/AMA
Handbook of Descriptif Informatique
D6.07 booklet: -
Document: D6.07.05
Utilities for Structures of data
Summary:
One presents in this document some utilities of operative general interest on structures of data:
copy, destruction, existence, impression.
Utility DISMOI is used to extract “scalar” information (1 entirety or 1 text) in Structure of
Data.
Handbook of Descriptif Informatique
D6.07 booklet: - HT-66/05/003/A
Code_Aster ®
Version
8.1
Titrate:
Utilities for Structures of data
Date:
01/12/05
Author (S):
J. Key PELLET
:
D6.07.05-B Page
: 2/10
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”, “GRID”
IN K1 BASE
“G”/“V”/“It: name of the base where SD2 will be created
IN
SD1 K *
name of SD SD1
JXIN
IN
SD2 K *
name of SD SD2
JXOUT
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
SD1 K *
name of SD SD1
JXIN
IN
SD2 K *
name of SD SD2
JXIN
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”, “GRID”,
“MODEL”, “LIGREL”, “FUNCTION”, “MATR_ASSE”, “NUME_DDL”
IN
NOMSD K *
name of the SD to be tested
JXIN
OUT IRET
I 0: the structure of data does not exist
1: the structure of data exists
Handbook of Descriptif Informatique
D6.07 booklet: - HT-66/05/003/A
Code_Aster ®
Version
8.1
Titrate:
Utilities for Structures of data
Date:
01/12/05
Author (S):
J. Key PELLET
:
D6.07.05-B Page
: 3/10
4 Routine
DETRSD
SUBROUTINE DETRSD
(TYPESD, NOMSD)
drank:
to destroy a structure of data of the type TYPSD and 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” “GRID”
IN
NOMSD K *
name of the SD to be destroyed
JXIN
5 Routine
IMPRSD
SUBROUTINE IMPRSD
(TYPESD, NOMSD, FICH, TITLE)
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
NOMSD K *
name of the SD to be printed
JXIN
IN FICH K *
name of the file for the impression: “MESSAGE”, “RESULT”,…
IN TITLE 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 chain.
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.
Handbook of Descriptif Informatique
D6.07 booklet: - HT-66/05/003/A
Code_Aster ®
Version
8.1
Titrate:
Utilities for Structures of data
Date:
01/12/05
Author (S):
J. Key PELLET
:
D6.07.05-B Page
: 4/10
The declaration of this chain 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 “TOTO” followed by 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 field named CHAMP and which is on basis VOLATILE. 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 chain “.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 Structure de Donnée (SD).
Example:
·
the name of the grid associated with a field,
·
the number of equations of a nume_ddl,
·
…
It is to some extent a form of “JELIRA” on the SD.
To recover name (MA) grid associated with the field (CH), one will make:
CALL
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.
Handbook of Descriptif Informatique
D6.07 booklet: - HT-66/05/003/A
Code_Aster ®
Version
8.1
Titrate:
Utilities for Structures of data
Date:
01/12/05
Author (S):
J. Key PELLET
:
D6.07.05-B Page
: 5/10
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” makes it possible 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
impossible ier request.
In a “normal” use (out of the routines of “title”): 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 ibid is not tested
If the request fails, the stop brutal (“F”) but that is translated a programming error.
7.3
List types recognized by DISMOI
Name of the type
Length
Routine
“CARTE” K19
DISMCA
“CATALOG” K0
DISMCT
“CHAM_ELEM” or “RESUELEM”
K19
DISMCE
“CHAM_MATER” K8
DISMCM
“CHAM_NO” K19
DISMCN
“CHAMP” K19
DISMCP
“CHARGE” K8
DISMCH
“GRANDEUR” K8
DISMGD
“INCONNU” K19
DISMIC
“INTERF_DYNA” K14
DISMLI
“LIGREL” K19
DISMLG
“MACR_ELEM_STAT” K8
DISMML
“MAILLAGE” K8
DISMMA
“MATR_ASSE” K19
DISMMS
“MATR_ELEM” or “VECT_ELEM” K8
DISMME
“MODELE” K8
DISMMO
“NUME_EQUA” K19
DISMNE
“NUME_DDL” K14
DISMNU
“PHENOMENE” K16
DISMPH
“RESULTAT” K8
DISMRS
“TYPE_ELEM” K16
DISMTE
“TYPE_MAILLE” K8
DISMTM
Handbook of Descriptif Informatique
D6.07 booklet: - HT-66/05/003/A
Code_Aster ®
Version
8.1
Titrate:
Utilities for Structures of data
Date:
01/12/05
Author (S):
J. Key PELLET
:
D6.07.05-B Page
: 6/10
Note:
·
the length of the names of typified objects kN is indicative: routine DISMOI supplements (or
truncate) the name given by the user according to the associated type,
·
the name of routines DISMXX associated with the various types is given (in 3rd 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 the MODELE requires a CHAM_MATER
“CALC_RIGI”
K3
“YES”/“NOT”
Allows to know if one type_element can calculate “rigidity” (and thus if it is
a “principal” element of modeling and not an element of “edge”)
“CARA_ELEM” K8
name of the subjacent CARA_ELEM.
``: there is no subjacent CARA_ELEM.
“CHAM_MATER” K8
name of the subjacent CHAM_MATER.
``: there is no subjacent CHAM_MATER.
“COEF_MULT” I
value of the “multiplying” coefficient of the number of values of the 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 the subjacent type_elem are 1D (X)
2: all the subjacent type_elem are 2D (X, Y)
3: all the subjacent type_elem 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 grid type:
the answer is:
2: the grid aster read is of type “COOR_2D”
3: the grid aster read is of type “COOR_3D”
This value is that read in the file of grid: COOR_2D or COOR_3D.
Caution: it is not because COOR_3D that the grid is really 3D.
“ELAS_F_HYDR”
K3
“YES”/'NOT
if the CHAM_MATER uses for its behavior ELAS_XXX at least a function
hydration
Handbook of Descriptif Informatique
D6.07 booklet: - HT-66/05/003/A
Code_Aster ®
Version
8.1
Titrate:
Utilities for Structures of data
Date:
01/12/05
Author (S):
J. Key PELLET
:
D6.07.05-B Page
: 7/10
“ELAS_F_SECH”
K3
“YES”/'NOT
if the CHAM_MATER uses for its behavior ELAS_XXX at least a function
drying
“ELAS_F_TEMP”
K3
“YES”/'NOT
if the CHAM_MATER uses for its behavior ELAS_XXX at least a function
temperature
“ELEM_VOLU_QUAD”
K3
“YES”/“NOT”/“MEL”:
“OUI”: All the elements of the MODELE are mechanical, voluminal and
quadratic.
“NON”: All the elements of the MODELE are mechanical, voluminal and linear.
“MEL”: There are elements of the mechanical, voluminal MODELE linear and
the other quadratic ones.
“EXI_AMOR_ALPHA” K3 “YES”/'NOT
if the cham_mater refers at least a material has which has the CMP
“AMOR_ALPHA”
“EXI_AMOR_HYST”
K3
“YES”/“NOT”
if the cham_mater refers at least a material has which has the “CMP”
“AMOR_HYST”
“EXI_COQ1D' K3
“OUI”/“NON” if the MODELE contains finite elements of modelings
COQU_C_PLAN or COQU_D_PLAN or COQU_AXIS
“EXI_COQ 3D”
K3
“OUI”/“NON” if the MODELE contains finite elements of modelings
COQU_3D
“EXI_ELEM” K3
“OUI”/“NON” if the MODELE contains finite elements (it can only contain
static substructures)
“EXI_ELTVOL” K3
“OUI”/“NON” if the MODELE contains “voluminal” elements
“EXI_HYDRAT” K4
“NON”: the mechanical load does not contain a hydration
“EVOL”: the mechanical load contains a evol_ther hydration
“CHGD”: the mechanical load contains a field of hydration
“EXI_PLAQUE” K3
“OUI”/“NON” if the MODELE contains elements of plate: modelings
DST/DKT or Q4G
“EXI_POUX” K3
“OUI”/“NON” if the MODELE contains elements of beam “to the POUX”.
“EXI_RDM” K3
“OUI”/“NON” if the MODELE contains elements of R.D. Mr. (beam, plate or
hull)
“EXI_SECHAG” K4
“NON”: the mechanical load does not contain drying
“EVOL”: the mechanical load contains a evol_ther drying
“CHGD”: the mechanical load contains a field of drying
“EXI_TEMPER” K4
“NON”: the mechanical load does not contain a temperature
“EVOL”: the mechanical load contains a evol_ther temperature
“CHGD”: the mechanical load contains a field of temperature
“EXI_THM_CT” K3
“OUI”/“NON” if the MODELE contains elements of modelings
XXX_THM_CT
“EXI_THM_VR” K3
“OUI”/“NON” if the MODELE contains elements of modelings
XXX_THM_VR
“EXI_TUYAU” K3
“OUI”/“NON” if the MODELE contains elements “pipe”
“MODELISATION” K16
name of the MODELISATION associated with a MODELE.
If there is several MODELISATIONS in the MODELE, the answer is ''
“NB_CHAMP_MAX” I raising number of the sequence numbers of a SD RESULTAT.
“NB_CHAMP_UTI” I numbers sequence numbers used of a SD RESULTAT.
“NB_CMP_MAX” I
raising component count of a GRANDEUR.
“NB_DDLACT” I
a number of active DDLS = a number of physical DDLS minus the number of
constraints 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
“GRELS” in the LIGREL numbers.
“NB_MA_MAILLA” I numbers MAILLES of the MAILLAGE.
“NB_MA_SUP” I
a number of additional MAILLES of the LIGREL.
Handbook of Descriptif Informatique
D6.07 booklet: - HT-66/05/003/A
Code_Aster ®
Version
8.1
Titrate:
Utilities for Structures of data
Date:
01/12/05
Author (S):
J. Key PELLET
:
D6.07.05-B Page
: 8/10
“NB_NL_MAILLA” I numbers NOEUDS of LAGRANGE of the MAILLAGE. this number can be nonnull if
the grid contains SUPER_MAILLES.
“NB_NO_MAILLA” I numbers NOEUDS of the MAILLAGE.
“NB_NO_MAX” I
raising number of the NOEUDS of the TYPE_MAILLES.
“NB_NO_SS_MAX” I numbers maximum nodes for a SUPER_MAILLE of the MAILLAGE.
“NB_NO_SUP” I
a number of additional NOEUDS of the LIGREL.
“NB_SM_MAILLA” I numbers SUPER_MAILLES of the MAILLAGE.
“NB_SS_ACTI” I
a number of active substructures in a MODELE.
“NB_TYPE_MA” I
a number of TYPE_MAILLES in the catalog.
“NBNO_TYPMAIL” I numbers nodes of a type_maille
“NOM_GD” K8
name of the GRANDEUR.
“NOM_GD_SI” K8
name of the GRANDEUR simple partner.
“NOM_LIGREL” K19
name of the LIGREL.
“NOM_MAILLA” K8
name of the MAILLAGE.
“NOM_MODE_CYCL” K8 name of the MODE_CYCL.
“NOM_MODELE” K8
name of the MODELE.
“NOM_NUME_DDL” K14
name of the NUME_DDL.
“NOM_OPTION” K16
name of the OPTION (catalogs) calculation.
“NOM_TYPMAIL” K8
name of a type_maille
“NU_CMP_LAGR” I
number of component “LAGR” in a GRANDEUR.
“NUM_GD” I
number of the GRANDEUR.
“NUM_GD_SI” I
number of the GRANDEUR simple partner.
“NUM_TYPMAIL” I
number of a type_maille
“NUME_EQUA” K19
name of associated SD NUME_EQUA.
“PARA_INST” K3
“OUI”: if the CARTE is a card of FONCTIONS depend on time
'': if not
“PHENOMENE” K16
name of the PHENOMENE associates a MODELE.
the PHENOMENE is single in a MODELE)
“PROF_CHNO” K19
name of the subjacent PROF_CHNO.
“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
“OUI”/“NON” if the cham_mater uses for its behavior THER_XXX with
less one function of time
“TYPE” 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”: CARTE
“RESL”: RESUELEM
“NOEU”: CHAM_NO
“ELGA”: CHAM_ELEM at the points of GAUSS
“ELNO”: CHAM_ELEM with the nodes
“TYPE_CHARGE” K7
type of a 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 a RESULTAT: “EVOL_THER”, “EVOL_ELAS”, EVOL_NOLI',…. or
“CHAMP”
Handbook of Descriptif Informatique
D6.07 booklet: - HT-66/05/003/A
Code_Aster ®
Version
8.1
Titrate:
Utilities for Structures of data
Date:
01/12/05
Author (S):
J. Key PELLET
:
D6.07.05-B Page
: 9/10
“TYPE_SCA” K3
scalar type
“R”: real * 8
“I”: integer
“It: complex * 16
“K8”: character * 8
“K16”: character * 16
“TYPE_SUPERVIS”
Standard K16 which the supervisor would give to a SD:
“CHAM_NO_DEPL_R”, “CHAM_ELEM_EPSI_R”,…
“TYPE_TYPMAIL” K4
type of a type_maille:
/“POIN”/“LIGN”/“SURF” or “VOLU”
“Z_CST”
K3
“YES”/“NOT”
“OUI”: if all the nodes of the MAILLAGE have same “Z exactly” (3rd
co-ordinate)
“NON”: if not
7.5
Count cross of the possibilities
In the table below, one gives for each type of Structure de Données:
·
the theoretical length of the names of the objects of this type,
·
the list of the questions which one can put on this type.
“CARTE”
K19
“NOM_GD”
“NOM_MAILLA”
“PARA_INST”
“TYPE_CHAMP”
“CATALOG” K0
“NB_NO_MAX”
“NB_TYPE_MA”
“CHAMP”
K19
“NOM_GD”
“NOM_LIGREL”
“NOM_MAILLA”
“NOM_MODELE”
“NOM_OPTION”
“NUM_GD”
“TYPE_CHAMP”
“TYPE_SUPERVIS”
“CHAM_ELEM”
K19
“COEF_MULT”
“NOM_GD”
“NOM_LIGREL”
or “RESUELEM”
“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”
“CHARGE” K8
“EXI_TEMPER”
“EXI_HYDRAT”
“EXI_SECHAG”
“NOM_LIGREL”
“NOM_MAILLA”
“NOM_MODELE”
“PHENOMENE”
“TYPE_CHARGE”
“GRANDEUR” K8
“NB_CMP_MAX”
“NB_EC”
“NOM_GD_SI”
“NUM_GD”
“NUM_GD_SI”
“NU_CMP_LAGR”
“TYPE_MATRICE”
“TYPE_SCA”
“INCONNU” K19
“TYPE”
“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”
“PHENOMENE”
“NB_MA_MAILLA”
“MACR_ELEM_STAT” K8
“NOM_MAILLA”
“NOM_MODELE” “NOM_NUME_DDL”
“MAILLAGE” 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”
Handbook of Descriptif Informatique
D6.07 booklet: - HT-66/05/003/A
Code_Aster ®
Version
8.1
Titrate:
Utilities for Structures of data
Date:
01/12/05
Author (S):
J. Key PELLET
:
D6.07.05-B Page
: 10/10
“MATR_ELEM”
K8 “CARA_ELEM”
“CHAM_MATER”
“NB_SS_ACTI”
or “VECT_ELEM”
“NOM_MAILLA”
“NOM_MODELE” “PHENOMENON”
“SUR_OPTION”
“TYPE_MATRICE”
“MODELE” 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”
“MODELISATION”
“NB_MA_MAILLA”
“NB_NL_MAILLA” “NB_NO_MAILLA” “NB_NO_SS_MAX”
“NB_SM_MAILLA” “NB_SS_ACTI”
“NOM_LIGREL”
“NOM_MAILLA”
“PHENOMENE”
“Z_CST”
“NUME_DDL” K14
“NB_EQUA”
“NOM_GD”
“NOM_MODELE”
“NUM_GD_SI” “PHENOMENON” “NOM_MAILLA”
“PROF_CHNO”
“NUME_EQUA” K19
“NOM_MAILLA”
“PHENOMENE” K8
“NOM_GD”
“NUM_GD”
“RESULTAT” K8
“NB_CHAMP_MAX”
“NOM_MAILLA”
“TYPE_RESU”
“TYPE_ELEM”
K16
“DIM_GEOM” “MODELING”
“PHENOMENE”
“TYPE_TYPMAIL” “NBNO_TYPMAIL”
“NOM_TYPMAIL”
“NUM_TYPMAIL” “CALC_RIGI”
“TYPE_MAILLE” K8
“NBNO_TYPMAIL”
“NUM_TYPMAIL”
“TYPE_TYPMAIL”
Handbook of Descriptif Informatique
D6.07 booklet: - HT-66/05/003/A
Outline document