Code_Aster ®
Version
7.4
Titrate:
Procedure IMPR_RESU with format “ENSIGHT”


Date:
10/02/05
Author (S):
Key COURTEOUS Mr.
:
U7.05.31-H Page
: 1/8

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

Handbook of Utilization
U7.0- booklet: Data exchanges
Document: U7.05.31

Procedure IMPR_RESU with format “ENSIGHT”

1 Goal

To write a grid and/or results of a calculation on files with format “ENSIGHT”.

Currently this procedure makes it possible to write with the choice:

·
a grid,
·
fields with the nodes (of displacements, temperatures, clean modes, modes
statics,…),

For the concepts of the result type, one can print only part of information, in
selecting the fields and the sequence numbers which one wishes to exploit.

Handbook of Utilization
U7.0- booklet: Data exchanges
HT-66/05/004/A

Code_Aster ®
Version
7.4
Titrate:
Procedure IMPR_RESU with format “ENSIGHT”


Date:
10/02/05
Author (S):
Key COURTEOUS Mr.
:
U7.05.31-H Page
: 2/8

2 Syntax
IMPR_RESU
(

MODELE= MO,
[model]

FORMAT
=/“ENSIGHT”,

UNITE = links,

RESU =_F (

| MAILLAGE
=
MA,
/
[grid]
/
[skeleton]



| /CHAM_GD = CH_GD,


/
RESULTAT
=
RESU,






# Extraction of a field of size of resu








/
TOUT_CHAM
=
/“YES”, [DEFECT]






/“NON”,







/

NOM_CHAM = L_NOMSYMB, [l_K16]








/

TOUT_ORDRE =
“OUI”,
[DEFAUT]







/

NUME_ORDRE =
LORDRE, [l_I]
/
LIST_ORDRE =
LENTI,
[listis]







/

NUME_MODE
=
LMODE,
[l_I]
/
NOEUD_CMP
=
LNOECMP,
[l_K16]
/
NOM_CAS =
NCAS,
[l_K16]
/
ANGL =
LANGL,
[l_K16]
/
/
FREQ =
LFREQ,
[l_R]
/
LIST_FREQ
=
LREEL,
[listr8]
/
INST =
LINST,
[l_R]
/
LIST_INST
=
LREEL,
[listr8]









| PRECISION =/PREC,
[R]
/
1.0D-3
[DEFAUT]









|
CRITERION =/“RELATIVE” [DEFECT]
/
“ABSOLU”


# Selection of the components



/
TOUT_CMP
=
“OUI”,
[DEFAUT]



/
NOM_CMP =
L_NOMCMP,
[l_K8]


)
)
Handbook of Utilization
U7.0- booklet: Data exchanges
HT-66/05/004/A

Code_Aster ®
Version
7.4
Titrate:
Procedure IMPR_RESU with format “ENSIGHT”


Date:
10/02/05
Author (S):
Key COURTEOUS Mr.
:
U7.05.31-H Page
: 3/8

3 Formats
of writing

Procedure IMPR_RESU makes it possible to write a grid and/or values of results to the format
“ENSIGHT” (EnSightTM marketed by company CEI) for a graphic visualization.

EnSightTM is an accessible software on workstation.

One asks for the creation of files ASCII, which could be read again by EnSightTM.

In the interface astk, the user must indicate a name of repertory and choose the type of files ensi.

The files produced by IMPR_RESU, FORMAT “ENSIGHT” will be deposited in this repertory at the end
calculation.

The names of the files produced in this repertory are automatically defined in the procedure
IMPR_RESU starting from the names of the concepts handled by the user, the names of the fields that they
contain and their components (see operand CHAM_GD and operand RESULTAT).

4 Word
key
RESU

This key word factor makes it possible to specify the results to print and the format according to which one wants them
to print.

5
Impression of the grid: operands MAILLAGE/MODELE

Operand MAILLAGE makes it possible to print the grid with format “ENSIGHT”. Impression of the grid
can be asked only only once and before any other result.

Concept of the model type is optional in the majority of the impressions. It can also be
used in the case of the impression of a grid, which can seem redundant with the operand
MAILLAGE: it is not wanted, in this case, to print that the part of the grid whose meshs are affected
in the model.

