If PARAM,POST,0 is requested in SOL 144, a large number of new outputs become available. First, the aerodynamic mesh (for Doublet Lattice Slender Body geometries) is stored so that the unit solutions and trim solutions can be visualized in MSC.Patran using either the NASTRAN preference or FlightLoads. Without MSC.FLD, you must import both the model and the results. Using MSC.FLD, you will typically have the model already available in MSC.Patran. When the XDB is attached to PATRAN for both model and results data, the aerodynamic model will be imported and placed in a GROUP named “Aero Model CONFIG=<aeconfig>” where <aeconfig> is the AECONFIG name assigned in Case Control. The structural model is imported as before, except it will be placed in the group entitled “Aeroelastic Structural Model.”

In the Results module of MSC.Patran, the trim subcase data and unit solution data are available to be visualized on both the structural mesh and the aerodynamic mesh. These data consist of both displacements and several force components. The data are divided into TRIM results (subcases labelled SC<subcase index>) and “Flexible Increments (labelled FI <condition and parameter identifier>)” that represent the unit solution results. Each of these “Result Cases” (in the PATRAN parlance) is further divided into several “Results Types” that are the rigid, elastic, inertial, and total loads and the displacements. For Flexible Increments, both restrained and unrestrained data are available. For TRIM subcases, only restrained data are used to create the linear combination that is the TRIM result.

The Result Case labels are formed using the following rules:

All the data results are available on both meshes except for the inertial loads and the static applied loads, which are defined only on the structural mesh. Since these forces arise on the structural mesh, and the spline relationships don’t allow us to move forces from the structure to the aerodynamic nodes, these data are not defined over the aerodynamic model. Note, however, that the elastic increment aeroelastic forces associated with the deformations caused by the inertial forces are defined on both meshes. These data are part of the “elastic” component of the forces.

Table C‑1 shows the Result Types for the Trim Cases and Table C‑2 shows the Results Types for the Flexible Increments Cases. Note that, for Doublet Lattice models, the results are defined at the centroidal “grid” points, which, for display purposes in MSC.Patran become “elemental” results defined at the center of each aerodynamic box. Hence, the labels further hint that the results are defined on the aerodynamic mesh by labelling the results as “elemental” or “nodal.” In fact, “nodal” aerodynamic results are supported, but cannot be generated by DLM.