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
Data-processing manual of Description
D2.03 booklet: Establishment of the catalogs
HI-75/95/009 Ind A
Organization (S):
EDF/IMA/MN
Data-processing manual of Description
D2.03 booklet: Establishment of the catalogs
D2.03.01 document
Rules concerning the writing of the 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 control or a catalog of finite element.
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
Data-processing manual of Description
D2.03 booklet: Establishment of the catalogs
HI-75/95/009 Ind A
Contents
1 Presentation .................................................................................................................................... 3
2 Catalogs of controls .............................................................................................................. 3
3 Catalogs of elements ..................................................................................................................... 3
3.1 catalog of PHENOMENE_MODELISATION .......................................................................... 3
3.2 catalog of the SIZES ..................................................................................................... 3
3.3 catalogs of the OPTIONS ......................................................................................................... 4
3.4 catalogs of the TYPE_ELEM ..................................................................................................... 4
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
Data-processing manual of Description
D2.03 booklet: Establishment of the catalogs
HI-75/95/009 Ind A
1 Presentation
We indicate here the rules (and consultings) concerning the writing:
·
catalogs of controls [D5.01.01 §2]
·
catalogs of elements [D3.02.01 §3]
2
Catalogs of controls
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 the Project Leader.
3 Catalogs
elements
3.1 catalog
of
PHENOMENE_MODELISATION
1) The names of the phenomena and modelings must be validated by the Project Leader because they
appear with the user.
3.2 catalog
SIZES
1) To give a name to the sizes of the 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 one modifies the catalog of
SIZES
, 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) Not to destroy
CMPS
in an existing size without to have checked that none
type_elem
uses.
6) Not to change the command of
CMPS
of an existing size without modifying them
type_elem
who
use.
7) When one introduces a new component into a size, to put it following
CMPS
existing. This avoids “breaking” programming too much “into hard”; for example, one
programmer can have made:
·
checking that
“DX”
and
“DY”
are the two first
CMPS
size
“DEPL_R”
,
·
then use of
DEPL_R (I), I = 1,2
.
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
Data-processing manual of Description
D2.03 booklet: Establishment of the catalogs
HI-75/95/009 Ind A
3.3 catalogs
OPTIONS
1) Names of
OPTIONS
must be validated by the Project Leader 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 news is added
option
, to think of putting
“- 1”
in the catalogs of
type_elem
who erudite pitch to calculate this news yet
OPTION
.
3.4 catalogs
TYPE_ELEM
1) For the names of the local modes to take as a starting point the the names chosen by
type_elem
neighbors.
To respect the use:
-
Cxxxx
: mode of the type
card
-
Nxxxx
: mode of the type
chamno
-
Exxxx
: mode of the type
chamelem
2) For a local mode of type
CHAMELEM
of type
“NR No…”,
to make sure that
No
is well it
a number of nodes of
type_maille
associated.
3) When new is added
type_elem
, to think of putting
“- 1”
compared to
OPTIONS
existing that the new one
type_elem
cannot calculate yet.
4) To put questions about the coherence of
type_elem
that one modifies with the others
type_elem
:
-
why the new one
type_elem
it would have a local mode “with the nodes” whereas all them
do others have it “at the points of GAUSS”?
-
why the new one
type_elem
do not use it this field parameter, this
CMP
?
-…