ProductsAbaqus/StandardAbaqus/ExplicitAbaqus/CAE TypeModel data
LevelThis option is not supported in a model defined in terms of an assembly of part instances. Abaqus/CAEUnsupported; meshing techniques in the
Mesh module
are usually preferable.
Required parameters
 NSET

Set this parameter equal to the name of the node set containing the nodes to
be mapped. The nodes that are mapped are those that belong to this set at the
time this option is encountered.
 TYPE

Set TYPE=ROTATION to introduce a rotation of a specified angle about a given
axis defined by two points a and b
(or by the coordinates of these points). The origin of rotation is given by a
third point c (or by the coordinates of this point).
Set TYPE=TRANSLATION to introduce a translation along a given axis defined by two
nodes a and b (or by the coordinates
of these points).
Set TYPE=SCALE to scale each axis with respect to one node
a (or by the coordinates of this point).
Set TYPE=RECTANGULAR to introduce a simple shift or rotation. Point
a in
Figure 1
defines the origin of the local rectangular coordinate system defining the map.
The local $\widehat{x}$axis
is defined by the line joining points a and
b. The local $\widehat{x}$–$\widehat{y}$
plane is defined by the plane passing through points a,
b, and c.
Set TYPE=CYLINDRICAL to map from cylindrical coordinates. Point
a in
Figure 1
defines the origin of the local cylindrical coordinate system defining the map.
The line going through point a and point
b defines the $\widehat{z}$axis
of the local cylindrical coordinate system. The local $\widehat{r}$–$\widehat{z}$
plane for $\theta =0$
is defined by the plane passing through points a,
b, and c.
Set TYPE=DIAMOND to map from skewed Cartesian coordinates. Point
a in
Figure 1
defines the origin of the local diamond coordinate system defining the map. The
line going through point a and point
b defines the $\widehat{x}$axis
of the local coordinate system. The line going through point
a and point c defines the
$\widehat{y}$axis
of the local coordinate system. The line going through point
a and point d defines the
$\widehat{z}$axis
of the local coordinate system.
Set TYPE=SPHERICAL to map from spherical coordinates. Point
a in
Figure 1
defines the origin of the local spherical coordinate system defining the map.
The line going through point a and point
b defines the polar axis of the local spherical coordinate
system. The plane passing through point a and
perpendicular to the polar axis defines the $\varphi =0$
plane. The plane passing through points a,
b, and c defines the local
$\theta =0$
plane.
Set TYPE=TOROIDAL to map from toroidal coordinates. Point a
in
Figure 1
defines the origin of the local toroidal coordinate system defining the map.
The axis of the local toroidal system lies in the plane defined by points
a, b, and c. The
Rcoordinate of the toroidal system is defined by the
distance between points a and b. The
line between points a and b defines
the $\varphi =0$
position. For every value of $\varphi $
the $\theta $coordinate
is defined in a plane perpendicular to the plane defined by the points
a, b, and c and
perpendicular to the axis of the toroidal system. $\theta =0$
lies in the plane defined by the points by a,
b, and c.
Set TYPE=BLENDED to map via blended quadratics in an
Abaqus/Standard
analysis.
Optional parameters
 DEFINITION

Set DEFINITION =COORDINATES (default) to define the local system, the axis of rotation,
the origin of rotation, or the axis of translation by giving the coordinates of
the points a, b,
c, and d whichever appropriate for
the chosen type.
Set DEFINITION=NODES to define the local system, the axis of rotation, the origin
of rotation, or the axis of translation by giving global node numbers for
points a, b, c,
and d depending on the type. This option cannot be used
with TYPE=BLENDED.
Data lines for TYPE=ROTATION, DEFINITION=COORDINATES First
line

Xcoordinate of point a.

Ycoordinate of point a.

Zcoordinate of point a.

Xcoordinate of point b.

Ycoordinate of point b.

Zcoordinate of point b.
 Second line

Xcoordinate of point c.

Ycoordinate of point c.

Zcoordinate of point c.
 Third line

The rotation angle in degrees.
Data lines for TYPE=ROTATION, DEFINITION=NODES First
line

Local node number of point a.

Local node number of point b.
 Second line

Local node number of point c.
 Third line

