Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 22/04/97
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
1/24

Department Mécanique and Modèles Numériques



Index: With
Diffusion:
Users - Developers

Handbook of Référence

D9.07 booklet:

D9.07.01 document

Data-processing description of IMPR_RESU


Summary:

This document is a data-processing description of the command IMPR_RESU, whose role is to print
results of Code_Aster to format “RESULTAT”, “IDEAS”, “CASTEM” or “ENSIGHT”.

One finds the list of the principal routines used by the command, as well as a short summary of theirs
functionalities.

One describes the characteristics of the impression of the results to format I-DEAS, as well as the format of
“datasets” constituting universal file IDEAS.

For format CASTEM, one describes the format of the file used by code CASTEM 2000.

EDF
Direction of Etudes and Recherches

Electricity of France
Project Code de Mécanique
Copyright EDF/DER 1996

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
2/24


Tables of content

Tables of content .......................................................................................................... 2
1 Tree of call of the principal routines of IMPR_RESU .............................................. 3
1.1
Description of the routines appearing in the tree of call ................................ 3
1.2 Others
routines ............................................................................................ 5
2 Structure of file CASTEM 2000 ............................................................................. 6
2.1
Recording of the type 4: general information grid ..................... 6
2.2
Recording of the type 7: general information CASTEM 2000 ........... 6
2.3
Recording of the type 2: description of a pile ....................................... 7
2.3.1
Crush 0: co-ordinates of the nodes .............................................. 7
2.3.2
Crush 1: connectivities of the elements ........................................... 7
2.3.3
Crush 2: field with the nodes ........................................................ 9
2.3.4
Crush 39: field by element ..................................................... 10
2.4
Writing of a concept Aster result with format CASTEM 2000 ................... 11
2.4.1
Crush 27: Crush type word .......................................................... 11
2.4.2
Crush 26: Crush entireties ............................................................ 12
2.4.3
Crush 25: Crush realities ............................................................... 12
2.4.4
Crush 10: descriptor of the table ................................................. 13
3 Structure of universal file IDEAS ...................................................................... 14
3.1 Dataset
151
: Titrate ......................................................................................
15
3.2
Dataset 775: Properties of the beams ......................................................... 15
3.3
Dataset 15: Co-ordinates of the nodes in single precision ...................... 15
3.4
Dataset 781: Co-ordinates of the nodes in double precision .................... 16
3.5
Dataset 71: Connectivities of the meshs ....................................................... 16
3.6
Dataset 780: Connectivities of the meshs ..................................................... 18
3.7
Dataset 752: Groups of nodes and meshs ......................................... 19
3.8
Writing of the Aster results: CHAM_GD or Concept RESULTAT ................ 20
3.8.1
Dataset 55: Values with the nodes .............................................. 20
3.8.2
Dataset 56: Values by elements ............................................ 22
3.8.3
Dataset 57: Values with the nodes by element .......................... 23
3.9
Writing rule of a dataset of results .................................................. 23
4 Structure of file ENSIGHT ................................................................................. 24
5 Bibliography ...............................................................................................................
24


Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
3/24

1
Tree of call of the principal routines of IMPR_RESU



1.1
Description of the routines appearing in the tree of call

OP0039.f
Program main associate with command IMPR_RESU. It is in this
routine which are read all the operands of command IMPR_RESU.
IRECRI.f
Writing of a field of size or a concept result. This routine can
to be called by other routines for the impression of a Aster concept. It
“cap” for the impression of results is to some extent a routine
Aster, deprived of any adherence to command IMPR_RESU (not
calls to routines supervisor). It is in this routine that one finds
loops on the sequence numbers of a concept result and on the list of
reference symbols.
IRCH19.f
Routine of impression of a cham_no or a cham_elem.
IRCHML.f
Impression of a cham_elem with real or complex components with the format
RESULTAT, IDEAS or CASTEM.
IRDEPL.f
Impression of a cham_no with real or complex components with the format
RESULTAT, IDEAS, CASTEM or ENSIGHT.
IRCNRL.f
Impression of a cham_no with actual values with format RESULTAT (on listing).
This routine also allows the search and the note printing
minimal and of the maximum value of the field to the nodes.
These processing can be carried out on all the field or only on
values belonging to an interval defined by the user.

Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
4/24