With format “ENSIGHT”, the classification of the nodes is that of Aster except when the grid results from
software I-DEASTM (one checks the presence of the character string AUTEUR=INTERFACE_IDEAS
in the first line of the title of the grid and starting from the tenth position); in this case one restores
classification IDEAS.

With format “ENSIGHT”, one writes a NOM_MAILLAGE.geo file in the repertory defined by the user
in the interface astk (NOM_MAILLAGE indicates the name allotted to the grid by the user). One y
print:

·
a first “share” EnSightTM containing all the meshs of the grid and whose name is
that of the Aster grid,
·
then for each group of Aster meshs a “share” of the same name than the group.

The groups of nodes are not printed in the NOM_MAILLAGE.geo file and the finite elements
Aster QUAD9 and PENTA15 are respectively reduced in QUAD8 and PENTA6.

Handbook of Utilization
U7.0- booklet: Data exchanges
HT-66/05/004/A

Code_Aster ®
Version
7.4
Titrate:
Procedure IMPR_RESU with format “ENSIGHT”


Date:
10/02/05
Author (S):
Key COURTEOUS Mr.
:
U7.05.31-H Page
: 4/8

6 Operands
CHAM_GD and RESULTAT

The values of the computed fields are stored in structures of data called fields of
size. These fields of size can be directly accessible (concept cham_gd) where
to find in a structure of data gathering several fields of size (concept
result).

·
A field of size is a structure of data which makes it possible to store definite fields
with the nodes (cham_no_ *) or fields defined by elements (cham_elem_ *). For the fields
by elements, one distinguishes the fields defined in the nodes from the elements and the fields defined in
points of GAUSS of the elements.
·
A concept result is composed of one or more fields of size. For example, with
each step of calculation one stores in the structure of data result, the field of size
displacement. This structure is thus a matric structure of command 2, whose index is, by
example, the list of the moments of calculation and the other the whole of the computed fields (displacements,
constraints, deformations,…).

One reaches in this case a field of size by specifying a value of a variable of access
(sequence number, moment, frequency, number of mode…) and a field name (“DEPL”,
“SIGM_ELNO_DEPL”,…). There are several types of concept result: evol_elas,
evol_noli, mode_meca,…. With each one corresponds a list of fields and a list of variables
licit accesses (cf [U5]).

Taking into account the structure of data result, one understands easily that the possibilities
of impression which one lays out are those of the fields of size, supplemented by
specific possibilities.

Note:

With format “ENSIGHT”, one can treat only the fields with the nodes: fields by
elements with the nodes or the points of GAUSS must thus be transformed into fields with
nodes via command CALC_NO [U4.81.03] before the call to the procedure
IMPR_RESU.

Currently, EnSightTM handles only scalar real variables and variables
vectorial (3 values per file).

·
Scalar variable

With each scalar component of a Aster size is associated a EnSightTM file which
contains the values of this component in all the nodes of the grid.

·
Vectorial variable

One regards as vectorial variables, the components of a field of size which
can be gathered in a vector quantity with three components (component
FLUX, FLUY, FLUZ of the size flu_, component DX, DY, DZ of the size depl_).

For each vectorial variable one writes a “vectorial” file containing the three values of
vector in all the nodes of the grid.

Note:

For the size depl (component DX, DY, DZ), one generates moreover three files
scalars containing the values of each component of the vector in all the nodes of
grid.

·
Tensorial variable

One treats the various terms of the tensor like scalar variables.
Handbook of Utilization
U7.0- booklet: Data exchanges
HT-66/05/004/A

Code_Aster ®
Version
7.4
Titrate:
Procedure IMPR_RESU with format “ENSIGHT”


Date:
10/02/05
Author (S):
Key COURTEOUS Mr.
:
U7.05.31-H Page
: 5/8

Note:

The complex variables are described in two distinct scalar files of which one contains
the value of the real part in all the nodes and the other the value of the imaginary part.

6.1 Operand
CHAM_GD

A field of Aster size named U.S. 'supports on a size defined by its components.
According to the type of the component (scalar real, scalar complex, vectorial real, vectorial
complex), one produces 1 or several files as mentioned previously.

The name of the produced files follows the following rule:

·
Real scalar variable

1 named file
u.NOMCMP

·
Complex scalar variable

