Code_Aster ®
Version
3
Titrate:
Rules concerning the catalogs
Date:
28/04/98
Author (S):
J. PELLET
Key: D2.03.01-A
Page:
1/4
Organization (S): EDF/IMA/MN
Handbook of Descriptif Informatique
D2.03 booklet: Establishment of the catalogs
D2.03.01 document
Rules concerning the writing of Catalogs
Summary:
We give in this document, the rules (or consultings) which must comply with the developer when it
add or modifies a catalog of command or a catalog of finite element.
Handbook of Descriptif Informatique
D2.03 booklet: Establishment of the catalogs
HI-75/95/009 Ind A

Code_Aster ®
Version
3
Titrate:
Rules concerning the catalogs
Date:
28/04/98
Author (S):
J. PELLET
Key: D2.03.01-A
Page:
2/4
Contents
1 Presentation .................................................................................................................................... 3
2 Catalogs of commands .............................................................................................................. 3
3 Catalogs of elements ..................................................................................................................... 3
3.1 catalog of PHENOMENE_MODELISATION .......................................................................... 3
3.2 catalog of the GRANDEURS ..................................................................................................... 3
3.3 catalogs of the OPTIONS ......................................................................................................... 4
3.4 catalogs of the TYPE_ELEM ..................................................................................................... 4
Handbook of Descriptif Informatique
D2.03 booklet: Establishment of the catalogs
HI-75/95/009 Ind A

Code_Aster ®
Version
3
Titrate:
Rules concerning the catalogs
Date:
28/04/98
Author (S):
J. PELLET
Key: D2.03.01-A
Page:
3/4
1 Presentation
We indicate here the rules (and consultings) concerning the writing:
· catalogs of commands [D5.01.01 §2]
· catalogs of elements [D3.02.01 §3]
2
Catalogs of commands
1) As much as possible to use the possibilities of the supervisor concerning exclusions, the values by
defect,…
2) Not to use the concept of argument multiple.
3) When an argument is of type “text”:
-
if it can take a finished number of values, to define it in TXM and to give the integral list of
possibilities by the key word IN.
-
if it is a free text: comment,… to use TX
4) The comments are welcome.
5) to make validate the vocabulary by Chef de Projet.
3 Catalogs
elements
3.1 catalog
of
PHENOMENE_MODELISATION
1) The names of the phenomena and modelings must be validated by Chef de Projet because they
appear with the user.
3.2 catalog

GRANDEURS
1) To give a name to the sizes of form where S can be worth:
-
R: reality
-
C: complex
-
F: function (K8)
2) When one does not want to create a new too particular size, to use the sizes
“neutral”: NEUT_R or NEUT_K24.
3) When the catalog of the GRANDEURS is modified, to think of updating the document “description
sizes " [D4.04.02] and to classify the names of sizes alphabetically.
4) Not to define sizes of the type: L, K32, K80
5) To destroy CMPS in an existing size without to have checked only any type_elem
uses.
6) Not to change the command of the CMPS of an existing size without modifying the type_elem which
use.
7) When one introduces a new component into a size, to put it following the CMPS
existing. This avoids “breaking” programming too much “into hard”; for example, one
programmer can have made:
· checking that “DX” and “DY” are the first two CMPS of size “DEPL_R”,
· then use of DEPL_R (I), I = 1,2.
Handbook of Descriptif Informatique
D2.03 booklet: Establishment of the catalogs
HI-75/95/009 Ind A

Code_Aster ®
Version
3
Titrate:
Rules concerning the catalogs
Date:
28/04/98
Author (S):
J. PELLET
Key: D2.03.01-A
Page:
4/4
3.3 catalogs

OPTIONS
1) The names of OPTIONS must be validated by Chef de Projet if they appear with the user.
2) Not to reinvent the names of the parameters for each option; to take as a starting point those already selected.
The usual form is as follows: nom_par = “P”//nom_gd. Examples: PMATERF, PGEOMER
3) To comment on each field parameter: example: PGEOMER, GEOM_R % field of geometry
4) When a new option is added, to think of putting “- 1” in the catalogs of
type_elem which erudite step to calculate this new OPTION yet.
3.4 catalogs

TYPE_ELEM
1) For the names of the local modes to take as a starting point the the names chosen by the close type_elem.
To respect the use:
-
Cxxxx: mode of the card type
-
Nxxxx: mode of the chamno type
-
Exxxx: mode of the chamelem type
2) For a local mode of type CHAMELEM of the type “NR No…”, to make sure that No is well it
a number of nodes of the associated type_maille.
3) When new a type_elem is added, to think of putting “- 1” compared to the OPTIONS
existing that new the type_elem cannot calculate yet.
4) To put questions about the coherence of the type_elem which one modifies with the others
type_elem:
-
why new the type_elem would have it a local mode “with the nodes” whereas all them
do others have it “at the points of GAUSS”?
-
why new the type_elem use doesn't this field parameter, this CMP?
-…
Handbook of Descriptif Informatique
D2.03 booklet: Establishment of the catalogs
HI-75/95/009 Ind A