3.5. Reviewing the Results

Results from a modal analysis (that is, the modal expansion pass) are written to the structural results file, Jobname.RST. Results consist of:

You can review these results in POST1 (/POST1), the general postprocessor. Some typical postprocessing operations for a modal analysis are described below. For a complete description of all postprocessing functions, see An Overview of Postprocessing in the Basic Analysis Guide.

3.5.1. Points to Remember

  • If you want to review results in POST1, the database must contain the same model for which the solution was calculated.

  • The results file (Jobname.RST) must be available.

3.5.2. Reviewing Results Data

  1. Read in results data from the appropriate substep. Each mode is stored on the results file as a separate substep. If you expand six modes, for instance, your results file will have one load step consisting of six substeps.

    Command(s): SET, LSTEP, SBSTEP
    GUI: Main Menu> General Postproc> Read Results> By Load Step

    If the results data are complex, you can retrieve the real part, the imaginary part, the amplitude or the phase using KIMG in the SET command.

    SET, LSTEP, SBSTEP , , KIMG

  2. Perform any desired POST1 operations. Typical modal analysis POST1 operations are explained below:

3.5.3. Option: Listing All Frequencies

You may want to list the frequencies of all modes expanded. A sample output from this command is shown below.

  *****  INDEX OF DATA SETS ON RESULTS FILE  *****
   SET   TIME/FREQ    LOAD STEP   SUBSTEP  CUMULATIVE
     1  22.973             1         1         1
     2  40.476             1         2         2
     3  78.082             1         3         3
     4  188.34             1         4         4
Command(s): SET,LIST
GUI: Main Menu> General Postproc> List Results

3.5.4. Option: Display Deformed Shape

Command(s): PLDISP
GUI: Main Menu> General Postproc> Plot Results> Deformed Shape

Use the KUND field on PLDISP to overlay the nondeformed shape on the display.

3.5.5. Option: Line Element Results

Command(s): ETABLE
GUI: Main Menu> General Postproc> Element Table> Define Table

For line elements, such as beams, spars, and pipes, use the ETABLE command to access derived data (stresses, strains, and so on). Results data are identified by a combination of a label and a sequence number or component name on the ETABLE command. See the ETABLE discussion in The General Postprocessor (POST1) in the Basic Analysis Guide for details.

3.5.6. Option: Contour Displays

Command(s): PLNSOL or PLESOL
GUI: Main Menu> General Postproc> Plot Results> Contour Plot> Nodal Solu or Element Solu

Use these options to contour almost any result item, such as stresses (SX, SY, SZ...), strains (EPELX, EPELY, EPELZ...), and displacements (UX, UY, UZ...).

The KUND field on PLNSOL and PLESOL gives you the option of overlaying the nondeformed shape on the display.

You can also contour element table data and line element data:

Command(s): PLETAB, PLLS
GUI: Main Menu> General Postproc> Element Table> Plot Element Table
Main Menu> General Postproc> Plot Results> Contour Plot> Line Elem Res


Caution:  Derived data, such as stresses and strains, are averaged at the nodes by the PLNSOL command. This averaging results in "smeared" values at nodes where elements of different materials, different shell thicknesses, or other discontinuities meet. To avoid the smearing effect, use selecting (described in Selecting and Components in the Basic Analysis Guide) to select elements of the same material, same shell thickness, and so on before issuing PLNSOL.


3.5.7. Option: Tabular Listings

Command(s): PRNSOL (nodal results) PRESOL (element-by-element results) PRRSOL (reaction data), and so on NSORT, ESORT
GUI: Main Menu> General Postproc> List Results> solution option
Main Menu> General Postproc> List Results> Sorted Listing> Sort Nodes
Main Menu> General Postproc> List Results> Sorted Listing> Sort Elems

Use the NSORT and ESORT commands to sort the data before listing them.

3.5.8. Other Capabilities

Many other postprocessing functions - mapping results onto a path, load case combinations, and so on - are available in POST1. See The General Postprocessor (POST1) in the Basic Analysis Guide for details.


Release 18.2 - © ANSYS, Inc. All rights reserved.