Download D3PLOT 12.0 user manual

User manual Version 12.0, October 2014
D3PLOT
double or double array GetUbinData(handle, item_type, item, int_pnt, (state_id))
Retrieves data for <type/item> in the UBIN component <handle>.
If the data has not previously been written (a) value(s) of 0.0 will be returned.
Arguments: <handle>
Integer A UBIN component handle as
This must be a handle of an existing
returned by CreateUbinComponent() UBIN component.
<item_type>Constant A constant of the standard type codes It is illegal to attempt to store data for
NODE, SOLID, SHELL, etc.
a type that does not match the
underlying UBIN component type
This must match the underlying type thus, for example, you cannot store
of the UBIN component, thus NODE NODE data for a U_SOSH
for components of type U_NODE, and component.
so on.
<item>
Integer If +ve: The internal item number
Internal item numbers will be many
starting from 1
times faster to process
If -ve: The external label of the item
<int_pnt> Integer Integration point: must be a +ve layer "Top", "Middle" and "Bottom" are
number (lowest = 1)
not allowed in this context since
"middle" is not directly readable in
Or zero for item type / data
cases with an even number of points.
component combinations that do not
consider integration points in this
A value of 1 should normally be used
context. (For example nodal
for solid elements
displacements or beam forces.)
Note from v11.0 onwards the order
of the integration points for SHELLS
and TSHELLS is <int_pnt> 1->n:
BOTTOM->TOP surface (so long as
a ZTF file is present) see Section
12.8.2.2.
<state_id> Integer Optional: State number
Return
value:
<data>
double
Results are returned as:
or
"Data type" Data type returned
double
array
U_SCALAR
Scalar double
U_VECTOR
Double array[3]
U_TENSOR
Double array[6]
Prior to this they were in the order of
the integration points output by
LS-DYNA, e.g. for <maxint>=3
<int_pnt> 1 was the MIDDLE
surface, <int_pnt> 2 was the
BOTTOM surface and <int_pnt> 3
was the TOP surface.
The state to be used instead of the
current state.
Examples:
dvec = GetUbinData(handle_1,
SOLID, 27, 1);
sxx = dvec[0];
szx = dvec[5];
Retrieve an array of tensor data for solid #27, which implies that the
UBIN data component <handle_1> is of type U_SOSH, and that its
data type is U_SCALAR.
nval = GetUbinData(handle_2,
NODE, 17, 0, istate);
Retrieve the scalar value of node #17, in state <istate>.
This implies that the UBIN component <handle_2> is of type
U_NODE and its data is U_SCALAR.
Page A.61