General Results

III.1.2.1 General Results

The correspondence between the Nastran output requests and the DMAP data blocks written in the “op2” file is given in Tables III.1.7 to III.1.16. Note that in all the examples presented in Part IV, the results are printed in the “op2” file with “SORT1” option. This means that no test has been done with “SORT2” option.

Table III.1.7: Correspondence between the Nastran output cards and the “op2” result data blocks. (Displacements read from OUG data blocks.)


Nastran	“op2”	Generated
Statement	Data Block	Result


DISPL	OUG	“Displacements, Translational” “Displacements, Rotational” “Displacements, Scalar”

VELO	OUG	“Velocities, Translational” “Velocities, Rotational” “Velocities, Scalar”

ACCEL	OUG	“Accelerations, Translational” “Accelerations, Rotational” “Accelerations, Scalar”

Table III.1.8: Correspondence between the Nastran output cards and the “op2” result data blocks. (Applied loads read from OPG data blocks.)


Nastran	“op2”	Generated
Statement	Data Block	Result


OLOAD	OPG	“Applied Loads, Forces” (2, 8) “Applied Loads, Moments” (2, 8)

Table III.1.9: Correspondence between the Nastran output cards and the “op2” result data blocks. (MPC and SPC forces read from OQG data blocks.)


Nastran	“op2”	Generated
Statement	Data Block	Result


MPCFORCES	OPG	“MPC Forces, Forces” (2, 8) “MPC Forces, Moments” (2, 8) “MPC Forces, Scalar” (2, 8)

SPCFORCES	OPG	“SPC Forces, Forces” (2, 8) “SPC Forces, Moments” (2, 8) “SPC Forces, Scalar” (2, 8)

Table III.1.10: Correspondence between the Nastran output cards and the “op2” result data blocks. (Grid point forces read from OGF data blocks.)


Nastran	“op2”	Generated
Statement	Data Block	Result


GPFORCES	OGF	“Grid Point Forces, Internal Forces” “Grid Point Forces, Internal Moments” “Grid Point Forces, MPC Forces” (2) “Grid Point Forces, MPC Moments” (2) “Grid Point Forces, MPC Internal Forces” (9) “Grid Point Forces, MPC Internal Moments” (9) “Grid Point Forces, SPC Forces” (2) “Grid Point Forces, SPC Moments” (2) “Grid Point Forces, Applied Forces” (2) “Grid Point Forces, Applied Moments” (2) “Grid Point Forces, Contact Forces” (2, 3) “Grid Point Forces, Contact Moments” (2, 3) “Grid Point Forces, Friction Forces” (2, 3) “Grid Point Forces, Friction Moments” (2, 3) “Grid Point Forces, Global Damping Forces” (4, 5, 6) “Grid Point Forces, Global Damping Moments” (4, 5, 6) “Grid Point Forces, Viscous Damping Forces” (4, 5, 6) “Grid Point Forces, Viscous Damping Moments” (4, 5, 6)

Table III.1.11: Correspondence between the Nastran output cards and the “op2” result data blocks. (Strains read from OES data blocks and corresponding to “STRAIN” output requests.)


Nastran	“op2”	Generated
Statement	Data Block	Result


STRAIN	OES	“Strain Tensor” (10, 2) “Beam Axial Strain for Axial Loads” “Beam Axial Strain for Bending Loads” “Beam Axial Strain for Total Loads” (14) “Beam Shear Strain for Torsion Loads” “Beam Deformations” (20) “Beam Velocities” (20) “Beam Stations” (23) “Gap Forces” (21) “Gap Deformations” (21) “Gap Slips” (21) “Spring Scalar Strain” “Bush Forces Strain Tensor” (18 and 19) “Bush Moments Strain Tensor” (18 and 19) “Bush Plastic Strain” (18 and 19) “Curvature Tensor” (10, 13) “Shear Panel Strain, Max” “Shear Panel Strain, Average”

