Code_Aster ®
Version
7.2
Titrate:
Description of storage JEVEUX to format HDF


Date:
01/10/03
Author (S):
Key J.P. LEFEBVRE
:
D9.02.04-A Page
: 1/6

Organization (S): EDF-R & D/AMA

Handbook of Descriptif Informatique
D9.02 booklet: -
Document:D9.02.04

Description of storage JEVEUX to format HDF

Summary:

One describes here the organization of file HDF adopted to store the contents of a base JEVEUX. This file
an image of the whole of objects JEVEUX created on the Globale basis contains at the time of the backup
and can be used to launch an execution in continuation on the platform of initial execution or all
another platform compatible and having the version carried of Code_Aster.

Handbook of Descriptif Informatique
D9.02 booklet: -
HT-66/03/007/A

Code_Aster ®
Version
7.2
Titrate:
Description of storage JEVEUX to format HDF


Date:
01/10/03
Author (S):
Key J.P. LEFEBVRE
:
D9.02.04-A Page
: 2/6

1 General information

By defect, the manager of memory JEVEUX employed in Code_Aster uses several files
random access of binary type. These files constitute “bases” JEVEUX, the structures of
data which will again be used in the event of continuation of calculation are stored in the base
GLOBALE in a format specific to the manager of memory. During calculation, the manager of
memory is brought to use the bases to discharge the memory temporarily, thus the mode
access chosen for its performances in this mode of use is not adapted to a backup
especially if he one wants to make them independent of the platform.
The use of bookstore HDF, already used within the framework of the interchange format of data MED, for
a writing of the contents of bases JEVEUX appears much more adapted. The file obtained afterwards
backup can be easily transferred, after a possible compression, on a platform
local to carry out for example operations of postprocessing with a version carried of
Code_Aster.
A file with format HDF is organized like a tree structure file Unix, the concept of “group”
are connected with the concept of repertory, the concept of “dataset” corresponds to the file. Moreover it is
possible to assign attributes to each level of “group” and/or to each “dataset”. We have
exploited these some concepts to organize the recopy of the whole of objects JEVEUX contained
in a base.
HDF provides a utility (h5dump) making it possible to write with format ASCII the contents of a whole file, it
is thus very easy, for files of reasonable size, to obtain the contents of all the objects
constituting a base JEVEUX.

2
Writing of objects simple JEVEUX

Objects simple JEVEUX are in general of homogeneous type, they are stored in a “dataset”
bearing the name of the simple object on the level of the “group”/. Simple objects of repertory kind of
names contain at the same time a table of h-coding of the type INTEGER and the list of the names stored of
type CHARACTER and must be treated separately. They are divided to store two “datasets”
respective names T_HCOD and T_NOM on the level of a group bearing the name of the simple object on the level of
“group”/.
One associates a named list “ATTRIBUTS JEVEUX” of 5 attributes all the associated “datasets”
with the simple objects and all the groups associated with the repertories with names containing respectively:

· a text (“OBJET SIMPLE”),
· an identifier (identifying of object simple JEVEUX),
· a chain containing the class, the kind and the type with direction JEVEUX (argument of JECREO),
· associated the Fortan type,
· a null string

The objects systems JEVEUX contain all information of the type attribute JEVEUX and
allow to rebuild the structure of associated data. They do not differ from the simple objects
JEVEUX, accessible to the user, that by their name, they are treated in the same way. Objects
systems are of homogeneous type and thus do not pose a particular problem of storage. One
store each object JEVEUX in a “dataset” bearing the name of the system object on the level of
“group”/.
One associates a named list “ATTRIBUTS JEVEUX” of 5 attributes all the associated “datasets”
with the system objects containing respectively:

· a text (“OBJET SYSTEME”),
· an identifier (identifying of object simple JEVEUX),
· a chain containing the class, the kind and the type with direction JEVEUX,
· associated the Fortan type,
· a null string

The attributes associated with the “dataset” or the “groups” will be used during the second reading of the file
HDF to rebuild the structures of data associated with objects JEVEUX.
Handbook of Descriptif Informatique
D9.02 booklet: -
HT-66/03/007/A

Code_Aster ®
Version
7.2
Titrate:
Description of storage JEVEUX to format HDF


Date:
01/10/03
Author (S):
Key J.P. LEFEBVRE
:
D9.02.04-A Page
: 3/6

3
Writing of collections JEVEUX

3.1 Collections
contiguous

