Code_Aster ®
Version
3.0
Titrate:
Rules concerning the extraction and the restitution of the sources of Aster
Date:
29/04/98
Author (S):
J. PELLET
Key:
D2.01.01-A
Page:
1/4
Organization (S): EDF/IMA/MN
Handbook of Descriptif Informatique
D2.01 booklet: Overload of a version in exploitation
D2.01.01 document
Rules concerning the extraction and
restitution of the sources of Aster
Summary:
One gives here the rules which the developers of Aster must comply with when they recover a source
official (extraction) and when they propose a modification of a source official (restitution). These rules
points also approached in the plan of development [A2.01] specify.
Handbook of Descriptif Informatique
D2.01 booklet: Overload of a version in exploitation
HI-75/95/009 Ind A

Code_Aster ®
Version
3.0
Titrate:
Rules concerning the extraction and the restitution of the sources of Aster
Date:
29/04/98
Author (S):
J. PELLET
Key:
D2.01.01-A
Page:
2/4
1 Introduction
One explained in [D1.01.01] how a developer could “overload” Code_Aster with sources
personnel. The sources about which one speaks here are:
· routines FORTRAN, or C or CAL (CRAY Assembling Language),
· catalogs,
· case-tests.
The sources official of Code are accessible in reading on the CRAY [D1.02.01 §2].
A traditional development of Aster results in general in:
· modification of certain sources,
· the writing of new sources.
The modification of sources supposes their preliminary extraction (recopy) sources official. Paragraph 2
relate to the rules of extraction.
The finished development, it can “be restored”: one puts up to date the sources then official. Paragraph 3
relate to the rules of restitution.
Handbook of Descriptif Informatique
D2.01 booklet: Overload of a version in exploitation
HI-75/95/009 Ind A

Code_Aster ®
Version
3.0
Titrate:
Rules concerning the extraction and the restitution of the sources of Aster
Date:
29/04/98
Author (S):
J. PELLET
Key:
D2.01.01-A
Page:
3/4
2 Rules
of extraction
R1
The extraction of a source is the recopy of the official version [D1.02.01 §2] of this source.
(To avoid the copies of copies).
R2
When a source must be modified for a future restitution, “to note” this source
[D1.02.01] (command asno of asterix). This notation gives rights of precedence
for the restitution when a source is modified simultaneously by several developers:
“noted” first is that which has the right to restore.
R3
When a source must be modified and restored: not to touch the “line” MODIF which contains
the date of the last modification of the source. This date makes it possible to check at the time of
restitution that the source of origin (before modification) is well last the source official.
This prevents that a modification “does not crush” a modification prédédente.
This rule is capital: an intentional violation would be very badly interpreted… and
sanctioned.
R4
Not to modify (for the pleasure or by taste) the presentation of the source: the indentation, the name
variables,… except if is to make it in conformity with the rules presentation or of
programming [D2.02]; because this artificially increases the volume of the “delta of evolution”
that one preserves: the relevant modifications do not jump any more to the eyes.
R5
If the source extracts was already noted by another developer:
· to contact to make him confirm its intention to restore this source,
· to try to negotiate with him, the command of the restitutions,
· if there remains noted “in front of” you, not to launch out head lowered in a modification of
great width of this source, because it will be necessary to start again the modifications in
source official resulting from its evolution (cf R3).
R6
Not to note sources unnecessarily: you can géner the other developers (cf R5).
In particular, to note a source only one intends to restore in 6 months!
R7
When one noted a source by error, to indicate it [D1.02.01] (command asdeno).
Handbook of Descriptif Informatique
D2.01 booklet: Overload of a version in exploitation
HI-75/95/009 Ind A

Code_Aster ®
Version
3.0
Titrate:
Rules concerning the extraction and the restitution of the sources of Aster
Date:
29/04/98
Author (S):
J. PELLET
Key:
D2.01.01-A
Page:
4/4
3
Rules of restitution
R1
To use the automatic mechanism of restitution of asterix/agla: order asrest
[D1.02.01].
This mechanism imposes that a restitution is autonomous: the official code modified by
restitution must be able to carry out the case-tests of nonregression.
R2
A “asrest” erases another of them: there is no pile of restitution for a developer
given. A developer cannot thus make more asrest per week for a version
data of code (NEW2 or NEW3).
R3
A “restitution” (sources modified + sources added) will not be effective (modification
sources official) that after the procedure of update of the code made by the administrator
[D1.02.02 §1.2].
R4
To destroy the sources of a restitution only after having received (and read) the announcing “mall”
update of the code.
R5
Any restitution must be accompanied by a file of history (standard histor of asterix)
in which the developer must document sobrement but with precision its restitution:
· new key words (vocabulary),
· new functionalities: a little mechanics and numerical analysis,
· numbers of the corrected anomalies: AL94-XX,
· numbers of the treated evolutions: EL95-XX,
· evolutions or additions of the cases tests.
Not to tire itself to list the names of the modified units of source: the system does it
automatically.
R6
“to present” its restitution in meeting of EDA Monday. To bring a transparency of its file
history.
R7
To think of the validation of its restitution: addition/modification of case-tests.
R8
To destroy a source (or to change it library) to see [D1.02.01 §3].
R9
When a new unit of source is added. This unit must contain a line “AJOUT”
whose syntax depends on the type of the unit [D1.02.01§1].
C AJOUT nom_de_bibliothèque
for FORTRAN
% & AJOUT nom_de_catalogist (COMMANDE, TYPELEM,…)
for CATALOG
% AJOUT
for case test
% TITER…
Handbook of Descriptif Informatique
D2.01 booklet: Overload of a version in exploitation
HI-75/95/009 Ind A