Procedure IMPR_RESU with format GMSH

Code_Aster

Version

8.2

Titrate:

Procedure

IMPR_RESU

format `

GMSH

Date:

22/02/06

Author (S):

COURTEOUS Mr., NR. TARDIEU

Key

U7.05.32-C1

Page:

1/6

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

Organization (S):

EDF-R & D/AMA

Instruction manual
U7.0- booklet: Data exchanges
Document: U7.05.32

Procedure

IMPR_RESU

with the format `

GMSH

1 Goal

To write a field of size or a concept result with the format

“GMSH”

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

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

fields by elements with the nodes (of stresses, generalized efforts, variables
interns…).

For the concepts of the type

result

, one can print only part of information, in

selecting the fields and the sequence numbers which one wishes to exploit.

It is possible to select the topological entities (meshs or groups of meshs) on which
one wants to print the results.

Code_Aster

Version

8.2

Titrate:

Procedure

IMPR_RESU

format `

GMSH

Date:

22/02/06

Author (S):

COURTEOUS Mr., NR. TARDIEU

Key

U7.05.32-C1

Page:

2/6

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

2 Syntax

IMPR_RESU

(

MODELE= Mo,

[model]

UNIT = links,

FORMAT

=/“GMSH”,

RESU

(

| /MESH = my,

[mesh]

[skeleton]

CHAM_GD =

ch_gd,

RESULT

resu,

# Extraction of a field of size of resu

/TOUT_CHAM

/“YES”, [DEFECT]

/“NOT”,

NOM_CHAM

l_nomsymb, [l_K16]

/TOUT_ORDRE = “YES”,

[DEFECT]

NUME_ORDRE =

lordre,

[l_I]

LIST_ORDRE =

lenti,

[listis]

NUME_MODE

lmode,

[l_I]

NOEUD_CMP

lnoecmp,

[l_K16]

NOM_CAS =

ncas,

[l_K16]

ENG =

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,

[DEFECT]

CRITERION

“RELATIVE”,

[DEFECT]

“ABSOLUTE”,

PART

=/“REAL”,

“IMAG”,

Selection of the topological entities

| NET

l_maille,

[l_maille]

GROUP_MA

l_grma, [l_gr_maille]

NOM_CMP =

l_cmp,

[l_K8]

VERSION =/

1.2,

[DEFECT]

1.0,

[R]

)

Code_Aster

Version

8.2

Titrate:

Procedure

IMPR_RESU

format `

GMSH

Date:

22/02/06

Author (S):

COURTEOUS Mr., NR. TARDIEU

Key

U7.05.32-C1

Page:

3/6

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

3 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.

4 Operands

CHAM_GD

and

RESULT

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

) or

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 fields
defined in the nodes (

cham_no_ *

) or of the fields defined by elements (

cham_elem_ *

). For

the fields by elements, one distinguishes the fields defined in the nodes from the elements and them
fields defined in the points of GAUSS of the elements.

A concept

result

is composed of one or more fields of size. For example, with

each pitch 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, including one
index is, for example, the list of the moments of calculation and the other the whole of the fields
calculated (displacements, stresses, deformations,…).

One reaches in this case a field of size by specifying a value of a variable
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

licit variables of access (cf [U5]).

Taking into account the structure of data

result

, it is understood easily that them

possibilities of impression which one lays out are those of the fields of size, supplemented
by specific possibilities.

Caution

One cannot print in the same file the MESH and the RESULT/CHAM_GD,

GMSH cannot read such a file. The control thus stops if the two key words

are present.

4.1 Operand

CHAM_GD

For

CHAM_NO

, the components of the field to the nodes are burst in a vector field

gathering the components

and

and in as many scalar fields there are others

components.

Example: In the case of a field with the nodes of size

DEPL

and whose modeling is of type

beam, one writes:

1 vector field (gathering the whole of the components of translation)

3 scalar fields (a field per degree of rotation).

For

CHAM_ELEM

, one prints only the fields by elements with the nodes (

_ELNO_

). One