IRCRRL.f
Impression of a cham_no with constant representation and actual values with
format RESULTAT.
Seek and impression of the values minimal and maximum.
Processing carried out on all the field or only on one definite interval
by the user.
IRCNC8.f
Impression of a cham_no with complex values with format RESULTAT.
Seek and impression of the values minimal and maximum.
Processing carried out on all the field or only on one definite interval
by the user.
IRDECA.f
Impression of a cham_no with actual values with format CASTEM (writing of
crush number 2, to see description of the structure of file CASTEM 2000 [§2]).
IRDRCA.f
Impression of a cham_no with constant representation and actual values with
format CASTEM (writing crushes number 2, to see description of the structure of
file CASTEM 2000 [§2]).
IRDESR.f
Impression of a cham_no with actual values with the format of the universal file
IDEAS (dataset 55, to see description of the structure of universal file IDEAS
[§3]).
IRDRSR.f
Impression of a cham_no with constant representation and actual values with
format of universal file IDEAS (dataset 55, to see description of the structure
universal file IDEAS [§3]).
IRDESC.f
Impression of a cham_no with complex values with the format of the universal file
IDEAS (dataset 55, to see description of the structure of universal file IDEAS
[§3]).
IRDEER.f
Impression of a cham_no with actual values with format ENSIGHT.
IRDRER.f
Impression of a cham_no with constant representation and actual values with
format ENSIGHT.
IRDEEC.f
Impression of a cham_no with complex values with format ENSIGHT.
IRDREC.f
Impression of a cham_no with constant representation and complex values
with format ENSIGHT.
IRCERL.f
Impression of a cham_elem to the nodes or the points of Gauss and values
real with format RESULTAT.
Seek and impression of the values minimal and maximum.
Processing carried out on all the field or only on one definite interval
by the user.
IRCECL.f
Impression of a cham_elem to the nodes or the points of Gauss and values
complexes with format RESULTAT.
Seek and impression of the values minimal and maximum.
Processing carried out on all the field or only on one definite interval
by the user.
IRCERS.f
Impression of a cham_elem to the nodes or the points of Gauss and values
real with the format of universal file IDEAS (datasets 56 and 57, to see
description of the structure of universal file IDEAS).
Note: the cham_elem at the points of Gauss are written as
constant fields by element, while realizing on the points of Gauss).

Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
5/24

IRCECS.f
Impression of a cham_elem to the nodes or the points of Gauss and values
complexes with the format of universal file IDEAS (datasets 56 and 57, to see
description of the structure of universal file IDEAS).
Note: the cham_elem at the points of Gauss are written as
constant fields by element, while realizing on the points of Gauss).
IRCECA.f
Impression of a cham_elem to the nodes and actual values with the format
CASTEM (writing of the structure of file CASTEM 2000).
IRMARE.f
Impression of the grid to the Aster format (which can be read again by the command
LIRE_MAILLAGE).
IRMACA.f
Impression of the grid to format CASTEM (impression of the piles number 0
(co-ordinates of the nodes) and number 1 (connectivities of the elements), to see
description of the structure of file CASTEM 2000).
IRMASU.f
Impression of the grid to the format universal file IDEAS (datasets 15
(co-ordinates of the nodes single precision), 781 (co-ordinates of the nodes
double precision), 71 or 780 (connectivities of the meshs) and 752 (groups of
nodes or of meshs), to see description of universal file IDEAS).
IRMAEN.f
Impression of the grid on file geometry ENSIGHT.

1.2 Others
routines

ECRTES.f
Writing of the heading of the datasets 55, 56 and 57 at the time of the writing of a field of
Aster size with format IDEAS.
This routine is called by the routines IRDESR.f, IRDRSR.f, IRDESC.f,
IRCERS.f and IRCECS.f.
IRGAGS.f
Seek datasets IDEAS necessary to the writing of a field of
Aster size.
This routine is called by the routines IRDESR.f, IRDRSR.f, IRDESC.f,
IRCERS.f and IRCECS.f.
IRADHS.f
Processing of “adherences IDEAS” at the time of the writing of a grid to the format
IDEAS.
This routine is called by the routines IRMAIL.f and IRCHML.f.
INISTB.f
Initializations necessary to the writing of a grid to format IDEAS.
This routine is called by the IRADHS.f routine.
IRPACA.f
Impression of the values of the variables of Aster access to the format of the files
CASTEM 2000 (piles 25, 26 and 27).
This routine is called by the IRECRI.f routine.
IRPARA.f
Impression of the values of the parameters and the variables of access to the format
RESULTAT.
This routine is called by the IRECRI.f routine.
RSINFO.f
Impression of the list of the reference symbols and the sequence numbers
available for a concept RESULTAT (key word INFO_RESU in
IMPR_RESU).
This routine is called by OP0039.f.


Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
6/24

2
Structure of file CASTEM 2000

This structure of file corresponds to level 3 of CASTEM 2000.

Each information contained in the file is preceded by a descriptor ENREGISTREMENT BY
TYPE followed by an entirety (I4). This one indicates the type of information which follows:


4 general Information on the grid

7 general Information CASTEM 2000

2 Description of a pile

5 End of file

2.1
Recording of the type 4: general information grid

General information on the grid. Two lines follow the descriptor.


NIVEAU niv NIVEAU ERREUR ierr DIMENSION ndim DENSITE dens


niv: number of version CASTEM 2000 (niv = 3, I4)

ierr
:
level
of error
(ierr
=
0,
I4)

ndim: dimension of the problem


(ndim = 2 or 3, I4)

dens: density of the grid



(dens = 0.D0, E12.5)

2.2
Recording of the type 7: general information CASTEM 2000

General information CASTEM 2000. Two lines follow the descriptor.


NOMBRE INFO CASTEM 2000 ninfo

IFOUR ifour NIFOUR nifour IFOMOD ifomod IECHO iecho IIMPI iimpi




IOSPI iospi ISOTYP isotyp

ninfo:
numbers information being reproduced on the following line (ninfo=7, I4)