2 named files
u.NOMCMP.R

u.NOMCMP.I

·
Real vectorial variable

1 named “vectorial” file
U

·
Complex vectorial variable

2 named “vectorial” files
u.R

u.I

Note:

In all the cases, one generates in more one file u.res which describes the correspondence between
name of the variables to be visualized and the name of the corresponding files of values.

Examples:



IMPR_RESU (FORMAT = “ENSIGHT”
RESU = (_F (CHAM_GD = CONT,)
))

·
The field with the nodes of name CONT is a real stress field having for components
SIXX, SIYY, SIZZ, SIXY, SIXZ, SIYZ.

Seven files are created in the repertory of the user.

CHAM_GD.res

correspondence enters the name of the variables to visualize and the name of the files of values
correspondents,

CONT.SIXX, CONT.SIYY, CONT.SIZZ, CONT.SIXY, CONT.SIXZ, CONT.SIYZ containing
the value of each component in all the nodes of the grid.


IMPR_RESU (FORMAT = “ENSIGHT”
RESU = (_F (CHAM_GD = DEPLA,)))

·
The field with the nodes of name DEPLA is a field of real displacements having for
components DX, DY, DZ, DRX, DRY, DRZ.

Eight files are generated in the repertory result.
Handbook of Utilization
U7.0- booklet: Data exchanges
HT-66/05/004/A

Code_Aster ®
Version
7.4
Titrate:
Procedure IMPR_RESU with format “ENSIGHT”


Date:
10/02/05
Author (S):
Key COURTEOUS Mr.
:
U7.05.31-H Page
: 6/8

CHAM_GD.res

correspondence enters the name of the variables to visualize and the name of the files of values,

DEPLA

file of vectorial variables gathering the value of components (DX, DY and DZ) in all them
nodes,


DEPLA.DX DEPLA.DY DEPLA.DZ DEPLA.DRX DEPLA.DRY DEPLA.DRZ

scalar files of variables containing the value of each component.

Note:

The user can reduce the number of files generated by using operand NOM_CMP.
In the case of a field of displacements, if the user specifies
NOM_CMP = (DX, DY, DZ), one creates only the file containing the vectorial variable
(components DX, DY and DZ).

6.2 Operand
RESULTAT

Operand RESULTAT makes it possible to print the fields contained in a concept result. One can
for example to choose to print only certain fields (Cf. the following key word: NOM_CHAM).

With format “ENSIGHT”, the concept result is written sequence number per sequence number and field of
size by field of size.

The processing of the fields of size extracted the concept result is described in [§6.1].

However the name of the produced EnSightTM files must take account of the structure of the concept result
(sequence number, reference symbol).

In a general way, a concept result of name resu defined by N sequence numbers and m names
symbolic systems contains n.m fields of size.

These fields of size do not have a name user also IMPR_RESU with format ENSIGHT them
give a fictitious name which is used like the name user of the field of size in the case of them
CHAM_GD:

RESU.NOMSYM.CHNUO1+CHIORD
if NBORDR > 1
RESU.NOMSYM.CHNUO1
if NBORDR = 1

with:

·
NOMSYM
reference symbol of the field in Aster (DEPL, SIGM_NOEU_DEPL,…),
·
CHNUO1
number of the first sequence number to be printed,
·
CHIORD
index of the sequence number in the course of impression (CHIORD makes it possible to respect
formats ENSIGHT),
·
NBORDR
numbers total sequence numbers to be printed.

The name of the EnSightTM files produced by IMPR_RESU follows then the rule exposed in [§6.1].

For example, for a field of size of N real components scalar, N files are produced.
Those are named resu.NOMSYM.CHNUO1+CHIORD.NOMCMP containing for each component
of name NOMCMP the value of the component in all the nodes of the grid.

In addition to the files of values, one generates a file of description named RESU.resCHNUO1 which
specify for the EnSightTM software the number of sequence numbers and the correspondence between the names
scalar and vectorial variables to visualize and names of the associated files of values.
Handbook of Utilization
U7.0- booklet: Data exchanges
HT-66/05/004/A

Code_Aster ®
Version
7.4
Titrate:
Procedure IMPR_RESU with format “ENSIGHT”


