Code_Aster ®
Version
8.2
Titrate:
Procedure TEST_RESU
Date:
31/01/06
Author (S):
J. Key PELLET
:
U4.92.01-I1 Page
: 1/10
Organization (S): EDF-R & D/AMA
Handbook of Utilization
U4.9- booklet: Impression/Test
Document: U4.92.01
Procedure TEST_RESU
1 Goal
To compare a value extracted from a structure of data with a value of reference provided by
the user.
This command makes it possible to test a numerical value: entirety, reality or complex extracted from one
concept already calculated. Today, one can test a component of a cham_no_ * or one
cham_elem_ *, a component of a field extracts from a result, a parameter of a result,
a “total” value extracted from a field or contents from an unspecified object from a concept
user.
The procedure writes a conventional message then:
·
“OK” (if it is good),
·
“NOOK” (if not).
follow-up of the found value, the value of reference and percentage of error.
Commands TEST_FONCTION [U4.92.02] and TEST_TABLE [U4.92.03] make it possible to test them
values extracted from the functions and the tables.
Handbook of Utilization
U4.9- booklet: Impression/Test HT-62/06/004/A
Code_Aster ®
Version
8.2
Titrate:
Procedure TEST_RESU
Date:
31/01/06
Author (S):
J. Key PELLET
:
U4.92.01-I1 Page
: 2/10
2 Syntax
TEST_RESU (
UNITE
=
/
8
,
[DEFAUT]
/
iunit,
,
[I]
|
CHAM_NO= (_F (
CHAM_GD
=
chno,
[cham_no_ *]
/
TYPE_TEST =/“SOMM_ABS”,
/
“SOMM”
,
/
“MAX”
,
/
“MIN”
,
NOM_CMP
=
lcmp,
[l_K8]
//NOEUD =
No,
[node]
/
GROUP_NO
= grno,
[group_no]
NOM_CMP =
nomcmp,
[K8]
# See definition of the value of reference
),)
|
CHAM_ELEM= (_F
(
CHAM_GD
=
chel,
[cham_elem_ *]
/
TYPE_TEST =/“SOMM_ABS”,
/
“SOMM”
,
/
“MAX”
,
/
“MIN”
,
NOM_CMP
=
lcmp,
[l_K8]
/
MAILLE
=
my
,
[mesh]
/POINT = nupoint,
[I]
/
NOEUD
=
No
,
[node]
/
GROUP_NO
=
grno,
[group_no]
NOM_CMP = nomcmp,
[K8]
# See definition of the value of reference
),),
|
RESU = (_F (RESULT
= LMBO
,
[resultat_ *]
SENSIBILITE = (… to see [U4.50.02])
/
NUME_ORDRE
=
nuor,
[I]
/
NUME_MODE
=
numo,
[I]
/
INST
=
inst,
[R]
/
FREQ
=
freq,
[R]
/
NOEUD_CMP
=
(node,
cmp),
[l_Kn]
/
NOM_CAS
=
nocas,
[KN]
/
ANGL
=
,
[R]
/PARA = para, [K16]
/
NOM_CHAM
=
nosymb,
[K16]
/
TYPE_TEST =/“SOMM_ABS”,
/
“SOMM”
,
/
“MAX”
,
/
“MIN”
,
NOM_CMP =
lcmp,
[l_K8]
//NOEUD = No,
[node]
/
GROUP_NO
=
grno, [group_no]
/MAILLE = my,
[mesh]
/POINT = nupoint, [I]
/
NOEUD
=
No,
[node]
/
GROUP_NO
=
grno,
[group_no]
NOM_CMP = nomcmp,
[K8]
Handbook of Utilization
U4.9- booklet: Impression/Test HT-62/06/004/A
Code_Aster ®
Version
8.2
Titrate:
Procedure TEST_RESU
Date:
31/01/06
Author (S):
J. Key PELLET
:
U4.92.01-I1 Page
: 3/10
# See definition of the value of reference
),),
|
GENE = (_F (/RESU_GENE
= LMBO
,
[VECT_ASSE_GENE]
NUME_CMP_GENE
=
ncmp,
[I]
/RESU_GENE
= LMBO
,
[HARM_GENE]
[MODE_GENE]
/PARA = para, [K16]
/
NOM_CHAM
=
nosymb,
[K16]
NUME_CMP_GENE = ncmp,
[I]
/NUME_ORDRE = nuor,
[I]
/
NUME_MODE
=
numo, [I]
/
FREQ
=
freq,
[R]
/RESU_GENE
= LMBO
,
[TRAN_GENE]
NOM_CHAM
=
nosymb,
[K16]
NUME_CMP_GENE
=
ncmp,
[I]
/NUME_ORDRE = nuor,
[I]
/
INST
=
inst,
[R]
# See definition of the value of reference
),),
|
OBJET = (_F (
NOM
=
nomobj
,
[K24]
/
S_I
=
vali,
[I]
/
S_R
=
valr,
[R]
PRECISION
=
/
1.D-3
,
[DEFAUT]
/
prec,
[R]
CRITERION =/“RELATIVE”,
[DEFAUT]
/
“ABSOLU”
,
# See definition of the value of reference
),),
)
# Definition of the value of reference
REFERENCE =/“ANALYTICAL”,
/
“NON_REGRESSION”
,
VERSION = towards,
[KN]
/
“SOURCE_EXTERNE”
,
/
“AUTRE_ASTER”
,
/
VALE
=
valley
,
[R]
/
VALE_C
=
valley
,
[C]
/
VALE_I
=
valley
,
[I]
VALE_ABS
=/
“NON”
,
[DEFAUT]
/
“OUI”
,
/ | PRECISION
=
/
1.0D-3
,
[DEFAUT]
/
prec,
[R]
| CRITERE
=
/
“RELATIF”
,
[DEFAUT]
/
“ABSOLU”
,
/ |
PRECISION =/(prec1, prec2),
[l_R]
|
CRITERE =/(crit1, crit2),
[l_Kn]
Handbook of Utilization
U4.9- booklet: Impression/Test HT-62/06/004/A
Code_Aster ®
Version
8.2
Titrate:
Procedure TEST_RESU
Date:
31/01/06
Author (S):
J. Key PELLET
:
U4.92.01-I1 Page
: 4/10
Note:
The type of the concepts which one can test is not checked by the command. A priori, the key word
CHAM_NO makes it possible to test all the types of cham_no, in the same way for key words CHAM_ELEM
and RESU (for the concepts of the result type).
3 General information
This command makes it possible to test a scalar numerical value recovered in a concept of the type
cham_no *, cham_elem_ * or result, compared to a value of reference provided by
the user.
Three types of numerical values can be tested:
·
a component of a field (cham_no or cham_elem or field belonging to one
result),
·
a parameter contained in a concept of result (see booklet [U5.01]),
·
a total value of a field [§4.5].
To test a component of field, it is necessary to choose a field [§4.2] then to choose a component
[§4.3].
To test a parameter, it is necessary to choose a sequence number [§4.2.4] and to choose the name of the parameter.
The awaited numerical value (real, complex or whole) is provided in accordance with [§4.7].
Remarks concerning the tests in the structures of “generalized” data:
One can test the generalized components (displacements, speeds or accelerations of one
transient in modal space). It is advisable nevertheless to be circumspect with this type of test. In
effect the value of a generalized component depends entirely on the standard of the mode. However
this one is given in an arbitrary way. Thus without preliminary standardization of the standards,
value of a generalized size is arbitrary. Lastly, it there not of possibility in Code_Aster
to fix the direction of a mode. For a multiple mode, that wants to say that, even once them
normalized modes, a generalized size can take an unspecified value. In the case of one
simple mode, it can be directed in a direction or the opposite direction. One obtains then
a generalized value or its opposite.
Handbook of Utilization
U4.9- booklet: Impression/Test HT-62/06/004/A
Code_Aster ®
Version
8.2
Titrate:
Procedure TEST_RESU
Date:
31/01/06
Author (S):
J. Key PELLET
:
U4.92.01-I1 Page
: 5/10
4 Operands
4.1 Operand
UNITE
UNITE = iunit
Number of the logical unit of the file where the impression (by defect will be done: RESULTAT).
4.2
Selection of a field
In order to test a field which can be a simple field (cham_no or cham_elem), or a field
extracted from a result, or will use the key words factors: CHAM_NO, CHAM_ELEM or RESU.
4.2.1 “Simple” fields
CHAM_GD = field
Name of the cham_no or the cham_elem which one wants to extract a value.
4.2.2 Operand
RESULTAT
RESULTAT = LMBO
Name of the concept treated result.
4.2.3 Operand
SENSIBILITE
SENSIBILITE = par_sensi
Name of the significant parameter. See [U4.50.22] for the details
4.2.4 Operand
NOM_CHAM
/NOM_CHAM = nosymb
Reference symbol of the field to be selected (see booklet [U5.01]).
4.2.5 Selection
of a sequence number
/NUME_ORDRE = nuor,
Sequence number of the field (or the parameter) required.
/NUME_MODE = numo,
/INST = inst,
/FREQ = freq,
/NOEUD_CMP = (node, cmp),
/NOM_CAS = nocas,
/ANGL =,
These key words make it possible to identify a sequence number in a result [U4.71.00].
They are called “variables of access”.
They all are not valid for all the types of result.
For a type of result given, its variables of access are given in [U5]
documentation of use.
When the access is not made an actual value (ANGL, FREQ, INST) the value given does not have
not to be ambiguous (cf [§4.7]).
Handbook of Utilization
U4.9- booklet: Impression/Test HT-62/06/004/A
Code_Aster ®
Version
8.2
Titrate:
Procedure TEST_RESU
Date:
31/01/06
Author (S):
J. Key PELLET
:
U4.92.01-I1 Page
: 6/10
4.3
Selection of a parameter in a result
To select a parameter in a result (see booklet [U5.01]), the number should be specified
of a desired nature [§4.2.4] and to give the name of the parameter.
PARA = para
Name of the sought parameter. This name is attached to the type of the concept treated result.
4.4
Selection of a component of a field
The access to a size is done for a cham_no by:
·
the name of the node which carries this size.
The access to a size is done for a cham_elem by:
·
the name of the mesh which supports the element,
·
something which specifies:
-
that is to say the name of a node of this mesh for the cham_elem “with the nodes” (_ELNO_).
-
that is to say the number of the point of GAUSS for the cham_elem “at the points of GAUSS”
(_ELGA_).
MAILLE = my
Name of the mesh where one wants to test the cham_elem.
/NOEUD = No
Name of the node which one wants to check a component.
/GROUP_NO = grno
To facilitate the use of this command, one can replace key word NOEUD by
GROUP_NO.
In this case, it is necessary that the group is reduced to only one node.
/POINT = nupoint
The entirety nupoint specifies the number of the point of GAUSS which one wants to test the value (case
cham_elem “at the points of GAUSS”).
NOM_CMP = nomcmp
Name of the component which one wants to test [U2.01.04].
4.5
To test a field “overall”
Once a selected field [§4.2], one can test a quantity calculated overall on all it
field. One can restrict the field on certain components (key word NOM_CMP):
NOM_CMP
=
lcmp [l_K8]
If NOM_CMP is not indicated, the whole of the components will be taken. If not, one will not take
in account that components of lcmp.
/TYPE_TEST = “SOMM_ABS”
The sum of the absolute values of the components of the field.
/TYPE_TEST = “SOMM”
The sum of the values of the components of the field.
/TYPE_TEST = “MAX”
The maximum of the values of the components of the field.
/TYPE_TEST = “MIN”
Minimum of the values of the components of the field.
Handbook of Utilization
U4.9- booklet: Impression/Test HT-62/06/004/A
Code_Aster ®
Version
8.2
Titrate:
Procedure TEST_RESU
Date:
31/01/06
Author (S):
J. Key PELLET
:
U4.92.01-I1 Page
: 7/10
4.6
To test the contents of an object JEVEUX
This functionality is reserved for the developers of Code. To use it, the names should be known
objects JEVEUX composing the concepts of the user. It is intended to check not
regression of the structures of data other than the RESULTAT, CHAMPS, TABLE and FONCTION.
4.6.1 Operand
NOM
NOM = nomobj
Name of the jeveux object which one wants to test.
4.6.2 Operands
S_I/S_R
S_I = vali
For the objects of the whole type, summons values contained in the object.
S_R = valr
For the objects of the type real (or complex), nap of the values of the numbers contained in the object.
For the complex numbers, one makes the sum of the parts real and imaginary.
Note:
The objective of this type of test (NOM + S_I or S_R) is to test a whole vector overall.
“nap” which is tested is unfortunately a bad “check sum” of the object: one
permutation within the vector does not change this sum. A more careful test consists with
to print the object in a file (IMPR_CO) then to test the contents of this file with a truth
“check sum” (TEST_FICHIER).
4.6.3 Operands
CRITERE and PRECISON
See below [§4.7].
4.7
Definition of the value of reference
REFERENCE =
/“ANALYTIQUE”:
the provided value of reference is “analytical”
/“NON_REGRESSION”:
the provided value of reference was obtained at the time of a precedent
calculation by Code_Aster
VERSION =
towards
worms is the number of the version of Aster which made it possible to obtain
value of reference (ex: “5.3.4”)
/“SOURCE_EXTERNE”:
the provided value of reference comes from a different program
that Aster (or of a bibliographical reference)
/“AUTRE_ASTER”:
the provided value of reference is that obtained by another
path Aster (another command, option of calculation,…)
/VALE = valley
Actual value awaited for the component nomcmp, the parameter para or the nomobj object.
/VALE_C = valley
Complex value awaited for the component nomcmp or the parameter para.
/VALE_I = valley
Whole value awaited for the parameter para or the nomobj object.
Handbook of Utilization
U4.9- booklet: Impression/Test HT-62/06/004/A
Code_Aster ®
Version
8.2
Titrate:
Procedure TEST_RESU
Date:
31/01/06
Author (S):
J. Key PELLET
:
U4.92.01-I1 Page
: 8/10
VALE_ABS
=
= “NON”
the value of reference and the computed value by Aster are compared just as they are.
= “OUI”
the value of reference and the computed value by Aster are compared in values
absolute.
PRECISION
=
Precision requested (by defect 1.D3) to accept the computed value.
CRITERE
=
Type of test to be carried out.
If v are the extracted value, the test will carry for:
·
“RELATIF” on:
·
“ABSOLU” on:
.
Note:
When the definition of the sequence number of a RESULTAT is done by a real variable of access
(FREQ, INST, ANGL), it is not necessary that there is ambiguity on this sequence number. For that
the user defines a small interval around the value requested thanks to key words CRITERE
and PRECISION.
In this case (“real” access) key words CRITERE and PRECISION will thus await 2 values
each one: (crit1, crit2) and (prec1, prec2).
crit1 and prec1 relate to the value of reference.
crit2 and prec2 make it possible to choose the interval of search of the sequence number.
The default values of crit1 and prec1 are “RELATIF” and 1.D-3.
The default values of crit2 and prec2 are “RELATIF” and 1.D-3.
One cannot explicitly define crit2 and prec2 without defining crit1 and prec1.
Handbook of Utilization
U4.9- booklet: Impression/Test HT-62/06/004/A
Code_Aster ®
Version
8.2
Titrate:
Procedure TEST_RESU
Date:
31/01/06
Author (S):
J. Key PELLET
:
U4.92.01-I1 Page
: 9/10
5 Examples
TEST_RESU
(
CHAM_NO = _F (CHAM_GD = F,
NOEUD
=
“N2”,
NOM_CMP
=
“DX”
,
REFERENCE
=
“ANALYTIQUE”
,
VALE
=
1.2E-5
,
PRECISION
=
1D-4
,),
CHAM_ELEM= (_F
(CHAM_GD = SIGGA,
MAILLE
=
“M3”,
POINT
=
3,
NOM_CMP
=
“SIXX”
,
REFERENCE
=
“NON_REGRESSION”
VERSION='5.3.3'
,
VALE
=
3.4E6,
),
_F
(
CHAM_GD
=
SIGNO,
MAILLE
=
“M5”,
NOEUD
=
“N1”,
NOM_CMP
=
“SIXX”
,
VALE
=
3.4E6,
),),)
TEST_RESU
(
RESU
= (_F
(
RESULTAT
=
mo_meca,
NUME_ORDRE=
2,
PARA
=
“FREQ”
,
VALE
=
1.5782,
),
_F
(
RESULTAT
=
evolth,
SENSIBILITE
=
PS,
NOM_CHAM
=
“TEMP”
,
INST
=
12.0,
NOEUD
=
“N37”,
NOM_CMP
=
“TEMP_R”
,
VALE
=
0.0,
CRITERE
=
“ABSOLU”
,),
_F
(
RESULTAT
=
evolth,
NOM_CHAM
=
“FLUX_ELGA_TEMP”
,
TYPE_TEST
=
“MAX”
,
VALE
=
154.35,),
OBJET
= _F
(
NOM
=
“CH1 .CHME.LIGREL.LIEL”
,
IF
=
1278484
,),
)
Handbook of Utilization
U4.9- booklet: Impression/Test HT-62/06/004/A
Code_Aster ®
Version
8.2
Titrate:
Procedure TEST_RESU
Date:
31/01/06
Author (S):
J. Key PELLET
:
U4.92.01-I1 Page
: 10/10
Intentionally white left page.
Handbook of Utilization
U4.9- booklet: Impression/Test HT-62/06/004/A
Outline document