ifour:
options of calculation
(- 1: plane deformations (if dimension 2), I4









2: three-dimensional (if dimension 3), I4)

nifour: harmonic of Fourier (0: no the harmonic, I4)

ifomod: type of mode
(- 1: plan (if dimension 2), I4



2:
three-dimensional
(if
dimension
3),
I4)

iecho:
echo of the data to the screen (iecho=1, I4)

iimpi:
level of impression

(iimpi=0, I4)

iospi:
trace operators

(iospi=0 not of trace, I4)

isotyp: type of layout of isovaleurs (isotyp=1, I4)


Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
7/24

2.3
Recording of the type 2: description of a pile

Description of a pile. This line is always followed following line:


PILE NUMERO npile NBRE OBJETS NOMMES iobno NBRE OBJETS iob

npile:
described the type of elements contained in the pile (I4)

(
npile
=0
co-ordinates

nodes

=1
connectivity

elements

=2
fields
with
nodes

=10

description of a table

=25

crush realities

=26
crush
entireties

=27

crush of word type

=39
fields
by
elements
)

iobno:
a number of named objects
(I5)

iob:
a total number of objects
(I5)

2.3.1
Crush 0: co-ordinates of the nodes


PILE NUMERO 0 NBRE OBJETS NOMMES iobno NBRE OBJETS iob

The named objects are the groups of Aster nodes to only one node.

If the number of named objects is not null, there is two information;

·
the list of the names of groups of Aster nodes to only one node (8 (1X, A8)),
·
the position of each node in the pile (16I5).

Then the co-ordinates and the density of the points follow: X (I), I = 1, iob * (ndim+1)
(3 (1X, D21.14)).

2.3.2
Crush 1: connectivities of the elements


PILE NUMERO 1 NBRE OBJETS NOMMES iobno NBRE OBJETS iob

If iobno is not null, there are two lines, one describing the names of the objects (8 (1X, A8) and the other
their position (16I5).

The named objects are the groups of nodes Aster to more than one node, the groups of Aster meshs
and meshs of the Aster model (if requested by the user by key word MODELE).

In the objects, one finds:

· the whole of the nodes of the grid in the form of meshs of the type POI1. This object is
essential during the reading of fields to the nodes. This object is not named and is
always the first object written in this pile,
· one
object
CASTEM 2000 for each group of Aster nodes to more than one node. It is
grids containing of the meshs of the type POI1,
· one
object
CASTEM 2000 for each group of Aster meshs. The object bears the name of the group
meshs in Aster,
·
grid
Aster: object named with same name as the Aster grid,
·
model
Aster (if it were stipulated in command IMPR_RESU by key word MODELE):
object named with same name as the Aster model.


Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
8/24

Note:

In Aster, a group of nodes and a group of meshs can have even name.
The interface writes the two objects with format CASTEM 2000 pennies the same name but under two
forms distinct (meshs of the type POI1 for the group of nodes and meshs of the group of
meshs).
Taking into account about writing in file CASTEM 2000, it is the object associated with
group meshs which is accessible.

Then, for each grid object, a line describes this object:


--> itype nbsd nbref nbnoe nbelem

itype: number of the type of element grid (I5)


1:
POI1

2:
SEG2

3:
SEG3

4:
TRI3


6:
TRI6

8:
QUA4
10:
QUA8
14:
CUB8

15:
CU20
16:
PRI6
17:
PR15
23:
TET4

24:
TE10
25:
PYR5
26:
PY13







0: if the object is composed of under objects

nbsd: numbers of under objects (I5)
For the interface, the number of under objects is the number of the types of meshs
composing the grid object.
(A group of meshs made up of triangles and quadrangles will be written in the form of
three objects CASTEM 2000:
·
under object containing the triangles,
·
under object containing the quadrangles,
·
a named object pointing on the two other objects)

nbref: a number of references (=0, I5)

nbnoe: a number of nodes per element (I5) (=0 if object pointing on under objects)

nbelem:
a number of elements (I5) (=0 if object pointing on under objects)

Note:

Under object of a given object is the standard whole of the elements in the same way being able to be
extracts. If the object consists of only one type of elements, there is not under objects.

If nbsd0, the list of the rows of under objects is registered with the line according to (16I5).
If itype=0, then necessarily nbsd0. That means that object is with a grid with elements of
different types.

If nbsd=0,

One finds then the list of the numbers of the colors of each element



ICOLOR (I), I=1, nbelem (16I5)

Then the list of the numbers of the nodes “nodes” of the elements



(NUM (I, J) I=1, nbnoe), j=1, nbelem (16I5)


Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
9/24

2.3.3
Crush 2: field with the nodes


PILE NUMERO 2 NBRE OBJETS NOMMES iobno NBRE OBJETS iob

This pile makes it possible to write cham_no Aster. The cham_no can be fields of size
named or of the fields of size resulting from a concept result (in which case they are not
expressly named).


iobno = 1 if cham_no named Aster


0 if associated a reference symbol of a concept result

iob = 1

--> If iobno0, the two following lines appear in the file with format CASTEM 2000:

· name

CHAM_NO Aster (1X, A8),
·
number of occurrence of the field to the nodes in file CASTEM 2000 (I5).


--> nbsch nbcmp ifour (3I5)

nbsch: of “under fields to the nodes” = 1 (one numbers considers that all the nodes have it
an even number of degrees of freedom; the envelope of the degrees of freedom present).

nbcmp: component count present at the nodes: wrap components.

ifour:2 = standard of three-dimensional calculation


--> ipgeo nbpoin nbcmp (3I5)

ipgeo: pointer in the pile of connectivities of the elements = 1 (the object made up of
elements of the type POI1 associated with all the nodes with the grid is always written at the beginning of
the pile of connectivities).

nbpoin: a number of points of the grid.

nbcmp: component count (idem that on the preceding line).


--> NOMCMP (I) (1:4), I=1, nbcmp 16 (1X, A4)

list names of the components. They are the first four characters of the name of
Aster components, except for displacements (DX becomes UX, DY becomes UY, DZ becomes
UZ, DRX becomes X-ray, DRY becomes RY and DRZ becomes RZ).


--> NOHARM (I), I=1, nbcmp (16I5)

corresponds to the numbers of the harmonics of Fourier. These parameters are identically
null in the case of the Aster interface - CASTEM 2000.


--> Name of the size (1X, A71).

--> 1 white line

--> (Value of the field (I, J), I=1, nbpoin), j=1, nbcmp) (3 (1X, E21.14)).


Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
10/24