field by elements with the nodes is burst in as many scalar fields there are components.

4.2 Operand

RESULT

The operand

RESULT

allows to print the fields contained in a concept result. One can

for example to choose to print only certain fields (cf the key word: NOM_CHAM).

The concept

result

is written field of size by field of size as described in

[§4.1].

Code_Aster

Version

8.2

Titrate:

Procedure

IMPR_RESU

format `

GMSH

Date:

22/02/06

Author (S):

COURTEOUS Mr., NR. TARDIEU

Key

U7.05.32-C1

Page:

4/6

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

Extraction of a field of size

5.1 Operands

TOUT_CHAM/NOM_CHAM

Cf document [U4.71.00].

5.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 [U4.71.00].

Selection of the topological entities and the components

In order to reduce the volume of the impressions, it is sometimes necessary to print only part of
result. With this intention one can wish not to print a field with the nodes or a field by element
that in certain elements.

This selection which one will note “selection on topological entities” is possible with the format

“GMSH”

One cannot print complex fields with format GMSH, it is thus necessary, for such fields,
to select the Real or Imaginary PART to print.

6.1 Operand

NET

This key word makes it possible to indicate the list of the meshs on which one wishes to print one

cham_elem

For one

cham_no

, it makes it possible to indicate the list of the nodes, nodes of the meshs to which one wishes

to print it

cham_no

6.2 Operand

GROUP_MA

This key word makes it possible to indicate the list of the groups of meshs on which one wishes to print one

cham_elem

. For one

cham_no

, it makes it possible to indicate the list of the nodes, nodes of the meshs to which

one wishes to print it

cham_no

6.3 Operand

NOM_CMP

This key word makes it possible to choose the list of the components which one wishes to print.
If this key word is not indicated, one prints the field with the tensor format (9 components per node).

Code_Aster

Version

8.2

Titrate:

Procedure

IMPR_RESU

format `

GMSH

Date:

22/02/06

Author (S):

COURTEOUS Mr., NR. TARDIEU

Key

U7.05.32-C1

Page:

5/6

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

7 Operand

UNIT

UNIT makes it possible to choose on which file the results will be written. By defect, UNIT = 37 with

format “GMSH”.

One can thus print results on different files with each control IMPR_RESU.

The natural suffix of the files of post processing GMSH is .pos and the usual logical unit (by

defect in astk) is 37.

8 Operand

VERSION

Meshs accepted by

GMSH

(in postprocessing) are, since the version 1.35, the meshs of the type

POI1

SEG2

TRIA3, QUAD4

TETRA4, HEXA8, PENTA6, PYRAM5

, which corresponds to:

VERSION = “1.2” which is the default value

If one requires to visualize the fields with an old version of GMSH or if one wishes
to cut out all the meshs in

POI1

SEG2

TRIA3

and

TETRA4

, one uses VERSION = “1.0”.

To be able to visualize the sights with

GMSH

, the mesh is modified to have only meshs

GMSH

Currently, meshs

PYRAM13

are not treated.

SEG3

is broken up into 2

SEG2

SEG4

is broken up into 3

SEG2

TRIA6

is broken up into 4

TRIA3

TRIA7

is broken up into 4

TRIA3

QUAD4

is broken up into 2

TRIA3

(cut out only if VERSION='1.0'),

QUAD8

is broken up into 6

TRIA3

QUAD9

is broken up into 6

TRIA3

TETRA10

is broken up into 8

TETRA4

PENTA6

is broken up into 3

TETRA4

(cut out only if VERSION='1.0'),

PENTA15

is broken up into 16

TETRA4

PYRAM5

is broken up into 2

TETRA4

(cut out only if VERSION='1.0'),

HEXA8

is broken up into 6

TETRA4

(cut out only if VERSION='1.0'),

HEXA20

is broken up of 24

TETRA4

HEXA27

is broken up into 48

TETRA4.

Notice

TRIA7 (respectively QUAD9) is cut out like the TRIA6 (resp. QUAD8) because the node

exchange does not carry a DDL of displacement in modeling COQUES_3D.