Date:
10/02/05
Author (S):
Key COURTEOUS Mr.
:
U7.05.31-H Page
: 7/8

Example:

IMPR_RESU
(
FORMAT
=
“ENSIGHT”,
RESU
= (_F (RESULTAT
=
FIL,
NUME_ORDRE
=
(1,2),
NOM_CHAM
=
(“DEPL”, “SIGM_NOEU_DEPL”),



















)))

The field of displacements to the nodes has as components DX, DY, real DZ.
The stress field to the nodes has as components SIXX, SIYY, SIZZ, SIXY, SIXZ, SIYZ
real.

The example led to creation, inside the repertory result of the user of the following files:

Number command 1

FIL.DEPL.1+0

file of vectorial variable containing displacement (components DX, DY, DZ)


FIL.DEPL.1+0.DX, FIL.DEPL.1+0.DY, FIL.DEPL.1+0.DZ

scalar files of variables containing the value of each component (DX, DY, DZ) in all
nodes of the grid.

FIL.SIGM_NOEU_DEPL.1+0.SIXX,
FIL.SIGM_NOEU_DEPL.1+0.SIYY
FIL.SIGM_NOEU_DEPL.1+0.SIZZ,
FIL.SIGM_NOEU_DEPL.1+0.SIXY
FIL.SIGM_NOEU_DEPL.1+0.SIXZ,
FIL.SIGM_NOEU_DEPL.1+0.SIYZ

scalar files of variables containing the value of each component (SIXX,…) in all them
nodes of the grid.

Number command 2

FIL.DEPL.1+1

file containing displacement (components DX, DY, DZ)


FIL.DEPL.1+1.DX, FIL.DEPL.1+1.DY, FIL.DEPL.1+1.DZ

files containing components DX, DY and DZ in all the nodes of the grid.

FIL.SIGM_NOEU_DEPL.1+1.SIXX,
FIL.SIGM_NOEU_DEPL.1+1.SIYY
FIL.SIGM_NOEU_DEPL.1+1.SIZZ,
FIL.SIGM_NOEU_DEPL.1+1.SIXY
FIL.SIGM_NOEU_DEPL.1+1.SIXZ,
FIL.SIGM_NOEU_DEPL.1+1.SIYZ

files containing components SIXX,… SIYZ in all the nodes of the grid.
Handbook of Utilization
U7.0- booklet: Data exchanges
HT-66/05/004/A

Code_Aster ®
Version
7.4
Titrate:
Procedure IMPR_RESU with format “ENSIGHT”


Date:
10/02/05
Author (S):
Key COURTEOUS Mr.
:
U7.05.31-H Page
: 8/8

7
Extraction of a field of size

7.1 Operands
TOUT_CHAM/NOM_CHAM

Cf document [U7.71.00].

7.2 Operands TOUT_ORDRE/NUME_ORDRE/LIST_ORDRE/
NUME_MODE/INST/LIST_INST/FREQ/LIST_FREQ/
NOEUD_CMP/NOM_CAS/ENG/PRECISION/CRITERION

Cf document [U7.71.00].

8
Selection on the components

Another manner of reducing the volume of the impressions is to print only the values of
certain components (for example that displacement following axis X: component DX).

Format “ENSIGHT” this selection on the components makes it possible to reduce the number of files
generated.

8.1 Operand
TOUT_CMP

This key word makes it possible to indicate that one wishes to print all the components of the field.

8.2 Operand
NOM_CMP

This key word makes it possible to choose the list of the components of the CHAM_GD or all the fields of the concept
result which one wishes to print.

Key words TOUT_CMP and NOM_CMP cannot be used simultaneously.

These components are described in the specific documentation of the elements.

Note:

With format “ENSIGHT”, and if the user specifies NOM_CMP = (“DX, DY, DZ”), one does not create
that the file containing the vectorial variable (corresponding to components DX, DY and DZ
[§6.2]).

9 Operand
UNITE

With format “ENSIGHT” the results are written in several formatted files whose names are
determined automatically starting from the names of the concepts, the fields of size and theirs
components (Cf. operand CHAM_GD and operand RESULTAT).
Consequently, operand UNITE does not have any effect with the format of impression “ENSIGHT”.

Handbook of Utilization
U7.0- booklet: Data exchanges
HT-66/05/004/A

Outline document