background image
Code_Aster
®
Version
4
Titrate:
Utilities of management of the CARDS
Date:
28/01/1999
Author (S):
J. PELLET
Key:
D6.10.01
Page:
1/6
Mechanical department and Digital Models
Index:
With
Dissemination:
Users - Developers
EDF
Direction of the Studies and Search
Electricity of France
Project Codes of Mechanics
Copyright EDF/DER 1997
Data-processing manual of Description
D6.10 booklet:
D6.10.01 document
Utilities of management of the CARDS
1
Introduction
cards
are fields [D4.06.05] “constant by element”. Formally a card is one
structure of data which puts in correspondence meshs and occurrences of same
size (for example
MATER
for the characteristics of material).
cards
are often used to store the data affected by the user on “areas”
of its mesh (controls
AFFE_CHAR_MECA
,
AFFE_MATERIAU
,
AFFE_CARA_ELEM
,…).
These fields can then be used like “inputs” of elementary calculations [D3.02.01].
Four routines are at the disposal of the programmers to build
CARDS
:
MECACT
:
to create a constant card.
ALCART
:
“to allocate” a card.
NOCART
:
to write a couple (size, zone_affectée) in a card.
TECART
:
“to finish” a card (optional operation).
background image
Code_Aster
®
Version
4
Titrate:
Utilities of management of the CARDS
Date:
28/01/1999
Author (S):
J. PELLET
Key:
D6.10.01
Page:
2/6
Data-processing manual of Description
D6.10 booklet:
Index A
2
To create a constant CARD: routine
MECACT
CAL MECACT (card, mocle, nommoa, nomgd, ncmp, licmp, ICMP, rcmp, K8cmp)
CARD
K19
in
jxout
name of the card to be created.
MOCLE
K6
in
/
“NETTED”
:
one affects all the meshs of
MESH
specified
in
NOMMOA (1:8)
/
“MODEL”
:
one affects all the late meshs of
LIGREL
specified in
NOMMOA (1:19)
NOMMOA
K *
in
name of
MESH
(or of
LIGREL
) on which the card rests.
NOMGD
I
in
name of the size associated with the card.
NCMP
I
in
numbers
CMPS
affected size
LICMP
L_K8
in
list names of
CMP
affected size.
ICMP
L_I
in
list values of
CMPS
affected size if the aforementioned is of
“whole” type
RCMP
L_R
in
list values of
CMPS
affected size if the aforementioned is of
“real” type
K8CMP
L_K8
in
list values of
CMPS
affected size if the aforementioned is of
type “K8”
Example:
licmp (1) = “DX”
licmp (2) = “DY”
rcmp (1)
= 1.0
rcmp (2)
= 2.0
CAL MECACT (“ma_carte”, “netted”, NETTED, “depl_r”, 2, licmp, ibid, rcmp, '')
will cause to create a constant card of the size
“DEPL_R”
for which, all them
meshs of the mesh will be affected by the values: (
DX = 1.0, DY = 2.0)
.
3
To create a CARD by “areas”
3.1
Principle of creation by areas
A card is an ordered list of couples (size, zone_affectée). When for example, one
user written in his command file:
AFFE_CHAR_MECA (….
PRES_REP:(
ALL: “YES”
NEAR: 0. )
PRES_REP:(
GROUP_MA: (GM1, GM3)
NEAR: 2. )
PRES_REP:(
NET: (M7, M8)
NEAR: 7. )
PRES_REP:(
NET: (M9)
NEAR: 9. )
The card of the size '
PRES_R'
contains 5 zone_affectée and the sizes which are attached there.
It will be said that the card was created “by area”. In the “large” made program:
CAL ALCART
allowance of the card
CAL NOCART
ALL:“YES”
NEAR:0.
“writing” of the 1ère zone_affectée in
CARD
CAL NOCART
GROUP_MA: GM1
NEAR: 2.
“writing” of 2nd zone_affectée in
CARD
CAL NOCART
GROUP_MA: GM3
NEAR: 2.
“writing” of 3rd zone_affectée in
CARD
background image
Code_Aster
®
Version
4
Titrate:
Utilities of management of the CARDS
Date:
28/01/1999
Author (S):
J. PELLET
Key:
D6.10.01
Page:
3/6
Data-processing manual of Description
D6.10 booklet:
Index A
CAL NOCART
NET:(M7, M8)
NEAR: 7.
“writing” of 4th zone_affectée in
CARD
CAL NOCART
NET:(M9)
NEAR: 7.
“writing” of 5th zone_affectée in
CARD
3.2
To allocate a CARD: routine
ALCART
Cal ALCART (card, netted, nomgd, nasmax, nmamax)
CARD
K19
in
jxout
name of the card to be created.
NETTED
K8
in
jxin
name of the mesh on which the card is based.
NOMGD
K8
in
name of the size associated with the card.
NASMAX
I
in
raising number of zone_affectée of the card.
NMAMAX
I
in
raising total number of meshs forming the lists of meshs of
zone_affectée
For the example of [§3.1] one will make:
Cal ALCART (“ma_carte”, “mailla_1”, “depl_r”, 5, 3)
3.3
To write in a CARD: routine
NOCART
Cal NOCART (Card, code, group, mode, nma, limano, limanu, nomlig, ncmp)
CARD
K19
in
jxvar
name of the card where one wants “to write”
CODE
I
in
code zone_affectée:
+1:
the whole of the meshs of the mesh (
ALL: “YES”
)
- 1:
the whole of the late meshs of one
LIGREL
+2:
one
GROUP_MA
mesh
+3:
a list of meshs of the mesh
- 3:
a list of late meshs of one
LIGREL
GROUP
K8
in
used only if Code = 2
it is the name of a group of meshs of the mesh.
MODE
K3
in
used only if code = ± 3.
mode =
“NUM”
if one is useful oneself of numbered meshs:
LIMANU
mode =
“NAME”
if one is useful oneself of named meshs:
LIMANO
NMA
I
in
used only if code = ± 3.
it is the number of meshs in the list
LIMANU
(or
LIMANO
)
LIMANO
L_K8
in
used only if code = + 3
it is the list of the names of the meshs of the mesh which are affected by
size.
LIMANU
L_I
in
used only if code = ± 3
it is the list of the numbers of the meshs which one affects.
NOMLIG
K19
in
used only if code = - 1 or = ­ 3.
it is the name of
LIGREL
where are defined the LATE meshs.
NCMP
I
in
it is the number of
CMP
that one wants to note in the card.
Information not transmitted by arguments.
The description of the size which one wants to note in the card makes via 2
objects of work which are allocated by
ALCART
:
background image
Code_Aster
®
Version
4
Titrate:
Utilities of management of the CARDS
Date:
28/01/1999
Author (S):
J. PELLET
Key:
D6.10.01
Page:
4/6
Data-processing manual of Description
D6.10 booklet:
Index A
CARD (1:19)//“.NCMP”
V (K8)
CARD (1:19)//“.VALV”
V (?)
(? = I, R, C, K8.)
·
in
CARD (1:19)//
'.
NCMP'
, the programmer writes the name of the components of
size which he wants to note.
·
in
CARD (1:19)//
'.
VALV'
, the programmer writes the values of the components
(in the same order as.
NCMP
).
3.4
Processing of the example of [§3.1]
CAL ALCART (CARD, netted, “PRES_r”, 5, 4)
CAL JEVEUO (CARD (1:19)//“.NCMP”, “E”, IANCMP)
ZK8 (IANCMP) = ' PRES'
CAL JEVEUO (CARD (1:19)//“.VALV”, “E”, IAVALV)
ZR (IAVALV) =0.
CAL NOCART (CARD, 1, ““,””, 0, ““, IBID,””, 1)
ZR (IAVALV) =2.
CAL NOCART (CARD, 2, “GM1”, ““, 0,””, IBID, '', 1)
ZR (IAVALV) =2.
CAL NOCART (CARD, 2, “GM3”, ““, 0,””, IBID, '', 1)
ZR (IAVALV) =7.
LIMANO (1) = ' M7'
LIMANO (2) = ' M8'
CAL NOCART (CARD, 3, ““, “NAME”, 2, LIMANO, IBID,””, 1)
ZR (IAVALV) =9.
LIMANO (1) = ' M9'
CAL NOCART (CARD, 3, ““, “NAME”, 1, LIMANO, IBID,””, 1)
3.5
Principle of overload
The principle of overload is applied for a CARD: in the list of the affected areas, one
element of the list overloads the elements which precedes it in the list. That wants to say that if one
mesh belongs to several zone_affectée different, the size which is associated is for him that
associated the zone_affectée last which contains this mesh.
If in the preceding example, the mesh
M8
belongs to the 2
GROUP_MA
GM1
and
GM3
, the pressure which him
is associated is
7.
Important remark:
The overload is total for all them
CMPS
size.
If one makes for example (card of
“DEPL_R”
):
GM1 - >
DX: 1.
DY: 2.
GM3 - >
DX: 3.
DZ: 4.
Meshs of
GM3
are affected by the size:
(
DX: 3. DZ: 4.)
Meshs of
GM1
(except those of
GM3
) are affected by the size
:
(
DX: 1. DY: 2.)
One can want that the principle of overload is more “fine” and that meshs of the intersection
of
GM1
and
GM3
“profit” from the 2 assignments and that their associated size is:
DX: 3. DY: 2. DZ: 4.
This is possible thanks to the routine
TECART
[§3.6]
background image
Code_Aster
®
Version
4
Titrate:
Utilities of management of the CARDS
Date:
28/01/1999
Author (S):
J. PELLET
Key:
D6.10.01
Page:
5/6
Data-processing manual of Description
D6.10 booklet:
Index A
3.6
Overload “fine”: routine
TECART
CAL TECART (card)
CARD
K19
in
jxvar
name of the card “to be finished”
This routine is has to call after the last call to
NOCART
.
This operation modifies the contents of the card to take account of the rule of “fine” overload
defined in the preceding paragraph.
Practically, one “extends” the card on all the meshs, one determines on each one of them the size
who is associated to him by a “fine” overload of the type:
M1: DX
=
1.
DY
=
2.0
+
M1: DX
=
3.0
DZ
=
4.0
M1: DX
=
3.0
DY
=
2.0
DZ
=
4.0
command of the calls
with
NOCART
In the second time, one recompacte the card, by gathering the meshs which are affected by
even size.
background image
Code_Aster
®
Version
4
Titrate:
Utilities of management of the CARDS
Date:
28/01/1999
Author (S):
J. PELLET
Key:
D6.10.01
Page:
6/6
Data-processing manual of Description
D6.10 booklet:
Index A
Intentionally white left page.