Code_Aster
®
Version
4
Titrate
:
Rules concerning the inputs/outputs
Date:
28/01/1999
Authors:
J. PELLET
Key:
D2.07.01
Page:
1/6
Mechanical department and Digital Models
Index:
With
Dissemination:
Developers
EDF
Direction of the Studies and Search
Electricity of France
Project Codes of Mechanics
Copyright EDF/DER 1997
Data-processing manual of Description
D2.07 booklet:
D2.07.01 document
Rules concerning the inputs/outputs
Summary:
This document lists the rules concerning the inputs/outputs which the developers must respect
of Aster.
Code_Aster
®
Version
4
Titrate:
Rules concerning the inputs/outputs
Date:
28/01/1999
Authors:
J. PELLET
Key:
D2.07.01
Page:
2/6
Data-processing manual of Description
D2.07 booklet:
Index A
1
Introduction
The Aster controls exchange data. Generally these data are Structures of
Data (or concepts “user”) for which, the programmer does not take place to make”
READ
“(for its
data) nor of “
WRITE
“(for its results). In this case, the “left” “inputs”/are made by JEVEUX
[D6.02.01].
It happens however that certain controls (in general of the procedures) have to read data on one
file or to write a result. The rules concerning these controls are given to [§4].
At the time of a calculation, a control can want to transmit an alarm or error message, in it
case, it will use the “package”
UTMESS
[D6.04.01]. One will speak again about it to [§5].
Lastly, a control can want to write messages of information concerning the unfolding of
calculation. These impressions are controlled by the key word
INFORMATION
control. These impressions are the subject of
[§6] for which one uses the package
INFXXX
[D6.04.02].
2
Various files of Aster and their use
2.1
Data bases:
“TOTAL”
,
“VOLATILE”
and
“LOCAL”
(
IN/OUT
) they are the files with random accesses managed by JEVEUX. JEVEUX is the only one with reading/writing on these
files.
2.2
General and essential files
·
(
IN
) command file (
.comm
) and (of include): these files are only read by
supervisor,
·
(
OUT
) file
“error”
: only
UTMESS
can write there; a trace of the errors there is found,
·
(
OUT
) file
“MESSAGE”
: one finds there:
-
impressions of
UTMESS
,
-
impressions of INFORMATION [§3.5],
-
echoes of the controls by the supervisor,
-
the result of the “debug post mortem' if the execution finishes badly.
·
(
OUT
) file
“RESULT”
: one finds there information asked explicitly by the user
: impression with the format “Aster” of the results (controls
IMPR_RESU
,…),
be added to that:
-
impressions of
UTMESS
: alarms and errors,
-
the summary of the times placed in the various orders.
Note:
Approximately, the difference between the files
“MESSAGE”
and
“RESULT”
is as follows:
·
the file
“RESULT”
contains information interesting the sleeping partner of
the study,
·
the file
“MESSAGE”
contains information interesting that which makes a study
to control the courses of calculations.
2.3
Particular files
They are the other files. They are known as “private individuals” because they are used only by some controls
or procedures. For example:
·
file mesh Aster (
.mail
),
Code_Aster
®
Version
4
Titrate:
Rules concerning the inputs/outputs
Date:
28/01/1999
Authors:
J. PELLET
Key:
D2.07.01
Page:
3/6
Data-processing manual of Description
D2.07 booklet:
Index A
·
file Gibi mesh (
.mgib
),
·
file Castem result (
.cast
),
·
…
3
Various types of messages
When a programmer wishes to print information in a file, it is important for him
to try “to typify” this information, because from this type, the name rises from the file where one prints and the way
to print:
UTMESS
or
WRITE
.
3.1
The error
It prevents the continuation of calculation. One must always use
UTMESS <F>, <E>
or
<S>
(cf [D6.04.01]).
3.2
Alarm
The continuation of calculation is possible but the use is strongly disadvised;
Examples: negative Young modulus, affected in double,…
It is necessary to use
UTMESS <A>
3.3
The result
It is a result of the study. It is asked explicitly by the user.
It is necessary to use
WRITE
(
IFR
,…)…
where
IFR
is the logical unit of the file result:
·
“RESULT”
(with the format Aster),
·
“IDEAS”
(with the format
IDEAS
),
·
…
3.4
The echo of the data
Examples:
“You chose the method
TRICK
“
“For the option '
SMALLER
', the frequencies are ignored.
These impressions must be avoided: they do nothing but repeat what the user wrote or what must
to be known as in the Documentation of Use (Manual U).
Code_Aster
®
Version
4
Titrate:
Rules concerning the inputs/outputs
Date:
28/01/1999
Authors:
J. PELLET
Key:
D2.07.01
Page:
4/6
Data-processing manual of Description
D2.07 booklet:
Index A
3.5
INFORMATION
It is information which relates to the course of calculation.
Examples:
·
iteration count to converge,
·
coefficient of conditioning of Lagranges,
·
criterion of convergence reached,…
It can be also “data-processing” information more:
·
cut memory (or disc) of a matrix
·
time spent in the factorization of a matrix,
·
…
It can be finally information intended to reassure the user (confirmation of its data):
·
a number of nodes, meshs,
·
list nodes likely to come into contact.
The writing of INFORMATION is made by
WRITE
on the file
“message”
it is necessary to comply with the rules of [§6].
Information of the INFORMATION type is associated a level (1 or 2): INFORMATION of level 1 is more
important that INFORMATION of level 2. The INFORMATION of level 1 will be described systematically in the Manual
of Use (cf [D6.04.02 §3]. They are contractual.
When the user asks
INFORMATION: 1
(defect), one prints the INFORMATION of level 1.
Lorqu' it requires
INFORMATION: 2
, one prints the INFORMATION of level 1 and level 2.
4
Read/write in a file different from
“ERROR”
or
“MESSAGE”
Controls making of the readings/writing in a file different from the files
“ERROR”
or
“MESSAGE”
[§5] are in a limited number.
·
If a control reads a file, one will try to give him a name of the form
LIRE_XXX
:
LIRE_MAILLAGE
,
LIRE_FONCTION
,…,
·
if a control writes in a file, one will try to give him a name of the form
IMPR_XXX
:
IMPR_RESU
,
IMPR_COURBE
,…,
·
controls of interface of input:
PRE_IDEAS
,
PRE_GIBI
,… read in general on a file
and write in another.
R1:
The controls should not read and write in files except if they are
conceived for that (cf R2). The files should not be used to be exchanged
information between controls (the SD are there for that) nor to make
“pagination” memory (it is JEVEUX which takes care some).
R2:
The controls which read/write in files do it always explicitly.
I.e. they use standard key word:
/FILE
: when the file is named
/UNITE_XXX
: when one uses the logical unit of the file
except the controls
LIRE_XXX
(which is operators) other controls
who read and write in files are all of the procedures (
IMPR_XXX
,
PRE_XXX
,…) what wants to say that their role is to read and/or write.
Code_Aster
®
Version
4
Titrate:
Rules concerning the inputs/outputs
Date:
28/01/1999
Authors:
J. PELLET
Key:
D2.07.01
Page:
5/6
Data-processing manual of Description
D2.07 booklet:
Index A
5
Emission of alarm or error message
R3:
All control can transmit an error message (more or less immediate stop)
or of alarm (one continues the execution). For that, it will use them exclusively
routines
UTMESS
,
UTDEBM
,… [D6.04.01].
The transmitted messages will go then automatically in “the good” files
predetermined:
“ERROR”
,
“MESSAGE”
and
“RESULT”
.
R4:
Only the supervisor can make
UTMESS <I>
, the controls do not make
UTMESS
<I>
(information). The messages of “information” are printed with
WRITE
(cf.
[§6]).
6
Writing of messages of information, key word
INFORMATION
In this paragraph, one calls INFORMATION, a message of information.
R5:
INFORMATION is always written by one
WRITE
. The logical unit (of the file
“MESSAGE”
)
is always recovered by the routine
INFNIV
.
R6:
INFORMATION has a level: 1 or 2. The INFORMATION of level 1 are contractual; they
are described in the Documentation of Use. The person in charge for the control
must present in meeting EDA any evolution of the INFORMATION of level 1.
R7:
The level of impression chosen by the user (1 or 2) is always via the key word
INFORMATION: /1/2
. Value 1 is always the default value.
When the user asks
INFORMATION: 2
, that wants to say that it wishes the INFORMATION of
level 1 and of level 2.
R8:
Processing of the key word
IMPR
in a control
OPOOXX
:
CAL INFMAJ
R9:
Impression of INFORMATION of level 1:
CAL INFNIV (INF, NIV
)! recovery of the logical unit and
! level of impression asked
IF (NIV
.
GE.1) WRITE
(
INF
,
FMT
)…
R10:
Impression of INFORMATION of level 2:
CAL INFNN
(
INF, NIV
)
IF
(
NIV
.
EQ.2
)
WRITE
(
INF
,
FMT
)…
Code_Aster
®
Version
4
Titrate:
Rules concerning the inputs/outputs
Date:
28/01/1999
Authors:
J. PELLET
Key:
D2.07.01
Page:
6/6
Data-processing manual of Description
D2.07 booklet:
Index A
Intentionally white left page.