Table III.1.12: Correspondence between the Nastran output cards and the “op2” result data blocks. (Stresses read from OES data blocks and corresponding to “STRESS” output requests.)


Nastran	“op2”	Generated
Statement	Data Block	Result


STRESS	OES	“Stress Tensor” (1 in section III.1.2.2) “Beam Axial Stress for Axial Loads” “Beam Axial Stress for Bending Loads” “Beam Axial Stress for Total Loads” (14) “Beam Shear Stress for Torsion Loads” “Beam Forces” (18 and 19) “Beam Moments” (18 and 19) “Beam Deformations” (20) “Beam Velocities” (20) “Beam Stations” (23) “Gap Forces” (21) “Gap Deformations” (21) “Gap Slips” (21) “Spring Scalar Stress” “Bush Forces Stress Tensor” (18 and 19) “Bush Moments Stress Tensor” (18 and 19) “Bush Stress, Axial” (20) “Bush Strain, Axial” (20) “Bush Plastic Strain” (20) “Shear Panel Stress, Max” “Shear Panel Stress, Average”

Table III.1.13: Correspondence between the Nastran output cards and the “op2” result data blocks. (Nonlinear stresses read from OES data blocks and corresponding to “NLSTRESS” or other output requests (24).)


Nastran	“op2”	Generated
Statement	Data Block	Result


NLSTRESS	OES	“Nonlinear Stress Tensor” (11) “Nonlinear Strain Tensor” (11) “Nonlinear Effective Plastic Strain” (11) “Nonlinear Effective Creep Strain” (11) “Nonlinear Spring Scalar Strain” “Nonlinear Spring Scalar Stress” “Nonlinear Beam Axial Strain for Axial Loads” “Nonlinear Beam Axial Stress for Axial Loads” “Nonlinear Beam Axial Strain for Total Loads” “Nonlinear Beam Axial Stress for Total Loads” “Nonlinear Beam Forces” “Nonlinear Beam Moments” “Beam Stations” (23) “Nonlinear Bush Forces Stress Tensor” (18 and 19) “Nonlinear Bush Moments Stress Tensor” (18 and 19) “Nonlinear Bush Forces Strain Tensor” (18 and 19) “Nonlinear Bush Moments Strain Tensor” (18 and 19) “Nonlinear Gap Forces” (21) “Nonlinear Gap Deformations” (21) “Nonlinear Gap Slips” (21)

Table III.1.14: Correspondence between the Nastran output cards and the “op2” result data blocks. (Element forces read from OEF data blocks or other “FORCE” output.)


Nastran	“op2”	Generated
Statement	Data Block	Result


FORCE (1, 20)	OEF	“Shell Forces” “Shell Moments” (12) _______________________________________________ “Beam Forces” (15, 16,17) “Beam Moments” (15, 16,17) “Beam Warping Torque” “Beam Deformations” “Beam Velocities” “Beam Stations” (23) “Gap Forces” (21) “Gap Deformations” (21) “Gap Slips” (21) “Spring Scalar Forces” “Bush Plastic Strain”

Table III.1.15: Correspondence between the Nastran output cards and the “op2” result data blocks. (Element forces read from OEE data blocks or “ESE”, “EKE” and “EDE” output.)


Nastran	“op2”	Generated
Statement	Data Block	Result


ESE	OEE	“Element Strain Energy” “Element Strain Energy (Density)” “Element Strain Energy (Percent of Total)”

EKE	OEE	“Element Kinetic Energy” “Element Kinetic Energy (Density)” “Element Kinetic Energy (Percent of Total)”

EDE	OEE	“Element Energy Loss” “Element Energy Loss (Density)” “Element Energy Loss (Percent of Total)”

Table III.1.16: Nastran Results for thermal calculations.


Nastran	“op2”	Generated
Statement	Data Block	Result


TEMPERATURE	OUG	“Temperature”

