III.1.2 Nastran Result characteristics

When a Result object is read from an “op2” or an “xdb” file, integer and/or real identifiers are associated with the object. These identifiers depend on the solution sequence to which the Results correspond:

• For SOL 101: IntId[0] corresponds to the sub-case identifier, and IntId[1] is the load set number.

• For SOL 103: IntId[0] corresponds to the sub-case identifier, and IntId[1] is the mode number. RealId[0] is the real eigenvalue. The corresponding eigen-frequency is given by $f=\sqrt{\text{RealId[0]}}∕2\pi$. (Note however that this eigen-frequency is left undefined for the Grid Point Forces.)

• For SOL 105: IntId[0] corresponds to the sub-case identifier, and IntId[1] is the mode number. RealId[0] is the real eigenvalue, corresponding to the critical load. (Note however that this critical load is left undefined for the Grid Point Forces.)

• For SOL 106 and SOL 400: IntId[0] corresponds to the sub-case identifier, and IntId[1] corresponds to the step index in the sub-case. RealId[0] is the value of the continuation parameter for which the Results have been saved in the Result file.

• For SOL 108 and SOL 111 Results, the IntId[0] corresponds to the frequency output integer ID, and RealId[0] corresponds to the frequency value. The same is true for the PSD and CRMS random analysis outputs, which are saved for each frequency output.

The “load case name” identifier associated with read or accessed results corresponds to the “SUBTITLE” associated with the SUBCASE defined in the Nastran data file. If this SUBTITLE is not defined, the SUBCASE ID is used to generate a default load case identifier as follows:

 lcName="Load Case "+ID

The subcase names are automatically generated by FeResPost when the Results are read from output files. Table III.1.5 lists possible subcase names generated by FeResPost when Nastran Results are read from OP2, XDB or HDF files. The integer and real values associated with the Results for each Nastran solution type are listed in Table III.1.4.

Finally, the results found in the op2 file are presented by blocks corresponding to the different “result element types”. Unfortunately, those element types do not correspond exactly to the element bdf cards presented in section III.1.1.1. The supported result element types are: “ROD”, “BEAM”, “TUBE”, “SHEAR”, “CONROD”, “ELAS1”, “ELAS2”, “ELAS3”, “ELAS4”, “DAMP1”, “DAMP2”, “DAMP3”, “DAMP4”, “VISC”, “MASS1”, “MASS2”, “MASS3”, “MASS4”, “CONM1”, “CONM2”, “PLOTEL”, “QUAD4”, “BAR”, “GAP”, “TETRA”, “BUSH1D”, “QUAD8”, “HEXA”, “PENTA”, “BEND”, “TRIAR”, “TRIA3”, “TRIA6”, “QUADR”, “TETRANL”, “GAPNL”, “TUBENL”, “TRIA3NL”, “RODNL”, “QUAD4NL”, “PENTANL”, “CONRODNL”, “HEXANL”, “BEAMNL”, “QUAD4LC”, “QUAD8LC”, “TRIA3LC”, “TRIA6LC”, “BUSH”, “FAST”, “QUAD144”, “QUADRNL”, “TRIARNL”, “ELAS1NL”, “ELAS3NL”, “BUSHNL”, “QUADRLC” and “TRIARLC”. (More information on the result element types can be found in [Rey04].)

Here again, some of the element result types can be disabled or enabled (section III.1.1.1). The arguments given to the enabling or disabling methods correspond to a String object, or an Array of Strings, the values of Strings corresponding to some of the Result element types given just above.

The negative node values corresponding to Results on specific Nastran elements are summarized in Table III.1.6. (This Table is a complement to Table I.4.2.) These keys can be used when Results are read from “OP2” or “XDB” files. Note that the “CbarGrdA” and “CbarGrdB” are used only to associate values to CBAR end nodes when the definition of CBAR element has not been found in the DataBase.