2.3.4
Crush 39: field by element


PILE NUMERO 39 NBRE OBJETS NOMMES iobno NBRE OBJETS iob

This pile makes it possible to write cham_elem with the Aster nodes. The cham_elem with the nodes can
to be named fields of sizes or fields of size resulting from a concept result (in
which case, they is not expressly named).


iobno = 1 if cham_elem with the nodes named in Aster


0 if associated a reference symbol of a concept result

iob = 1

--> If iobno0, the two following lines appear in the file with format CASTEM 2000:

· name

CHAM_ELEM Aster (1X, A8),
·
number of occurrence of the cham_elem to the nodes in file CASTEM 2000 (I5).


--> nzone ifour lcomp nbcar (4I5))

nzone: numbers of under zones. It is equal to the number of the type of elements present, in
model.
A model made up of triangles and quadrangles are composed of two pennies zones.

ifour: type of three-dimensional calculation = 2

lcomp: 4

nbcar: a number of characters composing the type of the cham_elem = 16

--> title of the cham_elem: name of the size Aster (1X, A71)



(except
CONTRAINTES for sizes SIEF * or SIGM *

DEFORMATIONS
for

sizes
EPSI *
)

--> (n1 N2 n3 n4 n5 n6 n7) X nzone (16 I5)

n1: pointer in the pile of connectivities of the elements. Number of occurrence of the model
Aster (or of its under objects if nzone 0) in the pile of connectivities

N2
: 0
n3
: component count of under zone
n4: 0
n5
: 0
n6: 0
n7
: 0
(cham_elem defined in the nodes. Documentation available does not indicate
value for cham_elem at the points of Gauss).

--> For each component of under zone, number of the harmonic (16I5).
n3 X (0.) X nzone


Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
11/24

--> Name of components (NOMCMP (I) (1:8), I=1, n3) X nzone (8 (1X, A8))

The names of components are composed of the first 2 characters concaténés with
the last 2 characters of the name of the Aster component.
For the internal variables, there are VAR1, VAR2,…
For the components of constraints, SiXX becomes SMXX,…, SiYZ becomes SMYZ.

--> Standard of the components (“REAL * 8”) X n3 X nzone 4 (1X, A16)

--> Value of the field by element to the nodes in each under zone



--> n1 N2 0 0 (16I5)

-->
(VAL
(I, J), i=1, n1)
(j=1, N2)
(1P, 3e22.14)

n1: a number of nodes defining the meshs of under zone considered.
N2: a number of elements of under zone considered.

2.4
Writing of a concept Aster result with format CASTEM 2000

The concepts Aster results are written with format CASTEM 2000, in the shape of tables.

The piles necessary to the writing of a table are (in the order and for each sequence number):

·
Crush 27: crush of word type, allows to have the list of the “concepts” available for the table:
variables of access, sequence number, fields to the nodes, fields by element. That gives them
indices “character” of the table, and makes it possible to extract from the table, a reality, an entirety, a field
with the nodes, or a field by element.

U
=
Count
.
1
.
DEPL
It is the word DEPL which appears in pile 27.

· Crush 26: crush entireties; allows to write the value of the sequence number and the value of
variables of access of the whole type. Pile 26 appears for each variable of access and for
sequence number, and this for all the sequence numbers.

·
Crush 25: crush realities, allows to write the value of the variables of access of the real type. This pile
appears for each variable of access and each sequence number.

·
Crush 2: field with the nodes (format describes previously),

·
Crush 39: field by elements (format describes previously),

·
Crush 10: description of the table. Give the occurrence of each object constituting the table in
the file with format CASTEM 2000. For example, the field with the nodes with the sequence number 10
is the 50ème object of the field type to the nodes stored in the file.

2.4.1
Crush 27: Crush word type


PILE NUMERO 27 NBRE OBJETS NOMMES 0 NBRE OBJETS iob