FLUX	OEF	“Temperature Gradient”
FLUX	OEF	“Conductive Heat Flux”

One can make a few remarks about the information given in Tables III.1.7 to III.1.16:

1.

The Nastran “CELASi” and “CDAMPi” elements produce scalar forces or moments that are stored in “Beam Scalar Forces” Results.

2.

“Applied Loads” are available both with the “OLOAD” and “GPFORCE” Nastran statements. A similar remark applies to “MPC Forces” and “SPC Forces”.

3.

“Contact” and “Friction” grid point loads can be read from Nastran OP2 and HDF5 files, but not from XDB files because Nastran does not output these loads in XDB. (XDB output is deprecated.)

4.

“Damping” and “Inertia” grid point loads can be read from Nastran OP2 and HDF5 files, but not from XDB files because Nastran does not output these loads in XDB. (XDB output is deprecated.)

5.

“Damping” and “Inertia” grid point loads correspond to outputs for Nastran SOL108 or SOL111 and are normally produced in complex format only.

6.

The manipulation of complex Grid Point Forces Results is illustrated in example “RUBY/EX34/checkInertiaLoads.rb” in section IV.2.16.

7.

The “Grid Points Forces” on DMIG elements may correspond to several Results, as different Result names are attributed to the different DMIG elements. For example, the request to “Grid Point Forces, DIMG * Forces” may correspond to “Grid Point Forces, DIMG K11X Forces”, “Grid Point Forces, DIMG K22X Forces”,... Also, in requests the “*” can be replaced by the name of one DMIG element, then results associated to specified DMIG element are returned. The small examples in directory “RUBY/EX33” illustrate the capabilities. (See section IV.2.15.)

8.

When forces or moments corresponding to “Applied Loads”, “MPC Forces” or “SPC Forces” are read by FeResPost, key-value pairs are inserted only when at least one of the components is not zero. This has been done to avoid the creation of Result objects filled with a lot of zero values.

9.

When the option “RIGID=LAGR” is activated, the contributions of rigid body elements and MPCs are included in “Grid Point Forces, MPC Forces” and “Grid Point Forces, MPC Moments” and not in “Grid Point Forces, Internal Forces” and “Grid Point Forces, Internal Moments”:

For the Results “Grid Point Forces, MPC Forces” and “Grid Point Forces, MPC Moments” The ElemId of each key is set to “NONE”. (These Results are pure nodal Results.)
For the “Grid Point Forces, Internal Forces” and “Grid Point Forces, Internal Moments” Results, the ElementId associated with each vector corresponds to the MPC ID of the RBE element. This means that care must be taken when extracting these Results on Groups of MPCs.

10.

The shear components of strain tensor output by Nastran are the angular deformations: $γ_{i j} = 2 ϵ_{i j}$ . When these results are imported in a NastranDb, the corresponding components are divided by two in such a way that a “physical” tensor is stored into the NastranDb. The same remark applies for the non-diagonal components of the curvature tensor (shell elements).

The “STRAIN” Nastran output statement with “FIBER” option outputs the strain tensor at Z1 and Z2, but does not produce the curvature tensor.

11.

The Nonlinear stresses and strains are available for CHEXA, CPENTA, CTETRA, CQUAD4 and CTRIA3 elements. Plastic deformation results are produced for non-linear results only.

12.

When shell bending moments are imported from Nastran finite element results, the sign of each component is changed. This has been done to ensure that a positive component of the bending moment results in a positive value of the corresponding stress tensor component on the upper face of the shell. In other words, a positive bending corresponds to tension stress in shell upper face. (See equation II.1.31 for the definition of bending moments tensor components.)

13.

When Nastran shell curvature Results are imported, two modifications are brought to the components:

The signs of all the components are changed,
The shear components of the tensor are divided by two.

This is done because FeResPost considers that positive curvature components corresponds to positive strain components in upper face of the shell, and negative components in lower face of the shell. (See equation II.1.32 for the definition of curvature tensor components.)

