Operator LIRE

Code_Aster

Version

8.2

Titrate:

Operator

LIRE_RESU

Date:

31/01/06

Author (S):

J. PELLET, F. LEBOUVIER

Key

U7.02.01-F1

Page:

1/14

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

Organization (S):

EDF-R & D/AMA, Delta CAD

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

Operator

LIRE_RESU

1 Goal

To see fields and to store them in a structure of data of the result type

The type of the format of the file read is: either universal format IDEAS, or format ENSIGHT, or it
format MED.

Product a structure of data of the type result (evol_noli, evol_ther,…).

Code_Aster

Version

8.2

Titrate:

Operator

LIRE_RESU

Date:

31/01/06

Author (S):

J. PELLET, F. LEBOUVIER

Key

U7.02.01-F1

Page:

2/14

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

2 Syntax

general

resu = LIRE_RESU

(

# Choice of the format of the file to reading:

/FORMAT

= “IDEAS”

NOM_CHAM

l_nomch

[l_Kn]

UNIT =

iunit,

[I]

19,

[DEFECT]

FORMAT_IDEAS = _F (…

# to see [§ 3.2.2])

/FORMAT

= “IDEAS_DS58”

NOM_CHAM

l_nomch

[l_Kn]

REDEFI_ORIENT = (_F (

CODE_DIR =

/1,

/2,
/3,

DIRECTION = (dx, Dy, dz), [l_R]

NODE =

l_no,

[l_noeud]

),),

FORMAT

“ENSIGHT”

NOM_CHAM

l_nomch

[l_Kn]

NOM_FICHIER

file,

[KN]

FORMAT

“MED”

UNIT =

iunit,

[I]

81,

[DEFECT]

FORMAT_MED =

(_F (

NOM_CHAM =

nomch,

[KN]

NOM_CHAM_MED

= nommed

[KN]

NOM_CMP =

lcmp,

[l_Kn]

NOM_CMP_MED

lcmpmed,

[l_Kn]

NOM_MAIL_MED = nomamed,

[KN]

),),

Is # Which structure of data necessary to create? :

TYPE_RESU =

/“EVOL_ELAS”,

“EVOL_CHAR”

“EVOL_THER”

“EVOL_NOLI”

“DYNA_TRANS”

“DYNA_HARMO”

“HARM_GENE”

“MODE_MECA”

TYPE_RESU=

“EVOL_NOLI”

NB_VARI=

nbvar,

[I]

TYPE_RESU=

“MODE_MECA”

MATR_A= matr_rigi

[matr_asse_DEPL_R]

MATR_B= matr_mass

[matr_asse_DEPL_R]

# different information:

MESH

[mesh]

MODEL

[model]

Code_Aster

Version

8.2

Titrate:

Operator

LIRE_RESU

Date:

31/01/06

Author (S):

J. PELLET, F. LEBOUVIER

Key

U7.02.01-F1

Page:

3/14

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

# choice of the sequence numbers to reading:

TOUT_ORDRE =

“YES”

, [DEFECT]

NUME_ORDRE =

lordr

[l_I]

LIST_ORDRE =

lordr

[listis]

INST =

linst

[l_R]

LIST_INST

linst

[listr8]

FREQ =

lfreq

[l_R]

LIST_FREQ

lfreq

[listr8]

PRECISION

prec,

[R]

1.D-03

[DEFECT]

CRITERION =

“RELATIVE”

[DEFECT]

“ABSOLUTE”

TITRATE

l_titer,

[l_Kn]

)

Code_Aster

Version

8.2

Titrate:

Operator

LIRE_RESU

Date:

31/01/06

Author (S):

J. PELLET, F. LEBOUVIER

Key

U7.02.01-F1

Page:

4/14

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

3 Operands

3.1 Operands

FORMAT

UNIT

NOM_FICHIER

/FORMAT = “IDEAS”

“IDEAS_DS58”

Reading of the file to format IDEAS.

UNIT

Logical number of unit of the file to universal format IDEAS, by defect 19.

/FORMAT = “MED”

Reading of the file to format MED.

UNIT

Logical number of unit of the file to format MED, by defect 81.

/FORMAT = “ENSIGHT”

Reading of files to the Ensight format, relates to the reading of fields of pressure to the nodes
and is associated

TYPE_RESU = “EVOL_CHAR”

and with

NOM_CHAM = “CLOSE”

NOM_FICHIER

File name (in small letters and between quotes) Ensight of the type “Measured Results” (see
Ensight To use Manual pages 3-49, 3-50) containing in particular:

the name of the file “Measured Geometry” containing of the numbers of followed nodes
their co-ordinates,

the name of (or of) the file (S) “Variable Scalar” containing the values of
pressure with the nodes specified in the file “Measured Geometry”.

Note:

The logical number of unit can be associated a file using the control

DEFI_FICHIER

[U4.12.03].

3.2 Operands

FORMAT = “IDEAS”

The datasets 58 are not read (but only the datasets 55,57 and 2414)

3.2.1 Word

key

FORMAT_IDEAS

3.2.1.1 Objective

The fields with reading in the universal file are written in the form of datasets. Each dataset is
composed of a heading “indentity card” and of a whole of values (results to the nodes or by
element with the nodes). This indentity card is made up of several recordings “record”,
composed of fields “field”. The objective of this key word is to make it possible the user to define its
clean “indentity card” by specifying its own search keys.

Note:

A certain number of “indentity cards” are defined by defect [§6]. They can

“to overload” by using key word FORMAT_IDEAS.

3.2.1.2 Syntax

FORMAT_IDEAS

= (_F (

NOM_CHAM =

nomch, [kN]

NUME_DATASET

=/55,

/57,
/2414,

| RECORD_3 = r3,

[l_I]

RECORD_6

r6,

[l_I]

RECORD_9

r9,

[l_I]

Code_Aster

Version

8.2

Titrate:

Operator

LIRE_RESU

Date:

31/01/06

Author (S):

J. PELLET, F. LEBOUVIER

Key

U7.02.01-F1

Page:

5/14

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

POSI_ORDRE = Po,

[l_I]

/POSI_INST

= pi,

[l_I]

POSI_FREQ

PF,

[l_I]

NOM_CMP =

lcmp,

[l_Kn]

),),

3.2.1.3 Operands

NOM_CHAM = nomch

Reference symbol of the field for which the user defines the search keys. See the key word

NOM_CHAM

out of the key words factors [§3.5.1].

NUME_DATASET

Number of the dataset from which will be extracted the results:

: values with the nodes,

: values with the nodes by element

2414: values

RECORD_3

RECORD_6

RECORD_9

Each one of these key words is composed of the word RECORD and a number. The number indicates it

number of the recording for which one will define the search keys. Each operand
allows to define to the maximum 10 whole values.

Ex:

RECORD_6 = (1, 4, 9999, 8, 2, 6),

In this example, if the dataset read contains on the level of the recording n°6 the values (1 4
9999 8 2 6), it will be retained for the continuation of search. Value 9999 is an allowing joker
to be unaware of the value read in the dataset.

/POSI_ORDRE

Vector of two entireties allowing to locate the sequence number

V (1): N° of the recording
V (2): Position of the sequence number

/POSI_INST

Vector of two entireties allowing to locate the moment

V (1): N° of the recording
V (2): Position of the moment

/POSI_FREQ

Vector of two entireties allowing to locate the frequency

V (1): N° of the recording
V (2): Position of the frequency

NOM_CMP

Name of the components to reading.

Ex: NOM_CMP = (“DX”, “DY”, “DZ”, “XXX”, “DRX”, “XXX”, “DRZ”,),

The character string “XXX” is a joker making it possible to be unaware of the component during the reading

values.

Code_Aster

Version

8.2

Titrate:

Operator

LIRE_RESU

Date:

31/01/06

Author (S):

J. PELLET, F. LEBOUVIER

Key

U7.02.01-F1

Page:

6/14

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

If the number of CMPS to reading is higher than the number of CMPS present in the file .unv,

those are ignored.

Important remark:

When one is read

cham_elem

, the aforementioned is dimensioned in accordance with the finite elements

model (see key word

MODEL

below). For example, if one reads a field of

forced on a model 2D, the components carried by the elements will be

SIXX

SIYY

SIXY

and

SIZZ

. If in file IDEAS, one finds the CMPS:

SIXX

SIZZ

SIXZ

CMPS

SIXZ

will be ignored. On the other hand, all CMPS not found in

file (

SIYY

and

SIXY

in our example) will be put at zero.

3.3 Operands

FORMAT = “IDEAS_DS58”

Only the datasets 58 are read.
One reads only the fields corresponding to:
NOM_CHAM= “DEPL”, “QUICKLY”, “ACCE”, “SIEF_NOEU”, “EPSI_NOEU_DEPL”.

3.3.1 Word

key

REDEFI_ORIENT

This key word factor makes it possible to possibly redefine the significant direction of the sensor in some
points of measurement. This redefinition is treated currently only for

NOM_CHAM

“DEPL”

“QUICKLY”

and

“ACCE”

. One redefines as many orientations as necessary. If this key word misses, one

adopt the usual convention recalled in the following table:

Code

direction

“DEPL”, “QUICKLY”, “ACCE”

“SIEF_NOEU”

“EPSI_NOEU_DEPL”

DX SIXX

EPXX

DY SIYY

EPYY

DZ SIZZ

EPZZ

SIXY

EPXY

SIXZ

EPXZ

SIYZ

EPYZ

3.3.1.1 Operands

CODE_DIR =/1,

/2,
/3,

Code describing the direction of measurement, given in the heading of the dataset 58

DIRECTION = (dx, Dy, dz),

Directing vector, expressed in the total reference mark, indicating the significant direction to associate

CODE_DIR

NODE = l_no,

List nodes where CODE_DIR must be associated the directing vector DIRECTION.

3.4 Operands

FORMAT = “MED”

3.4.1 Operand

NOM_CHAM

NOM_CHAM

= nomch,

Reference symbol of the field to reading. One can read the fields with the nodes a priori, the fields by
elements with the nodes (

ELNO

) or constant (

ELEM

). See the key word

NOM_CHAM

out of the key words

factors [§3.5.1]

Code_Aster

Version

8.2

Titrate:

Operator

LIRE_RESU

Date:

31/01/06

Author (S):

J. PELLET, F. LEBOUVIER

Key

U7.02.01-F1

Page:

7/14

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

3.4.2 Operand

NOM_CHAM_MED

NOM_CHAM_MED

= nommed,

Name according to convention MED of the field to reading in the file. It is a channel of 32 characters.

3.4.3 Operands

NOM_CMP, NOM_CMP_MED

NOM_CMP = lcmp,

NOM_CMP_MED

lcmpmed,

These two lists must be of the same length. One reads in file MED the components
listed in lcmpmed, then one affects them in the components within the meaning of Code_Aster, of

even row in the list lcmp.

The names of components MED are limited to 16 characters.

If these 2 lists miss, it is supposed that the names of the CMPS are the same ones for
MED and for Aster.

3.4.4 Operand

NOM_MAIL_MED

NOM_MAIL_MED = nomamed,

If this operand misses, one seeks the field related to the first mesh in the file. It is it
who does when the file contains one mesh.

If the file contains several mesh, one specifies here which is associated the field that one wants
to see.

3.5 Others

operands

3.5.1 Operands

TYPE_RESU

NOM_CHAM

TYPE_RESU

Type of the structure of data

result

created.

NOM_CHAM = l_nomch

This key word is obligatory for all the formats safe for format MED where it is prohibited.

Reference symbol of the fields to reading. It is under this (or these names) that the fields will be
stored in the structure of data

result

A priori, for format “IDEAS”, one can read the fields with the nodes (NOEU) or constant by

element (ELEM) or by nodes with elements (ELNO). For a type of structure of data
result, the list of the possible fields is given in the documents of the booklet [U5].

For format “ENSIGHT”, one can read only the fields of pressure (“NEAR”) of the SD of the type
evol_char.

For format “IDEAS_DS58”, one does not treat for the moment the fields with the following nodes:

displacement, speed, acceleration, stress and deformation.

3.5.2 Operand

NB_VARI

NB_VARI = nbvar,

A number of variables intern with reading for the fields of internal variables (VARI_R).

Code_Aster

Version

8.2

Titrate:

Operator

LIRE_RESU

Date:

31/01/06

Author (S):

J. PELLET, F. LEBOUVIER

Key

U7.02.01-F1

Page:

8/14

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

3.5.3 Operands

MATR_A and MATR_B

MATR_A= matr_rigi,

MATR_B= matr_mass,

When one reads again a concept of the mode_meca type and that one wants to be useful oneself of this mode_meca

in certain operators (for example PROJ_MATR_BASE), it is necessary that:

· the mode_meca produces reference the 2 matr_asse (rigidity and mass) which was used for

to calculate,

· the fields of the mode_meca are numbered same manner as the unknown factors of

these 2 matr_asse.

So that this coherent classification is established in LIRE_RESU, these 2 key words should be used

optional MATR_A and MATR_B (see for example the test sdnv102a).

Caution:

This possibility is available only to format “IDEAS”.

3.5.4 Operands

MESH

MODEL

MESH =

my,

Mesh on which one affects the fields read.

MODEL

= Mo,

Name of the model where are defined the types of finite elements affected on the mesh. If one wants
to see a cham_elem, it is necessary to give the name of the model.

3.5.5 Operands

TOUT_ORDRE

NUME_ORDRE

/LIST_ORDRE/

INST

LIST_INST

FREQ

LIST_FREQ

PRECISION

CRITERION

Selection in a structure of data

result

[U4.71.00].

3.5.6 Reading

MODE_MECA

One can read clean modes stored with format IDEAS. But to be able to re-use them in

operators of dynamics (in particular DYNA_TRAN_MODAL), one needs the assembled matrices

(rigidity and mass) associated these modes. Key words MATR_A and MATR_B (pointing out those of
MODE_ITER_SIMULT) make it possible to inform these two matrices.

Behind MATR_A, one gives the name of the matrix of rigidity, behind MATR_B that of the matrix of

mass.

3.5.7 In connection with an alarm

It can happen that the values read on the file cannot be recopied in the fields of
Produced SD_RESULTAT. For example, a field of pressure existing on surface meshs,

can be recopied on a model containing only elements 3D. In this case, the code emits one
message of alarm resembling:

<A> <LIRE_RESU> <LRCEME>

NONAFFECTED VALUES IN THE FIELD: 3699

VALUES READ IN THE FILE: 3699

3.5.8 Operand

TITRATE

TITRATE

Titrate that one wants to give to the result [U4.03.01].

Code_Aster

Version

8.2

Titrate:

Operator

LIRE_RESU

Date:

31/01/06

Author (S):

J. PELLET, F. LEBOUVIER

Key

U7.02.01-F1

Page:

9/14

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

4 Examples

4.1

Example 1: reading of one

result

of type

“dyna_trans”

One reads on universal file IDEAS, the fields of displacement, speed and acceleration with

moments 1., 2., 3., 4. and 5.,

resu = LIRE_RESU

(FORMAT

= “IDEAS”

MODEL

Mo,

TYPE_RESU

“DYNA_TRANS”

NOM_CHAM

(

“DEPL”

“QUICKLY”

“ACCE”

,),

INST

= (1. , 2. , 3. , 4. , 5. ,),

)

4.2 Example 2: reading of one

result

of type

“evol_noli”

defining the search keys

One reads on universal file IDEAS, the internal fields of variables and deformations at the moment
15. by taking account of search keys user.

INIT =LIRE_RESU (MODEL

Mo,

FORMAT = “IDEAS”,

TYPE_RESU

“EVOL_NOLI”

NOM_CHAM

(“VARI_ELNO”, “EPSA_ELNO”),

NB_VARI =

INST =

15.,

FORMAT_IDEAS= (_F

(NOM_CHAM

= “VARI_ELNO”,

NUME_DATASET

57,

RECORD_6

(1,4,3,9999,2,6),

POSI_ORDRE =

(7,4,),

POSI_INST

NOM_CMP =

(“V1”, “V2”, “V3”, “V4”,)),

_F (NOM_CHAM

= “EPSA_ELNO”,

RECORD_6

(1,4,4,3,2,6),

NOM_CMP =

(“EPXX”, “XXX”, “EPZZ”,

“EPXY”, “EPXZ”, “EPYZ”))),

)

Code_Aster

Version

8.2

Titrate:

Operator

LIRE_RESU

Date:

31/01/06

Author (S):

J. PELLET, F. LEBOUVIER

Key

U7.02.01-F1

Page:

10/14

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

Files IDEAS with reading

- 1

57% VALUES WITH THE NODES OF THE ELEMENTS

ASTER 3.05.30 CONCEPT U CALCULATES IT - FIELD BY ELEMENT WITH THE NODES OF NAME

FIELD BY ELEMENT WITH THE NODES OF REFERENCE SYMBOL VARI_ELNO_ELGA - VARI_1 (ELNO)

ASTER 3.05.30 CONCEPT U CALCULATES THE 29/12/95 A 09:56:55 OF TYPE EVOL_NOLI

FIELD BY ELEMENT WITH THE NODES OF REFERENCE SYMBOL VARI_ELNO_ELGA

1 4 3 0 2 6

2 1 1 1

0.15000E+02

1 1 8.6% MESH MA2

2.07919E-05 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00

- 1

57% VALUES WITH THE NODES OF THE ELEMENTS

ASTER 3.05.30 CONCEPT U CALCULATES IT - FIELD BY ELEMENT WITH THE NODES OF NAME

FIELD BY ELEMENT WITH THE NODES OF NAME SYMB - EPXX EPXY EPYY EPXZ EPYZ EPZZ (ELNO)

ASTER 3.05.30 CONCEPT U CALCULATES THE 29/12/95 A 09:56:55 OF TYPE EVOL_NOLI

FIELD BY ELEMENT WITH THE NODES OF REFERENCE SYMBOL EPSA_ELNO

1 4 4 3 2 6

2 1 1 1

0.15000E+02

1 1 8.6% MESH MA2

0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00

- 1

Record 7

Record 6

Record 8

POSI_ORDRE (7,4)

POSI_INST (8,1)

4.3 Example 3: reading of a result of the type “evol_ther” in

defining the search keys

One reads on universal file IDEAS, the field of temperature for moment 0.8 by taking account of
search keys user.

TEMP

LIRE_RESU

(MESH = mall,

UNIT

19,

FORMAT = “IDEAS”,

TYPE_RESU

“EVOL_THER”

NOM_CHAM

“TEMP”,

INST =

0.8,

FORMAT_IDEAS

=_F (NOM_CHAM

“TEMP”

NUME_DATASET

2414,

RECORD_3

(1,),

RECORD_9

(2,4,1,5,2,1),

POSI_ORDRE =

(10,7),

POSI_INST

(12,1),

)

Code_Aster

Version

8.2

Titrate:

Operator

LIRE_RESU

Date:

31/01/06

Author (S):

J. PELLET, F. LEBOUVIER

Key

U7.02.01-F1

Page:

11/14

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

- 1
2414
36
B.C. 0, TIME = 0.8, TEMPERATURE_36
1
ASTER 5.01.00 CONCEPT TEMPLE CALCULATES - FIELD WITH THE NODES OF…
FIELD WITH THE NODES OF REFERENCE SYMBOL TEMP - TEMP
ASTER 5.01.00 CONCEPT TEMPLE CALCULATES THE 18/12/98 A 15:19:49 OF…
FIELD WITH THE NODES OF REFERENCE SYMBOL TEMP
SEQUENCE NUMBER: 35 INST: 8.00000E-01
2 4 1 5 2 1
- 11 0 1 0 1 0 35 0
1500 0
8.00000E-01 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.
0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.00000E+00 0.
1
2.00000E+02
-----------
205
1.00000E+02
- 1

Record 9

Record 3

Record 10

POSI_ORDRE (10,7)

POSI_INST (12,1)

Record 13

Record 12

Record 11

4.4 Example 4: reading of a result of the type “evol_char” to the format

“ENSIGHT”

One reads on file ENSIGHT all the fields of pressure

close = LIRE_RESU

(FORMAT

= “ENSIGHT”

NOM_FICHIER

“face6.result”

MODEL

Mo,

TYPE_RESU

“EVOL_CHAR”

NOM_CHAM

“CLOSE”

TOUT_ORDRE =

“YES”

)

Code_Aster

Version

8.2

Titrate:

Operator

LIRE_RESU

Date:

31/01/06

Author (S):

J. PELLET, F. LEBOUVIER

Key

U7.02.01-F1

Page:

12/14

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

Files ENSIGHT with reading

FILE face6.result

*******************************

.50000E-03 .10000E-02 .15000E-02

1 1

face6.geom

presface6.*** pressure

FILE face6.geom

****************************

File Ensight measured geometry file

particles coordinates

13 1.48000e+03-7.77010e+02

7.42010e+02

14 1.48000e+03-7.77010e+02

7.42010e+02

15 1.48000e+03-7.77010e+02

7.42010e+02

16 1.48000e+03-7.77010e+02

7.42010e+02

17 1.48000e+03-7.77010e+02

7.42010e+02

18 1.48000e+03-7.77010e+02

7.42010e+02

19 1.48000e+03-7.77010e+02

7.42010e+02

20 1.48000e+03-7.77010e+02

7.42010e+02

21 1.48000e+03-7.77010e+02

7.42010e+02

22 1.48000e+03-7.77010e+02

7.42010e+02

FILE presface6.***

*********************

presface6.001

.10000E+00

.10000E+00 .10000E+00 .10000E+00 .10000E+00

.10000E+00

.10000E+00 .10000E+00

.10000E+00

presface6.002

.10000E+01

.10000E+01 .10000E+01 .10000E+01 .10000E+01

.10000E+01

.10000E+01 .10000E+01

.10000E+01

presface6.003

.10000E+02

.10000E+02 .10000E+02 .10000E+02 .10000E+02

.10000E+02

.10000E+02 .10000E+02

.10000E+02

4.5

Example 5: reading of a evol_ther to format MED

LIRE_RESU (FORMAT = “MED”, MESH = MA,

UNIT = 21, TOUT_ORDRE = “YES”, TYPE_RESU = “EVOL_THER”,

FORMAT_MED

(

NOM_CHAM

TEMP,

NOM_CHAM_MED

“THERDEP_TEMP”,

)

Code_Aster

Version

8.2

Titrate:

Operator

LIRE_RESU

Date:

31/01/06

Author (S):

J. PELLET, F. LEBOUVIER

Key

U7.02.01-F1

Page:

13/14

Instruction manual

U7.0- booklet: Data exchanges

HT-62/06/004/A

Appendix 1: FORMAT_IDEAS: default values

In this paragraph, we present for each field (NOM_CHAM) the search keys per defect

used to locate in the universal file the results to read.

CHAM_NO

NOM_CHAM

“DEPL” “QUICKLY” “ACCE” “TEMP”

NUME_DATASET

55 55 55 55

RECORD_3

RECORD_6

1 4 3 8 2 6

1 4 3 11 2 6 1 4 3 12 2 6

2 4 1 5 2 1

RECORD_9

POSI_ORDRE

7 4

POSI_INST

8 1

POSI_FREQ

NOM_CMP

“DX” “DY”

“DZ” “DRX”

“DRY” “DRZ”

“DX” “DY”

“DZ” “DRX”

“DRY” “DRZ”

“DX” “DY”

“DZ” “DRX”

“DRY” “DRZ”

“TEMP” “TEMP_INF”

TEMP_SUP'

CHAM_ELEM

NOM_CHAM

“VARI_ELNO” “EPSA_ELNO”

“SIEF_ELNO” “CLOSE”

NUME_DATASET

57 57

RECORD_3

RECORD_6

1 4 3 0 2 6

1 4 4 3 2 6

1 4 4 2 2 6 1 4 1 15 2 1

RECORD_9

POSI_ORDRE

7 4

POSI_INST

8 1

POSI_FREQ

NOM_CMP

“V1” “V2”
“V3” “V4”
“V5” “V6”
“V7” “V8”

… …

“V9” “V30”

“EPXX”

“EPXY”
“EPYY”

“EPXZ”
“EPYZ”

“EPZZ”

“SIXX”

“SIXY”
“SIYY”

“SIXZ”
“SIYZ”

“SIZZ”

“CLOSE”