Code_Aster ®
Version
4
Titrate:
Rules concerning the inputs/outputs
Date:
28/01/1999
Authors:
J. PELLET
Key:
D2.07.01
Page: 1/6
Department Mécanique and Modèles Numériques
Index:
With
Diffusion:
Developers
Handbook of Descriptif Informatique
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.
EDF
Direction of Etudes and Recherches
Electricity of France
Project Code de Mécanique
Copyright EDF/DER 1997

Code_Aster ®
Version
4
Titrate:
Rules concerning the inputs/outputs
Date:
28/01/1999
Authors:
J. PELLET
Key:
D2.07.01
Page: 2/6
1
Introduction
The Aster commands exchange data. Generally these data are of 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 commands (in general of the procedures) have to read data on one
file or to write a result. The rules concerning these commands are given to [§4].
At the time of a calculation, a command can want to transmit an alarm or error message, in it
case, it will use “package” UTMESS [D6.04.01]. One will speak again about it to [§5].
Lastly, a command can want to write messages of information concerning the unfolding of
calculation. These impressions are controlled by key word INFO of the command. These impressions are the subject of
[§6] for which one uses package INFXXX [D6.04.02].
2
Various files of Aster and their use
2.1
Data bases: “GLOBALE”, “VOLATILE” and “LOCALE”
(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 the UTMESS,
-
impressions of INFO [§3.5],
-
echoes of the commands by the supervisor,
-
the result of the “debug post mortem' if the execution finishes badly.
·
(OUT) file “RESULTAT”: one finds there information asked explicitly by the user
: impression with the format “Aster” of the results (commands IMPR_RESU,…),
be added to that:
-
impressions of the UTMESS: alarms and errors,
-
the summary of the times placed in the various orders.
Note:
Approximately, the difference between files “MESSAGE” and “RESULTAT” is as follows:
·
file “RESULTAT” contains information interesting the sleeping partner of
the study,
·
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 commands
or procedures. For example:
·
file grid Aster (.mail),
Handbook of Descriptif Informatique
D2.07 booklet:
Index A

Code_Aster ®
Version
4
Titrate:
Rules concerning the inputs/outputs
Date:
28/01/1999
Authors:
J. PELLET
Key:
D2.07.01
Page: 3/6
·
file grid Gibi (.mgib),
·
file result Castem (.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,…
UTMESS <A> should be used
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:
·
“RESULTAT” (with the Aster format),
·
“IDEAS” (with format IDEAS),
·

3.4
The echo of the data
Examples:
“You chose method TRUC”
“For option “PLUS PETITE”, 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 Documentation d' Utilization (Manuel U).
Handbook of Descriptif Informatique
D2.07 booklet:
Index A

Code_Aster ®
Version
4
Titrate:
Rules concerning the inputs/outputs
Date:
28/01/1999
Authors:
J. PELLET
Key:
D2.07.01
Page: 4/6
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 the INFO is made by of WRITE on the file “message” it is necessary to comply with the rules of [§6].
Information of the type INFO is associated a level (1 or 2): a INFO of level 1 is more
important that a INFO of level 2. The INFO of level 1 will be described systematically in Manuel
of Utilization (cf [D6.04.02 §3]. They are contractual.
When the user asks for INFO: 1 (defect), one prints the INFO of level 1.
Lorqu' it requires INFO: 2, one prints the INFO of level 1 and level 2.
4
Read/write in a file different from “ERREUR” or
“MESSAGE”
Commands making of the readings/writing in a file different from files “ERREUR” or
“MESSAGE” [§5] are in a limited number.
·
If a command reads a file, one will try to give him a name of form LIRE_XXX:
LIRE_MAILLAGE, LIRE_FONCTION,…,
·
if a command writes in a file, one will try to give him a name of form IMPR_XXX:
IMPR_RESU, IMPR_COURBE,…,
·
commands of interface of input: PRE_IDEAS, PRE_GIBI,… read in general on a file
and write in another.
R1:
The commands 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 commands (the SD are there for that) nor to make
“pagination” memory (it is JEVEUX which takes care some).
R2:
The commands which read/write in files do it always explicitly.
I.e. they use standard key word:
/FICHIER: when the file is named
/UNITE_XXX: when one uses the logical unit of the file
except the commands LIRE_XXX (which are operators) other commands
who read and write in files are all of procedures (IMPR_XXX,
PRE_XXX,…) what wants to say that their role is to read and/or write.
Handbook of Descriptif Informatique
D2.07 booklet:
Index A

Code_Aster ®
Version
4
Titrate:
Rules concerning the inputs/outputs
Date:
28/01/1999
Authors:
J. PELLET
Key:
D2.07.01
Page: 5/6
5
Emission of alarm or error message
R3:
All command 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: “ERREUR”, “MESSAGE” and “RESULTAT”.
R4:
Only the supervisor can make UTMESS <I>, the commands do not make a UTMESS
<I> (information). The messages of “information” are printed with of WRITE (cf.
[§6]).
6
Writing of messages of information, key word INFO
In this paragraph, one calls INFO, a message of information.
R5:
A INFO is always written by WRITE. The logical unit (of file “MESSAGE”)
is always recovered by routine INFNIV.
R6:
A INFO has a level: 1 or 2. The INFO of level 1 are contractual; they
are described in Documentation d' Utilization. The person in charge for the command
must present in meeting EDA any evolution of the INFO of level 1.
R7:
The level of impression chosen by the user (1 or 2) is always via the key word
INFO: /1/2. Value 1 is always the default value.
When the user asks for INFO: 2, that wants to say that it wishes the INFO of
level 1 and of level 2.
R8:
Processing of key word IMPR in a command OPOOXX:
CAL INFMAJ
R9:
Impression of a INFO 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 a INFO of level 2:
CAL INFNN (INF, NIV)
IF (NIV.EQ.2) WRITE (INF, FMT)…
Handbook of Descriptif Informatique
D2.07 booklet:
Index A

Code_Aster ®
Version
4
Titrate:
Rules concerning the inputs/outputs
Date:
28/01/1999
Authors:
J. PELLET
Key:
D2.07.01
Page: 6/6
Intentionally white left page.
Handbook of Descriptif Informatique
D2.07 booklet:
Index A