Code_Aster
®
Version
8.2
Titrate:
Procedure
CONTINUATION
Date:
31/01/06
Author (S):
J.P. LEFEBVRE
Key
:
U4.11.03-I1
Page
:
1/10
Instruction manual
U4.1- booklet: Management
HT-62/06/004/A
Organization (S):
EDF-R & D/AMA
Instruction manual
U4.1- booklet: Management
Document: U4.11.03
Procedure
CONTINUATION
1 Goal
To continue a study starting from the backup with format JEVEUX or format HDF of its base
“TOTAL”.
The apparently complex syntax of this procedure should not worry the user, the call with
the operands by defect, is sufficient in the majority of the cases:
CONTINUATION
()
The use of this control is completely similar to that of BEGINNING.
Code_Aster
®
Version
8.2
Titrate:
Procedure
CONTINUATION
Date:
31/01/06
Author (S):
J.P. LEFEBVRE
Key
:
U4.11.03-I1
Page
:
2/10
Instruction manual
U4.1- booklet: Management
HT-62/06/004/A
2 Syntax
CONTINUATION
(
PAR_LOT
=
/
“YES”
,
[DEFECT]
/
“NOT”
,
IMPR_MACRO
=
/
“NOT”,
[DEFECT]
/
“YES”,
BASE
=
_F
(
FILE
=
/“VOLATILE”,
/
|
LONG_ENRE=
lenr,
[I]
|
NMAX_ENRE=
nenr,
[I]
|
LONG_REPE=
lrep,
[I]
),
CODE
=
_F
(
NAME
=
name
code,
[K8]
UNIT
=
|
15
,
[DEFECT]
|
unitd,
[I]
NIV_PUB_WEB =/“INTERNET”,
/
“Intranet”
,
VISU_EFICAS
=
/
“YES”,
[DEFECT]
/
“NOT”,
),
IMPRESSION
=
F (
FILE
=
nomlocal
[l_Kn]
UNIT
=
uniti
,
[l_I]
),
ERROR = _F (
ERREUR_F =/“ABORT”,
[DEFECT]
/
“EXCEPTION”,
DEBUG = _F (
JXVERI
=/“YES”,
/
“NOT”,
ENVIMA
=
“TEST”, [l_Kn]
JEVEUX
=/“YES”,
/
“NOT”,
),
MEMORY = _F (
MANAGEMENT
=
/
“FAST”,
[DEFECT]
/
“COMPACTS”,
TYPE_ALLOCATION
=/ty,
[I]
/
1,
[DEFECT]
CUT
=
your,
[I]
PARTITION
=
AP,
[R]
TAILLE_BLOC
=
/
400.,
[DEFECT]
/
tbloc,
[R]
),
RESERVE_CPU
=
_F (
/
VALE =
vale [R]
/
PERCENTAGE = pcent
[R]
Code_Aster
®
Version
8.2
Titrate:
Procedure
CONTINUATION
Date:
31/01/06
Author (S):
J.P. LEFEBVRE
Key
:
U4.11.03-I1
Page
:
3/10
Instruction manual
U4.1- booklet: Management
HT-62/06/004/A
LIMIT =/bv,
[R]
/
180. [DEFECT]
)
FORMAT_HDF
=
/
“NOT”,
[DEFECT]
/
“YES”,
)
Code_Aster
®
Version
8.2
Titrate:
Procedure
CONTINUATION
Date:
31/01/06
Author (S):
J.P. LEFEBVRE
Key
:
U4.11.03-I1
Page
:
4/10
Instruction manual
U4.1- booklet: Management
HT-62/06/004/A
3
Principle of operation
This procedure affects, moreover, the resources memory necessary to the continuation of calculation.
The operands of the control are homologous with those of the procedure
BEGINNING
[U4.11.01]. They
allow to specify certain resources assigned to the new execution.
The study carried out previously continues with a whole of controls starting with
CONTINUATION
and ending in
END
[U4.11.02].
Controls placed front
CONTINUATION
(except obviously
BEGINNING
) or afterwards
END
, if they are
syntactically correct, are ignored.
Procedure
CONTINUATION
who is carried out, as of his reading by the supervisor, carries out the tasks
following:
·
definition of the logical units of the files used in impression,
·
allowance of the files associated with the data bases managed by JEVEUX,
·
reading of the catalogs of controls but not of the catalogs of the elements which were
recopied on the basis of data during the first execution.
The operands are to be used to divert the various files on numbers of logical unit
different from the numbers affected by defect or to adjust certain parameters of files.
The simple concepts of python (of variable type) created during a preceding execution are
preserved in a file associated with base JEVEUX (pickle.1). during the execution of the procedure
CONTINUATION these concepts are regenerated and can thus be used under the name under which they have
summer created.
4 Operands
The operand
PAR_LOT
and key words
IMPRESSION
and
DEBUG
are identical to those of the procedure
BEGINNING
[U4.11.01].
The key word
BASE
is different for the procedure
CONTINUATION
.
4.1 Operand
PAR_LOT
PAR_LOT
=
Mode of processing of the controls:
“YES”:
(default option); the supervisor analyzes all the controls before in
to ask the execution.
“NOT”:
after having analyzed a control the supervisor asks for his execution then
pass to the analysis (and the execution) of the following control (processing
order by control).
4.2 Word
key
IMPR_MACRO
IMPR_MACRO
=
Authorize or not the displays produced by the macros in the file of message. Reading
files of message can be painful when it contains the totality of the echoes of under
controls generated by macro itself. By defect, only the echo of the controls
explicitly called by the user in his command set will appear.
Code_Aster
®
Version
8.2
Titrate:
Procedure
CONTINUATION
Date:
31/01/06
Author (S):
J.P. LEFEBVRE
Key
:
U4.11.03-I1
Page
:
5/10
Instruction manual
U4.1- booklet: Management
HT-62/06/004/A
4.3 Word
key
BASE
BASE
=
The functionality of this key word is to redefine the values of the parameters of the files of access
direct associated the “data base” if one does not wish to use those fixed by
defect.
In CONTINUATION mode, the various characteristics of the TOTAL base cannot be any more
modified.
Default values of the parameters associated with the data bases
BIRD
NMAX_ENRE 15728
LONG_ENRE
100 K words
LONG_REPE 2000
LOCAL
NMAX_ENRE
512
LONG_ENRE
100 K words
LONG_REPE 2000
The word is worth 8 bytes out of platform 64 bits under TRU64 and IRIX 64, 4 bytes on platform
32 bits under SOLARIS, HP-UX and WINDOWS-NT, LINUX.
Under TRU64, the procedure
CONTINUATION,
with the default values, a file of access will allocate
direct of at the maximum
15728
recordings of
100
Kmot (K is worth
1024
) for the base
“VOLATILE”
.
Note:
The real size of the file is dynamic; it depends on the volume of information to store
indeed. But this size is limited by the conditions of operating and one
parameter preset among the values characterizing the platform. On the platform of
reference TRU64 the maximum size is fixed at 12 Go. This value perhaps modified in
placing an argument on the line of order of executable behind the key word
max_base size where size is an actual value measured out of Mo.
4.3.1 Operand
FILE
FILE
=
Only parameters of the data bases
“LOCAL”
and
“VOLATILE”
can be
redefined.
4.3.2 Operands
LONG_ENRE/NMAX_ENRE/LONG_REPE
Definition of the parameters of the data base (files of random access).
/
|
LONG_ENRE
=
lenr
lenr
is the length of the recordings in Kmots of the files of random accesses
used.
Note:
The manager of memory JEVEUX uses this parameter to determine
two types of objects: the large objects which will be cut out in as much
recordings that necessary, and the small objects which will be accumulated
in a buffer of the size of a recording before being discharged.
Code_Aster
®
Version
8.2
Titrate:
Procedure
CONTINUATION
Date:
31/01/06
Author (S):
J.P. LEFEBVRE
Key
:
U4.11.03-I1
Page
:
6/10
Instruction manual
U4.1- booklet: Management
HT-62/06/004/A
|
NMAX_ENRE
=
nenr
nenr
is the number of recordings per defect, this value is given with
to leave
LONG_ENRE
and of an operating parameter under IRIX 64 fixed at 12 Go
(12 884.901.888 bytes) for the maximum size of the file associated with a base with
data.
Note:
Two operands
LONG_ENRE
and
NMAX_ENRE
must be used with
precaution, a bad use which can lead to the brutal stop of
program by saturation of the files of random access. Coherence enters
maximum size of the file and the value resulting from the product of both
parameters
LONG_ENRE
and
NMAX
_ENRE is checked at the beginning of execution.
|
LONG_REPE
=
lrep
lrep
is the initial length of the index (a maximum number of addressable objects by
JEVEUX), it is managed dynamically by the manager of memory which extends
size of the index and all the system objects progressively associated with
needs.
4.4 Word
key
IMPRESSION
IMPRESSION
=
Definition of the logical units of the files used in impression.
4.4.1 Operand
FILE
FILE
=
List reference symbols of files.
4.4.2 Operand
UNIT
UNIT = uniti
Number of the logical unit associated the files of the list.
If
uniti
is negative or null, there is no impression on this (S) file (S).
By defect:
FILE
UNIT
“ERROR” 9
“MESSAGE” 6
“RESULT” 8
“MED” 80
The definition of association file name, logical number of unit feeds the structure of
data internal with the code which is generated by control DEFI_FICHIER [U4.12.03].
4.5 Word
key
ERROR
ERROR =
Allows to recover an error of the <F> type to carry out a particular processing, it
mechanism was installed to check the emission of error message in the tests
of not-regression of the code. It is also interesting to be able to recover properly
hand in some macros (Stanley or tools trades) without stopping brutally in
fatal error.
Code_Aster
®
Version
8.2
Titrate:
Procedure
CONTINUATION
Date:
31/01/06
Author (S):
J.P. LEFEBVRE
Key
:
U4.11.03-I1
Page
:
7/10
Instruction manual
U4.1- booklet: Management
HT-62/06/004/A
4.5.1 Operand
ERREUR_F
ERREUR_F =
“ABORT”
the behavior of the code is unchanged and the code stops by printing one
increase of error.
“EXCEPTION”
the exception is raised
aster.FatalError (code 20)
and one returns to
standard behavior in the event of error
(“ABORT”)
4.6 Word
key
DEBUG
DEBUG =
Option of déboggage (reserved for the developers and the maintenance of the code).
4.6.1 Operand
JXVERI
JXVERI
= “YES”
“NOT”
Allows to control the integrity of the memory between two executions of controls
consecutive. By defect the execution is carried out without “
DEBUG
“.
4.6.2 Operand
ENVIMA
ENVIMA = “TEST”
Allows to print in the file '
RESULTAT'
values of the parameters preset in
software package
ENVIMA
characterizing the machine [D5.01].
4.6.3 Operand
JEVEUX
JEVEUX = “YES”
“NOT”
Allows to activate the operating mode in debug of the manager of memory JEVEUX:
unloadings on disc not differed and assignment from the segments of values to a value
indefinite [D6.02.01].
4.7 Word
key
MEMORY
Allows to modify the mode of management of the memory. During the allowance in memory of a segment
values, it is possible is to carry out a search for place by causing unloadings
on disc (MANAGEMENT = “COMPACTS”), which makes it possible to use less memory capacity but with
price of many accesses disc, is to seek in a priority way the free areas or
agent with accesses in reading alone (MANAGEMENT = “FAST”).
4.7.1 Operand
MANAGEMENT
MANAGEMENT =
“COMPACTS”
:
allows to activate the mode of most sparing memory allocation in total place
“FAST”:
allows to activate the mode of memory allocation privileging a fast access
4.7.2 Operand
TYPE_ALLOCATION
TYPE_ALLOCATION = ty
1: standard management of memory, one does not distinguish the objects to be allocated,
2: the systems objects of collection are allocated at the end of the area memory in order to avoid
to scatter the latter and to too much split the areas likely to accommodate the large one
objects,
3: even standard of allowance that previously, but applying to a criterion of size of
objects,
4: the area memory is partitionnée into two, an area is reserved for the allowance of small
objects.
Code_Aster
®
Version
8.2
Titrate:
Procedure
CONTINUATION
Date:
31/01/06
Author (S):
J.P. LEFEBVRE
Key
:
U4.11.03-I1
Page
:
8/10
Instruction manual
U4.1- booklet: Management
HT-62/06/004/A
4.7.3 Operand
CUT
CUT = size in words (unit of addressing in entirety) defining the small objects used for a type
of allowance 3 or 4.
4.7.4 Operand
PARTITION
PARTITION = relationship between the size of the area memory used for the allowance of the large objects and
total area.
This area is located at the end of the segmentation, the systems objects specific to JEVEUX are allocated
in the partition reserved for the “small” objects.
Note:
If one of the partitions is saturated, one returns to a mode of standard management of the memory
(TYPE_ALLOC = 1).
4.7.5 Operand
TAILLE_BLOC
This key word, formerly placed under SOLVEUR in the total controls, is used to define
cut blocks of the matrix.
TAILLE_BLOC =
One can choose the size of the blocks of the matrix of rigidity (
tbloc
). This size is given in
kiloR8 (1 kiloR8 = 1024 realities). This parameter influences the number of operations of input/output and
thus over the time of assembly and resolution. By defect this value is fixed at 800 kiloR8,
that is to say 8 recordings per defect on the file of random access associated base JEVEUX.
4.8 Key word
RESERVE_CPU
Allows to reserve a share of the time CPU allotted to the job to finish the execution properly in
case of stop for lack of time CPU detected by a control Aster. This mechanism is not useful
that in the case of an execution batch of Code_Aster. The value of this reserve can be indicated
in absolute value or in the form of a percentage of total time CPU. This value is limited
by the value of the key word LIMITS.
4.8.1 Operand
VALE
Value expressed in seconds withdrawn from the total time CPU, over which certain controls
total bases itself to stop the execution properly.
4.8.2 Operand
PERCENTAGE
Percentage withdrawn from the total time CPU, over which certain total controls is based for
to stop the execution properly.
4.8.3 Operand
LIMIT
Maximum value of the reserve of time, being worth by defect 180 seconds.
Code_Aster
®
Version
8.2
Titrate:
Procedure
CONTINUATION
Date:
31/01/06
Author (S):
J.P. LEFEBVRE
Key
:
U4.11.03-I1
Page
:
9/10
Instruction manual
U4.1- booklet: Management
HT-62/06/004/A
4.9 Word
key
FORMAT_HDF
FORMAT_
HDF =
'
YES
'
Allows to read again a TOTAL base backed up in a file with format HDF (cf orders
END [U4.11.02]). The base is then rebuilt starting from objects JEVEUX stored in the file,
this file can be built on a different platform (operating system, punt
form 32 or 64 bits). The characteristics of the original base are read again in the file and the base
is rebuilt with identical (one preserves for example the length of the recordings).
The file associated with the TOTAL base with format HDF is named bhdf.1 in the index
of execution of the code.
5 Example
of use
The standard use of this procedure is:
CONTINUATION ()
To make an execution with a base
“VOLATILE”
with a record length of
400
Kmots:
CONTINUATION
(BASE = _F (FILE = “VOLATILE”, LONG_ENRE = 400),)
Code_Aster
®
Version
8.2
Titrate:
Procedure
CONTINUATION
Date:
31/01/06
Author (S):
J.P. LEFEBVRE
Key
:
U4.11.03-I1
Page
:
10/10
Instruction manual
U4.1- booklet: Management
HT-62/06/004/A
Intentionally white left page.