4. Operands#

4.1. Keyword DEFI_SUPER_MAILLE#

♦ DEFI_SUPER_MAILLE =

This keyword factor makes it possible to define the supermeshes of the mesh using macro-elements.

4.1.1. Operand MACR_ELEM#

♦ MACR_ELEM = l_se

l_se is the list of the names of the macro-elements that will generate the meshes.

4.1.2. Operand SUPER_MAILLE#

◊ SUPER_MAILLE = l_mail

l_mail is the list of names you want to give to knitwear. This argument is optional. In its absence, we will give the cells the names of the macro-elements (this is obviously impossible if we want to use the same macro-element several times).

4.1.3. Geometric transformation operands#

◊ | ◊ TRAN=

This keyword defines the translation to be applied to the macroelement:

if we are in**2D*, we expect 2 reals: (tx, ty),

if we are in**3D*, we expect 3 real ones: (tx, ty, tz).

| ◊ ENGLISH_NAUT=

These key words define the rotation to be applied to the macroelement.

If we are in 2D, we expect 3 real numbers:

  • a is the angle (in degrees) of rotation in the plane for ANGL_NAUT,

  • px and py are the coordinates of the center of rotation for CENTRE.

If we are in 3D, we expect 6 real ones:

  • a, b, c are the \((\alpha ,\beta ,\gamma )\) nautical angles of the rotation (in degrees). (cf. operator AFFE_CARA_ELEM [U4.42.01]) for ANGL_NAUT,

  • px, py, and pz are the coordinates of the center of rotation for CENTRE.

Important note:

We know that the order of the keywords is not significant for Aster. The translation/rotation operation is **conventionally done in the order rotation* **then translation. In general, these two operations do not switch.*

4.2. Keyword RECO_GLOBAL#

◊ | RECO_GLOBAL=

♦/TOUT = “OUI”, /SUPER_MAILLE = l_mesh, ◊ | CRITERION =/”ABSOLUTE”, /”RELATIF”, [DEFAUT] | PRECISION =/prec, /1.D-3, [DEFAUT]

This keyword makes it possible to automately re-glue a set of supermeshes (designated by the keyword SUPER_MAILLE or the keyword TOUT) with a criterion of geometric proximity: 2 nodes of 2 different supermeshes m1 and m2 will be combined if the distance that separates them is:

< prec*min (d (m1), d (m2)) (CRITERE = “RELATIF”).

where d (mi) notes the smallest distance between 2 knots of the supermesh mi.

Notes:

Two knots of the same stitch will never be glued back together.

If a mesh contains only one node, use the CRITERE =” ABSOLU “ .

4.3. Keyword RECO_SUPER_MAILLE#

◊ RECO_SUPER_MAILLE =

This factor keyword makes it possible to put together « by hand » certain super-stitches designated by the user. The supermeshes that can be glued back together are those that were defined by the keyword DEFI_SUPER_MAILLE. The supermeshes are then glued back together via groups of nodes. To say what you want to put back together, you must therefore give pairs (mesh, group of nodes (from the initial mesh)).

Notes:

When we give a pair (mesh, group of nodes), we designate the list of nodes in the group of nodes that are external to the macro element that defines the supermesh. It is in fact the intersection of the group of nodes and the edge of the substructure. This list is ordered like the initial group of nodes.

In principle, when 2 stitches are glued together via 2 groups of nodes, all the designated nodes must be glued together (cf. the convention chosen by the keyword OPTION). An alarm message will be sent if this is not the case.

4.3.1. Operands SUPER_MAILLE/GROUP_NO#

◊ SUPER_MAILLE =

One gives here the list of stitches to be glued back together. In general, the stitches are glued 2 by 2.

For the « corners », it can be pleasant to glue together all the competing meshes at once (for example the 4 super-cubes that share the same edge).

◊ GROUP_NO =

One gives here the list of node groups to be glued back together. This list is the same length as the mesh list.

4.3.2. Operand OPTION#

◊ OPTION =

This word allows you to choose the convention for grouping the lists of nodes defined by the groups of nodes.

  • “GEOMETRIQUE”:

The program will confuse the nodes by considerations of geometric proximity. (cf. keyword: RECO_GLOBAL)

  • “NOEUD_A_NOEUD”/”INVERSE”:

_images/Object_1.svg _images/Object_2.svg _images/Object_3.svg

Attention:

For option “ INVERSE “, only the first group of nodes in the list of GROUP_NOest « returned » .

4.4. Keyword DEFI_GROUP_NO#

◊ DEFI_GROUP_NO =

This factor keyword makes it possible to define groups of nodes based on groups existing in the initial meshes of the macro-elements.

Note:

An initial group of nodes may contain nodes that do not belong to the edges of the macro elements. These internal nodes therefore do not exist in the final mesh. For convenience, we take the convention of creating the reduced group anyway at its intersection with the edge of the macroelement.

4.4.1. Operands TOUT/SUPER_MAILLE/PREFIXE/INDEX#

/SUPER_MAILLE = email, ◊ PREFIXE = pref, ♦ INDEX = (dm, fm, dn, fn),

These keywords make it possible to create all the groups of nodes corresponding to the groups of the initial mesh associated with the email mesh or to all the cells if:

TOUT = “OUI”.

The renaming convention is as follows (in nickname FORTRAN):

gno_end (k8) = pref//no_mail (dm:fm) //gno_ini (dn:fn)

This means that the name of a group of nodes will be formed by concatenating:

  • the prefix possibly given by the user,

  • a character substring extracted from the name of the mesh,

  • a substring extracted from the name of the group_no of the initial mesh.

It is therefore necessary that:

ltot= length (prefix) + (fm-dm+1) + (fn-dn+1) 8

A common case is the following: the meshes that gave rise to macro-elements come from a pre-processor that generates names in the form GRNOijkl. If the user gives his supermeshes names with 2 characters: SA, SB,…, the sequence:

DEFI_GROUP_NO =_F (TOUT = 'OUI', PREFIXE ='GN', INDEX =( 1,2,5,8))

Will generate groups of name nodes:

GNSA0001, GNSA0002,..., GNSB0001.

4.4.2. Operands GROUP_NO_FIN/SUPER_MAILLE/GROUP_NO_INIT#

♦ SUPER_MAILLE = email, ♦ GROUP_NO_INIT = gno_ini,

These keywords allow you to create groups of nodes one by one:

  • gno_fin is the name we want to give to GROUP_NO,

  • mail and gno_ini identify the initial GROUP_NO:

  • mail is the name of the supermesh that has the GROUP_NO on it,

  • gno_ini is the name of the GROUP_NO of the initial mesh.