The contiguous collections are built starting from simple objects, it is thus easy to use them
methods associated with the simple objects to store these last. Objects of contiguous collection
are stored in the segment of values associated with the system object $$DESO.
The object simple descriptor of collection is stored in a “dataset” bearing the name of the collection
under the “group”/.
One associates a named list “ATTRIBUTS JEVEUX” of 5 attributes the associated “dataset” containing
respectively:

· a text (“COLLECTION”),
· an identifier (identifying of object simple JEVEUX),
· a chain containing the class, the kind (X) and the type with direction JEVEUX (I),
· associated the Fortan type,
· a null string.

The system objects of collection are stored in “datasets” bearing the name of each object
system of collection under the “group”/.
One associates a named list “ATTRIBUTS JEVEUX” of 5 attributes the associated “dataset” containing
respectively:

· a text (“OBJ. SYSTEM COLLECTION”),
· an identifier (identifying of object simple JEVEUX),
· a chain containing the class, the kind and the type with direction JEVEUX,
· associated the Fortan type,
· a null string.

3.2 Collections
dispersed

The dispersed collections are built starting from simple objects for the systems objects of
collection and of segment of values associated with each object with collection. The systems objects are
stored in the same way that for the collection contiguous. The system object $$DESO is particular
because there is not associated in the case of the collections dispersed with a segment with values, it is not thus
not associated “dataset”, and it is only by charging the contents of the objects sytèmes JEVEUX
that the dispersed collection is rebuilt during the second reading of file HDF.

A “group” bearing the name of the collection supplemented by __OBJETS is created on the level of the “group”/
to write the objects of dispersed collection. One associates a named list “ATTRIBUTS JEVEUX”
of 5 attributes to the “group”, only the first element is nonempty and contains a text (COLLECTION).

Each object of collection is then written in a “dataset” bearing the name of the collection
supplemented by the number of the object of collection (including for the named collections) under
the “group” describes above.

One associates a named list “ATTRIBUTS JEVEUX” of 5 attributes the associated “dataset” containing
respectively:

· a text (OBJET OF COLLECTION),
· the name or the number of the object of collection and the identifier of collection,
· a chain containing the class, the kind and the type with direction JEVEUX,
· associated the Fortan type,
· a null string.
Handbook of Descriptif Informatique
D9.02 booklet: -
HT-66/03/007/A

Code_Aster ®
Version
7.2
Titrate:
Description of storage JEVEUX to format HDF


Date:
01/10/03
Author (S):
Key J.P. LEFEBVRE
:
D9.02.04-A Page
: 4/6

4
Heading of the file

One stores a named list “BASE GLOBALE JEVEUX” of 5 attributes associated with the “group “/
containing respectively:

· a text identifying the version of Code_Aster used to build the file,
· the name of the server of calculation used,
· the name of the system on the server,
· the date of execution of the code,
· 3 characteristics machine (length out of bits of the standard entirety, length in bytes of the entirety
standard, length in bytes of the unit of addressing).

The first information is used during the second reading for if required emitting an alarm
when the version of Code_Aster used differs. Certain structures of data or catalogs
can appear incompatible.

5
Example of file

Here an example of file HDF obtained starting from the carrying out of the test TTLL01A and of which
representation ASCII results from the utility h5dump. One gives only some extracts here illustrating
descriptions of principal objects JEVEUX.