iob = a number “of objects” constituting table CASTEM 2000 for a given sequence number. These objects
are identified by a character string of 4 characters.

The objects present are:

·
ORDR, whole value of the sequence number,
·
the first 4 characters of the variables of access (for example: INST,…),
·
the first 4 characters of the name of the size associated with the fields with the nodes and/or with
fields by element (for example: DEPL, SIGM,…).

It is thus supposed that numbers it variables of access and fields is identical for all them
sequence numbers, and which they are in the same way standard.

Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
12/24

The following recordings are then present in the file:


--> ncar nmot (2I5)

ncar: total characters = iob * 4 numbers
nmot: word count = iob.


--> character string (A72)

for example ORDRINSTDEPLSIGM for a concept result which has the moment for
variable of access, a field with the nodes of the displacement type and a field by element of
type forced.


--> (npos) X iob (12I5)

pointers on the preceding character string.

2.4.2
Crush 26: Crush entireties



PILE NUMERO 26 NBRE OBJETS NOMMES 0 NBRE OBJETS iob

·
If writing of the value of the sequence number:


iob
=
2
*
NBORDR

where NBORDR = a number of sequence numbers present in the concept result

Then 2 recordings follow; the first is an entirety which is equal to 2 * NBORDR (I5), it
second is a list of entireties (I, value of the ième sequence number), I = 1, NBORDR (7I11).

·
If writing of a variable of access of the whole type:


iob
=
1

Then 2 recordings follow; the first is 1 (I5) and the second the value of the variable
access (2I11).

2.4.3
Crush 25: Crush realities


PILE NUMERO 25 NBRE OBJETS NOMMES 0 NBRE OBJETS iob

This pile makes it possible to write the actual values of the variables of access of the concepts results, and is written
for each variable of access and each sequence number:


iob
=
1

Then 2 recordings follow; the first is 1 (I5) and the second the value of the variable of access
(1X, 1P21.14).


Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
13/24

2.4.4
Crush 10: descriptor of the table


CRUSH NUMBER 10 NO. OBJECTS NAME 1 NO. OBJECTS 2

This pile makes it possible to define the structure of the table (which is in fact a table of tables) while giving
position of the piles constituting the table (order of appearance in the file with format CASTEM 2000).

The recordings necessary to the description of the table are:


--> name of the table which is not other than the name of the concept result Aster (1X, A8)


--> nbobj (I5)
It is the word count constituting the pile of the word type.


--> ncar (I5)
It is the total number of characters indicated in the pile of the word type.


--> (27 posmot numpile position) X nbobj (16I5)

27: crush of word type.
posmot: entirety indicating the occurrence in the character string appearing in the pile of
word type.
numpile: number of the pile containing information relating to the occurrence posmot (26, 25, 2
or 39).
position: occurrence of the pile in the file with format CASTEM 2000.

For example: Let us suppose that in the pile of the word type, one has ORDRINSTDEPLSIGM.

The table consists of four objects:

·
an object of the whole type (associate with chain ORDR), which is stored in a pile of
number 26, which contains the value of the sequence number, and which for the sequence number
considered is the ième table of this type,
·
an object of the real type (associate with chain INST) which is stored in a pile of number
25, which contains the value of the moment and which for the sequence number considered is
jème table of this type,
·
an object of the field type to the nodes (associate with chain DEPL) which is stored in one
crush number 2, which contains the values of the field of displacement in all the nodes
grid, and which for the sequence number considered are the kème table of this type,
·
an object of the field type by elements (associate with chain SIGM) which is stored in one
crush number 39, which contains the values of the stress field, and which for
sequence number considered is the lemma counts of this type.



27 1 26 I 27 2 25 J 27 3 2 K 27 4 39 L


--> 4 X number command (I5)


--> 26 numéroordre 10 numérotable


Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
14/24

3
Structure of the universal file

IDEAS


The total structure of a universal file IDEAS is presented in the form of datasets characterized by
their number.

Each dataset is framed by the line “- 1”:


-
1


dataset



-



-



-

-
1

-
1


dataset



-



-



-

-
1

Each dataset contains a particular type of information (coordinated nodes, connectivities of
meshs, results with the nodes,…), and is characterized by a number and a data-processing structure
clean.

However, the numbers of dataset and their data-processing structure are not solidified and can vary
of a version to another.

Command IMPR_RESU makes it possible to print grids, and results with the nodes or by
elements, and this, with the choices of the user, in version 4 or 5 of IDEAS.

So the number of datasets written by command IMPR_RESU is reduced:

Version 4
Version 5

151.151 Titrate
775
775
Properties of the beams
15

Co-ordinates of the nodes in single precision

781
Co-ordinates of the nodes in double precision
71
780
Connectivity of the meshs
752
752
Groups of nodes and meshs
55
55
Results with the nodes (cham_no)
56
56
Results by elements (cham_elem at the point
of Gauss)
57
57
Results with the nodes by elements
(cham_elem with the nodes)


Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
15/24

3.1
Dataset 151: Titrate


-
1

151% Title

Vxx.xx.xx aster of the date result of the date-stamp (A80)

1ère
line

titrate
Aster
(A80)

2nd
line

titrate
Aster
(A80)