14.

“Axial Strain” or “Axial Stress” for “Total Loads” and CBAR elements are produced by combined axial loads to bending loads. This has been done to harmonize CBAR Results with CBEAM Results. For CBEAM Results, Stresses or Strains are recovered on the extremities only.

15.

Nastran “BEAM” type elements (CBAR, CBEAM, CBEND,...) do not output vectorial or tensorial forces or moments. Instead, the different components are expressed in different coordinate systems (axial, plane 1 and plane 2). When importing these Results, a conversion into tensorial format is done as follows:

F = (\begin{matrix} F_{x x} & F_{x y} & F_{x z} \\ F_{x y} & 0 & 0 \\ F_{x z} & 0 & 0 \end{matrix}) = (\begin{matrix} F_{a x i a l} & V_{1} & V_{2} \\ V_{1} & 0 & 0 \\ V_{2} & 0 & 0 \end{matrix}),

M = (\begin{matrix} M_{x x} & M_{x y} & M_{x z} \\ M_{x y} & 0 & 0 \\ M_{x z} & 0 & 0 \end{matrix}) = (\begin{matrix} M_{t o r s i o n} & - M_{2} & M_{1} \\ - M_{2} & 0 & 0 \\ M_{1} & 0 & 0 \end{matrix}) .

16.

Nastran CBUSH elements produce forces and moments corresponding to the loads applied by Grid B of the element to Grid A. By analogy with the what is done for “BEAM” type of elements, “Beam Forces” and “Beam Moments” are produced, filled as follows:

F = (\begin{matrix} F_{x x} & F_{x y} & F_{x z} \\ F_{x y} & 0 & 0 \\ F_{x z} & 0 & 0 \end{matrix}) = (\begin{matrix} F_{x} & F_{y} & F_{z} \\ F_{y} & 0 & 0 \\ F_{z} & 0 & 0 \end{matrix}),

M = (\begin{matrix} M_{x x} & M_{x y} & M_{x z} \\ M_{x y} & 0 & 0 \\ M_{x z} & 0 & 0 \end{matrix}) = (\begin{matrix} M_{x} & M_{y} & M_{z} \\ M_{y} & 0 & 0 \\ M_{z} & 0 & 0 \end{matrix}) .

The choice of considering bush forces and moments as beams is questionable; it is justified as follows:

When grids A and B are not coincident, the definition of CBUSH element axes can be done the same way as for CBEAM elements (Figure III.1.1.a). The $e_{x}$ vector points from grid A to grid B, and $X$ component of force vector is positive when the CBUSH element is in tension. Then, the analogy between CBUSH element and CBEAM elements is perfect, and the tensorial character of CBUSH element forces and moments is obvious.
It is no longer true when the CBUSH orientation is specified with a coordinate system as represented in Figure III.1.1.a. In such a case, $X$ component of force vector no longer can be interpreted as a tension in CBUSH element. It is only the force applied by grid B to grid A, and projected on CBUSH coordinate system $X$ axis.

CBUSH elements are often used in the modeling of connections. Whatever the type of coordinate system definition, it is always possible to obtain vectorial forces and moments by a contracted multiplication of the vectorial result with a unit vector:

f = (\begin{matrix} F_{x x} & F_{x y} & F_{x z} \\ F_{x y} & 0 & 0 \\ F_{x z} & 0 & 0 \end{matrix}) \cdot (\begin{matrix} 1 \\ 0 \\ 0 \end{matrix}) = (\begin{matrix} F_{x x} \\ F_{x y} \\ F_{x z} \end{matrix}),

m = (\begin{matrix} M_{x x} & M_{x y} & M_{x z} \\ M_{x y} & 0 & 0 \\ M_{x z} & 0 & 0 \end{matrix}) \cdot (\begin{matrix} 1 \\ 0 \\ 0 \end{matrix}) = (\begin{matrix} M_{x x} \\ M_{x y} \\ M_{x z} \end{matrix}) .