The rotation angle in degrees.
Data lines for TYPE=TRANSLATION, DEFINITION=COORDINATES First
line

Xcoordinate of point a.

Ycoordinate of point a.

Zcoordinate of point a.

Xcoordinate of point b.

Ycoordinate of point b.

Zcoordinate of point b.
 Second line

The translation magnitude.
Data lines for TYPE=TRANSLATION, DEFINITION=NODES First
line

Local node number of point a.

Local node number of point b.
 Second line

The translation magnitude.
Data lines for TYPE=SCALE, DEFINITION=COORDINATES First
line

Xcoordinate of point a.

Ycoordinate of point a.

Zcoordinate of point a.
 Second line

Scale factor to be applied to the first local coordinate.

Scale factor to be applied to the second local coordinate.

Scale factor to be applied to the third local coordinate.
Data lines for TYPE=SCALE, DEFINITION=NODES First
line

Local node number of point a.
 Second line

Scale factor to be applied to the first local coordinate before mapping.

Scale factor to be applied to the second local coordinate before mapping.

Scale factor to be applied to the third local coordinate before mapping.
Data lines for TYPE=RECTANGULAR, CYLINDRICAL, DIAMOND, SPHERICAL, or TOROIDAL with DEFINITION=COORDINATES First
line

Xcoordinate of point a (see
Figure 1).

Ycoordinate of point a.

Zcoordinate of point a.

Xcoordinate of point b.

Ycoordinate of point b.

Zcoordinate of point b.
 Second line

Xcoordinate of point c.

Ycoordinate of point c.

Zcoordinate of point c.
 The following fields are needed only for TYPE=DIAMOND:

Xcoordinate of point d.

Ycoordinate of point d.

Zcoordinate of point d.
If TYPE=RECTANGULAR is specified and only point a is given,
the coordinates of the nodes in the set are simply shifted by
${X}_{a}$,
${Y}_{a}$,
and ${Z}_{a}$.
 Third
line

Scale factor to be applied to the first local coordinate before mapping. If
the value entered is zero or blank, a scale factor of 1.0 is assumed.

Scale factor to be applied to the second local coordinate before mapping. If
the value entered is zero or blank, a scale factor of 1.0 is assumed.

Scale factor to be applied to the third local coordinate before mapping. If
the value entered is zero or blank, a scale factor of 1.0 is assumed.
Data lines for TYPE=RECTANGULAR, CYLINDRICAL, DIAMOND, SPHERICAL, or TOROIDAL with DEFINITION=NODES First
line

Local node number of point a.

Local node number of point b.
 Second line

Local node number of point c.
 The following field is needed only for TYPE=DIAMOND:

Local node number of point d.
If TYPE=RECTANGULAR is specified and only point a is given,
the coordinates of the nodes in the set are simply shifted by
${X}_{a}$,
${Y}_{a}$,
and ${Z}_{a}$.
 Third
line

Scale factor to be applied to the first local coordinate before mapping. If
the value entered is zero or blank, a scale factor of 1.0 is assumed.

Scale factor to be applied to the second local coordinate before mapping. If
the value entered is zero or blank, a scale factor of 1.0 is assumed.

Scale factor to be applied to the third local coordinate before mapping. If
the value entered is zero or blank, a scale factor of 1.0 is assumed.
Data lines for TYPE=BLENDED First
line

Node number of the first control node.

Xcoordinate of the point to which this control node is
to be mapped.

Ycoordinate of the point to which this control node is
to be mapped.

Zcoordinate of the point to which this control node is
to be mapped.
 Second line

Node number of the second control node.

Xcoordinate of the point to which this control node is
to be mapped.

Ycoordinate of the point to which this control node is
to be mapped.

Zcoordinate of the point to which this control node is
to be mapped.
Continue, giving up to 20 control nodes, but giving at least
the eight corner nodes. If an edge of the blended mapping is to be mapped
linearly, the corresponding midedge control node can be omitted from the list.
This is done by inserting a line with node number 0 only (a blank line) in
place of the definition of the control node and its mapped coordinates. The
control nodes do not have to be nodes in the finite element model—they can be
nodes used just for mesh generation.
Abaqus
eliminates any nodes that are not used in the analysis model before doing the
analysis.