line
white
(A80)

4th
line

titrate
Aster
(A80)

5th
line

titrate
Aster
(A80)

6th
line

titrate
Aster
(A80)

-
1

This dataset is always the first dataset written in universal files IDEAS generated by
order IMPR_RESU.

3.2
Dataset 775: Properties of the beams

This dataset is obligatory when the grid comprises elements of the beam type, and appears then
just after the dataset 151.


-
1

775% Properties can section beams

1
0
0
(3I10)

BEAM1

0.
0.
0.
0.
0.
0.
(6 (1PE13.6))

0.
0.
0.
0.
(4 (1PE13.6))

0.
0.
0.
0.
0.
0.
(6 (1PE13.6))

0.
0.
0.
0.
0.
0.


0.
0.
0.
0.
0.
0.


0.
0.
0.
0.
0.
0.


0.
0.
0.
0.
0.
0.


0.
0.
0.
0.
0.
0.


0.
0.
0.
0.
0.
0.


11
7
8
14
1
10
(6I10)

0
45
1
11
1.
(4I10,1PE13.6)

-
1

3.3
Dataset 15: Co-ordinates of the nodes in single precision

If the user requests the writing of a grid from the format universal file IDEAS version 4, them
coordinated nodes are written in single precision, in the form of this dataset.


-
1

15% Nodes

N
0
0
11
X
Y
Z
(4I10,3E13.6)

·
·
·
·
·
·
·

·
·
·
·
·
·
·

-
1

N: number of the node (it is the Aster number except if the grid were generated by IDEAS, in which case
it is number IDEAS).

Following information relates to the definition of the frame of reference which in Aster is always
the Cartesian reference mark, from where value 0.


Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
16/24

The fourth information indicates the color affected during the display of the node.

X, Y, Z are the three co-ordinates of the node.

With each node of the grid a line in the dataset 15 corresponds.

3.4
Dataset 781: Co-ordinates of the nodes in double precision

If the user requests the writing of a grid from the format universal file IDEAS version 5, them
coordinated nodes are written in double precision, in the form of this dataset.


-
1

781% Nodes Real * 8

N
0
0
11
(4I10)

for
each
node

X
Y
Z
(3e25.17)

·
·
·
·

·
·
·

-
1

N: number of the node (it is the Aster number except if the grid were generated by IDEAS, in which case
it is number IDEAS).

Following information relates to the definition of the frame of reference which in Aster is always
the Cartesian reference mark, from where value 0.

The fourth information indicates the color affected during the display of the node.

X, Y, Z are the three co-ordinates of the node.

With each node of the grid two lines in the dataset 781 correspond.

3.5
Dataset 71: Connectivities of the meshs

If the user requests the writing of a grid from the format universal file IDEAS version 4, them
connectivities of the meshs are written in the form of this dataset.


-
1

71% Elements

IMAS ICOD1 ICOD2 IPHY IMAT 7 NO





(7I10)

NODSUP
(J),
J=1,
NOAH
(8I10)

·

·
·
·
·

·

·

-
1

The two lines of information indicated are written for each element of the grid.

IMAS: Number of the mesh. It is the Aster number except if the grid were generated by IDEAS, in
which case it is number IDEAS.

Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
17/24

ICOD1: Code graphic element.

Code graphic
Net
Nodes
Type
1 Linear
2
Linear
2 Triangle
3
Linear
3 Triangle
6
Quadratic
4 Triangle
9
Cubic
5 Quadrilateral
4
Linear
6 Quadrilateral
8
Quadratic
7 Quadrilateral
12
Cubic
14 Tetrahedron
4
Linear
15 Tetrahedron
10
Quadratic
16 Pentahedron
6
Linear
17 Pentahedron
15
Quadratic
18 Pentahedron
24
Cubic
19 Hexahedron
8
Linear
20 Hexahedron
20
Quadratic
21 Hexahedron
32
Cubic

ICOD2: Descriptor of the finite element

By defect, a value of the descriptor is assigned to each type of mesh. That is done when
the user did not specify of Aster model and that one thus does not have the knowledge of the type of
the finite element.

Type of mesh
Descriptor

POI1
161 (lumped
farmhouse)
SEG2
21 (linear
beam)
SEG3
24 (parabolic
beam)
TRIA3
74
(membrane linear triangle)
TRIA6
72
(membrane parabolic triangle)
TRIA9
73
(membrane cubic triangle)
QUAD4
71
(membrane linear quadrilateral)
QUAD8
75
(membrane parabolic quadrilateral)
QUAD12
76
(membrane cubic quadrilateral)
TETRA4
111
(solid linear tetrahedron)
TETRA10
118
(solid parabolic tetrahedron)
PENTA6
112
(solid linear wedge)
PENTA15
113
(solid parabolic wedge)
HEXA8
115
(solid linear brig)
HEXA20
116
(solid parabolic brig)

When the user provided a name of model, one refines these default values by holding account
type of the finite element. The elements concerned are:

MEAXQU4/THAXQU4
--> 84
(Quadrilateral Axi linear)
MEAXQU8/THAXQU8
--> 85
(Quadrilateral Axi parabolic)
MEAXTR3/THAXTR3
--> 81
(Axi linear triangle)
MEAXTR6/THAXTR6
--> 82
(Axi parabolic triangle)
MEDPQU4/THDPQU4
--> 54
(Strain linear Planes quadrilateral)
MEDPQU8/THDPQU8
--> 55
(Strain parabolic Planes quadrilateral)
MEDPTR3/THDPTR3
--> 51
(Strain linear triangle Planes)
MEDPTR6/THDPTR6
--> 52
(Strain parabolic triangle Planes)

Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
18/24

MECPQU4/THCPQU4
--> 44
(Planes quadrilateral stress linear)
MEPLQU4/THPLQU4


MECPQU8/THCPQU8
--> 45
(Planes quadrilateral stress parabolic)
MEPLQU8/THPLQU8


MECPTR3/THCPTR3
--> 41
(Stress linear triangle Planes)
MEPLTR3/THPLTR3


MECPTR6/THCPTR6
--> 42
(Stress parabolic triangle Planes)
MEPLTR6/THPLTR6


MEAXSE2/MECPSE2
--> 21
(Linear beam)
MEDPSE2/MEPLSE2


THAXSE2/THCPSE2


THDPSE2/THPLSE2


MEDKQU4/MEDSQU4
--> 94
(thin hull: Quadrilateral TN linear)
MEQ4QU4
MEDKTR3/MEDSTR3
--> 91
(thin hull: TN linear triangle)

IPHY: number of the table of the physical properties = Aster number associated with the type of mesh or it
Aster number associated with the type with the finite element if a model were specified by the user.

IMAT: number of the table of the characteristics material = 1 except for the meshs reduced to a point
in which case IMAT is worth 2.

The following recording indicates the color of the element during its display in IDEAS (by defect
7 green color).

NOAH: a number of nodes defining the mesh.

NODSUP (J), J=1, NO: list numbers of nodes composing the mesh.

Note:

The Aster meshs not existing in IDEAS are ignored by interface (QUAD9, HEXA27).

3.6
Dataset 780: Connectivities of the meshs

If the user requests the writing of a grid from the format universal file IDEAS version 5, them
connectivities of the meshs are written in the form of this dataset.


-
1

780% Elements

IMAS ICOD2
1
IPHY 1
IMAT 7
NOAH (8I10)

NODSUP (J),
J=1,
NOAH (8I10)

% if meshs linear

IMAS ICOD2
1
IPHY 1
IMAT 7
NOAH (8I10)

0
1
1
1
1
(5I10)

NODSUP (J),
J=1,
NOAH (8I10)

-
1

Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
19/24

IMAS: number of the mesh. It is the Aster number except if the grid were generated by IDEAS, in
which case it is number IDEAS.

ICOD2: descriptor of the finite element (see description dataset 71).

IPHY: number of the table of the physical properties (see description dataset 71).
IMAT: number of the table of the characteristics material (see description dataset 71).

The following recording indicates the color of the element during its display in IDEAS (by defect
7 green color).

NOAH: a number of nodes defining the mesh.

Note:

To write an element of beam, there is an additional line in the dataset 780. This
line defines the characteristics of the beam, inter alia, the number of the node being useful for
orientation of the principal directions of the beam. Values written by the command
IMPR_RESU are values can.

The Aster meshs not existing in IDEAS are ignored (QUAD9, HEXA27).

3.7
Dataset 752: Groups of nodes and meshs


-
1

752% Groups

NUM
0
0
0
0
NBRE (6I10)

NOM
(20A2)

(ICOD,
MUMENT)
I=1,
NBRE
(8I10)

·
·
·
·
·
·

·

·
·

-
1

For each group of nodes or Aster meshs, one writes the instructions indicated previously.

NUM: Number of the group. It is sequential; one starts with the groups of nodes in the order of
their appearance in Aster.

NBRE: A number of nodes or meshs composing the group.

NOM: Name of the group. It is the name Aster.

ICOD: It is a code indicating the type of the entity the following. 7 indicates that the number which follows it is
that of a node, 8 indicates that the number which follows it is that of a mesh.

NUMENT: Number of the entity (number of a node or a mesh).

Note:

The third line is as many repeated once as necessary to write all the numbers of
nodes or of meshs composing the group.


Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
20/24

3.8
Writing of the Aster results: CHAM_GD or Concept RESULTAT

The three datasets being used to write the Aster results are the datasets 55 (for fields with
nodes), 56 (for fields by elements at the points of Gauss) and 57 (for fields by
elements with the nodes).

3.8.1
Dataset 55: Values with the nodes



MODTYP: type of the model
MODTYP = 1 Structural

MODTYP = 2 Heat transfer

Command IMPR_RESU takes MODTYP = 1 except when the size associated with the field with
to print is TEMP or FLUX, in which case MODTYP = 2.

ANATYP: type of analysis

ANATYP =0
UNKNOW
Value taken by defect by the command
IMPR_RESU
=1
STATIC Valeur taken during the impression of fields of
size named in Aster
=2
NORMAL
MODE
Value taken during the impression of a concept
result having for variable of access NUME_MODE
=4
TRANSIENT
Value taken during the impression of a concept
result having for variable of access INST
=5
FREQUENCY
Value taken during the impression of a concept
RESPONSE
result having for variable of access FREQ and
not NUME_MODE

Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
21/24