This is generally the first operation performed when CBUSH loads are used for the sizing of connections. This also works when connection forces are extracted from CBEAM or CBAR elements.

(a)

(b)

Figure III.1.1: CBUSH element axes definition. (Pictures extracted from [Sof04b].)

17.

For CBAR elements, “Beam Forces” are always produced at the center of elements, and “Beam Moments” at the two end nodes. For CBEAM elements, “Beam Forces” and “Beam Moments” can be requested at different stations long the element. A minimum is then the production of outputs at the two ends of the element; Therefore, “Beam Forces” are output at element end nodes, as a minimum. But generally, no “Beam Forces” are output at element centers.

18.

Bush result types for OEF and OES outputs depend on the kind of BUSH elements to which they correspond:

Nastran “CBUSH” elements for linear analyses produce vectorial or tensorial results in OEF and OES blocks.
Nastran “CBUSH” elements for non-linear analyses produce vectorial or tensorial results in OES blocks. No results are produced in OEF blocks.

The element forces and moments are stored in “Beam Forces” and “Beam Moments” tensorial Results.

19.

The result types generated for CFAST elements are the same as for CBUSH elements.

Note that FeResPost cannot determine the CFAST element coordinate system when grids A and B are coincident. This may cause problems when transformation of reference coordinate systems are required. (This is the case when gmsh outputs of results are requested.) Note also that Patran also seems to experience some difficulties to calculate CFAST element axes.

20.

Nastran “CBUSH1D” elements produce scalar results in OEF and OES blocks. By this we mean that each type of result has only one single component. However, the scalar force is stored in “Beam Forces” tensorial result. Most components of the tensor are zero:

F = (\begin{matrix} F_{x x} & 0 & 0 \\ 0 & 0 & 0 \\ 0 & 0 & 0 \end{matrix}) .

No bending moments are produced by “CBUSH1D” elements.

21.

Nastran “CGAP” elements produces various results. These Results are read from OES or OEF data blocks. These Results are tensorial and:

Gap forces results are stored in “Gap Forces” tensorial Result. The value of the axial component is multiplied by “-1.0”, because it is a compression component.
Gap deformations are stored in “Gap Deformations” tensorial Result. Here again the value of the axial component is multiplied by “-1.0”.
“Gap Slips” is identical to “Gap Deformations” except that the axial component is set to “0.0”.

22.

Various Nastran elements refer scalar points instead of grids. Nevertheless, Nastran considers the scalar point as a kind of element rather than as a kind of grid. This is, in the authors’ opinion, an unfortunate choice. FeResPost considers SPOINT and EPOINT objects as a peculiar type of GRID. This has implications for the definition of keys when importing Results with from Nastran op2 files. It is hoped that this will not lead to problems.

23.

The “Beam Stations” scalar result is produced when stresses, strains or forces are read for CBEAM or CBAR elements:

This Result corresponds to the location of beam load recovery along the 1D element and varies between 0 and 1. It is scalar and has always a real format.
Intermediate stations, differing from 0 or 1, are produced by CBEAM elements, or CBAR elements if associated with a CBARAO card.
Up to 40 intermediate stations are supported by FeResPost. Beyond this value, Beam results are not read. This limit should be sufficient as Nastran Manuals recommend that no more than 6 intermediate stations are defined by CBARAO bulk card, and as CBEAM element allow up to 9 intermediate stations.
The node IDs to which intermediate station values are associated correspond to the “CbeamSt01” to “CbeamSt40” IDs defined in Table III.1.6.

24.

“Nonlinear” outputs may result from various output requests as “NLSTRESS”, “STRESS”, “STRAIN”, “FORCE”... The “Nonlinear” character of Results is more related to the type of Nastran solution than to the output request. For example, Nastran SOL 106 or SOL 400 analyses are likely to produce “Nonlinear” outputs.

[next] [front] [up]