HDF5 “resu64.hdf” {
GROUP “/” {
ATTRIBUTE “BASES TOTAL JEVEUX” {
DATATYPE H5T_STRING {
STRSIZE 24;
STRPAD H5T_STR_SPACEPAD;
CSET H5T_CSET_ASCII;
CTYPE H5T_C_S1;
}
SIMPLE DATASPACE {(5)/(5)}
DATA {
“13/08/2003 7. 1.13”, “CLA4ASTR.CLA.EDF”,
“OSF1”, “MA-19-AOUT-2003 10:35:24”,
“LBIS=64 LOIS= 8 LOUA= 1”
}
}
DATASET “&&SYS .CODE” {
DATATYPE H5T_STRING {
STRSIZE 8;
STRPAD H5T_STR_SPACEPAD;
CSET H5T_CSET_ASCII;
CTYPE H5T_C_S1;
}
SIMPLE DATASPACE {(3)/(3)}
DATA {
“TTLL01A”, “15”,” 95 "
}
ATTRIBUTE “ATTRIBUTES JEVEUX” {
DATATYPE H5T_STRING {
STRSIZE 24;
STRPAD H5T_STR_SPACEPAD;
CSET H5T_CSET_ASCII;
CTYPE H5T_C_S1;
}
Handbook of Descriptif Informatique
D9.02 booklet: -
HT-66/03/007/A

Code_Aster ®
Version
7.2
Titrate:
Description of storage JEVEUX to format HDF


Date:
01/10/03
Author (S):
Key J.P. LEFEBVRE
:
D9.02.04-A Page
: 5/6


SIMPLE DATASPACE {(5)/(5)}
DATA {
“SIMPLE OBJECT”, “30”,
“G V K8”, “CHARACTER * 8”,
““
}
}
}

GROUP “TEMPLE .DESC” {
ATTRIBUTE “ATTRIBUTES JEVEUX” {
DATATYPE H5T_STRING {
STRSIZE 24;
STRPAD H5T_STR_SPACEPAD;
CSET H5T_CSET_ASCII;
CTYPE H5T_C_S1;
}
SIMPLE DATASPACE {(5)/(5)}
DATA {
“SIMPLE OBJECT”, “287”,
“G NR K16”, “CHARACTER * 16”,
““
}
}
DATASET “T_HCOD” {
DATATYPE H5T_STD_I64LE
SIMPLE DATASPACE {(43)/(43)}
DATA {
37, 344, 16, 18, 18, 6, 0, 0, 0, 18, 8, 6, 4, 0, 0, 0, 7, 0, 0, 0,
0, 13, 17, 12, 0, 16, 11, 2, 0, 5, 0, 15, 14, 1, 0, 9, 0, 3, 0, 10,
0, 0, 0
}
}
DATASET “T_NOM” {
DATATYPE H5T_STRING {
STRSIZE 16;
STRPAD H5T_STR_SPACEPAD;
CSET H5T_CSET_ASCII;
CTYPE H5T_C_S1;
}
SIMPLE DATASPACE {(18)/(18)}
DATA {
“TEMP”, “FLUX_ELGA_TEMP”, “FLUX_ELNO_TEMP”,
“FLUX_NOEU_TEMP”, “META_ELGA_TEMP”, “META_ELNO_TEMP”,
“META_NOEU_TEMP”, “DURT_ELGA_META”, “DURT_ELNO_META”,
“DURT_NOEU_META”, “HYDR_ELGA”, “HYDR_ELNO_ELGA”,
“HYDR_NOEU_ELGA”, “DETE_ELNO_DLTE”, “DETE_NOEU_DLTE”,
“COMPORTHER”, “ERTH_ELEM_TEMP”, “ERTH_ELNO_ELEM”
}
}
}
DATASET “TEMPLE .INST” {
DATATYPE H5T_IEEE_F64LE
SIMPLE DATASPACE {(42)/(42)}
DATA {
0, 0.0001, 0.0002, 0.0003, 0.0004, 0.0005, 0.0006, 0.0007, 0.0008,
0.0009, 0.001, 0.002, 0.003, 0.004, 0.005, 0.006, 0.007, 0.008, 0.009,
0.01, 0.02, 0.1, 0.2, 0.7, 2, 1.79769e+308, 1.79769e+308,
1.79769e+308,
1.79769e+308, 1.79769e+308, 1.79769e+308, 1.79769e+308, 1.79769e+308,
1.79769e+308, 1.79769e+308, 1.79769e+308, 1.79769e+308, 1.79769e+308,
1.79769e+308, 1.79769e+308, 1.79769e+308, 1.79769e+308
}
Handbook of Descriptif Informatique
D9.02 booklet: -
HT-66/03/007/A

Code_Aster ®
Version
7.2
Titrate:
Description of storage JEVEUX to format HDF


Date:
01/10/03
Author (S):
Key J.P. LEFEBVRE
:
D9.02.04-A Page
: 6/6


ATTRIBUTE “ATTRIBUTES JEVEUX” {
DATATYPE H5T_STRING {
STRSIZE 24;
STRPAD H5T_STR_SPACEPAD;
CSET H5T_CSET_ASCII;
CTYPE H5T_C_S1;
}
SIMPLE DATASPACE {(5)/(5)}
DATA {
“SIMPLE OBJECT”, “293”,
“G V R”, “REAL * 8”,
““
}
}
}


Handbook of Descriptif Informatique
D9.02 booklet: -
HT-66/03/007/A

Outline document