DATCAR = characteristic of the data

=1
scalar
=3
vector with 6 degrees of freedom (3 translations and 3 rotations)
=4
symmetrical tensor

DATTYP = standard of the data

=0
unknown
=2
constraints
=3
deformations
=5
temperature
=6
flow
=8
displacement
=11
speed
=12
acceleration
=15
pressure

TYPE = 2 for actual values, 5 for complex values.

NBRE = a number of values to be printed by node.

NUMOR = sequence number Aster for the concepts results.

IMODE = value of the variable of access NUME_MODE for the sequence number considered (for
concepts result having this variable of access).

FREQ = value of the variable of access FREQ for the sequence number considered (for the concepts
result having FREQ for variable of access).

MASGEN = value of parameter MASSE_GENE for the sequence number considered (for the concepts
results having NUME_MODE for variable of access).

AMOR1 = value of parameter AMOR_REDUIT for the sequence number considered (for the concepts
result having NUME_MODE for variable of access).

AMOR2 = 0.D0

INST = value of the variable of access INST for the sequence number considered (for the concepts
result having INST for variable of access).

NBRE = a number of values of the result by node.
NUMNOE = number of the node.
VALE = values of the result (cham_no) to the node considered.


Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
22/24

3.8.2
Dataset 56: Values by elements



The heading of this dataset is identical to that of the dataset 55.

NUMMAI = number of the mesh.
NBVAL = a number of values on the mesh.
VALE = values of the result (cham_elem at the points of Gauss) on the mesh considered.
cham_elem at the points of Gauss Aster is written with format IDEAS in the form of constant fields
by element (average of the values at the points of Gauss).


Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
23/24

3.8.3
Dataset 57: Values with the nodes by element



The heading of this dataset is identical to that of the dataset 55 and 56.

NUMMAI = number of the mesh.
NBNOE = a number of nodes of the mesh.
NBVAL = a number of values per node.
VALEJ = values of the result (cham_elem to the nodes) on the node J of the mesh considered.

3.9
Writing rule of a dataset of results

In Code_Aster, the fields of size are fields with the nodes or fields by
element at the points of Gauss or the nodes.
The fields with the nodes are written in the form of datasets number 55, the fields by elements with
points of Gauss in the form of datasets number 56 and fields by element with the nodes under
form datasets 57.

For the concepts result, one treats sequence number per sequence number and reference symbol by name
symbolic system, various fields of size composing the concept result.

The only difference in the writing of the datasets 55, 56 and 57 is the value of the code corresponds to the type
from analysis (ANATYP) which are worth 1 for the fields of size named in Aster, and 2, 4 or 5 for
concepts results (see description dataset 55).


Handbook of Référence
D9.07 booklet:
Index A

Code_Aster ® Version
3


Titrate:
Data-processing description of IMPR_RESU


Date: 19/09/2003
Author (S):
A. Mr. DONORE

Key: D9.07.01
Page:
24/24

In Code_Aster, a field of size is associated a size of which the list of the components
possible is defined in a catalog. The various components can be vectors,
tensors or of the scalars.

In IDEAS, a dataset includes/understands to the maximum 6 components, and these components are typified:

·
vectors with 6 components of the displacement type, speed, acceleration, flow or unknown,
·
symmetrical tensors of type forced or deformations,
·
scalars of the temperature type or pressure.

Also, one associates a Aster size a finished number of datasets IDEAS likely to be written (if
the components really exist on the model). It is the IRGAGS.f routine which carries out this work.

Let us consider for example the size DEPL_R whose components are DX, DY, DZ, DRX,
DRY, DRZ, GRX, DDZDN, NEAR, PHI.

With a field with the nodes associated with this size to the maximum three datasets IDEAS (all corresponds
three of number 55):

·
a dataset of the vector type to 6 components for the writing of DX, DY,… DRZ,
·
a dataset of the scalar type for the writing of PRES,
·
a dataset of the unknown type for the writing of components GRX, DDZDN, PHI.

These datasets can then exist or not according to the presence or not components. The dataset
exist as soon as one of the components the component is defined on a node of the grid (in which
case the value of the components absent is 0.).

With regard to the internal variables, one generates an one or more (dataset includes/understands with
maximum 6 components) datasets of number 55 and type “UNKNOWN”.

4
Structure of the file

ENSIGHT


The description of format ENSIGHT will be integrated into a forthcoming version of this document.

5 Bibliography

[1]
R. GALLON, H. BUNG. Ratio DMT/91.127. Program Plexus: outputs on files
for postprocessing by CASTEM 2000. 04/03/1991.

[2]
Mr. FARVACQUE. Ratio DEMT/86/411. CASTEM 2000: Informatique note of
operators SAUVER-RESTITUER. 28/10/1986.

[3]
D. RICHARD. Structure of the backup file of CASTEM 2000. Report/ratio
SCA/92.022. 31/08/1992.

[4]
User' S Guide “Core utilities”. I-DEAS. SDRC.


Handbook of Référence
D9.07 booklet:
Index A

Outline document