Command Default

Writes the specified solution item for every substep. Exceptions to the default behavior are as follows:

Notes

OUTRES controls following output parameters:

The command generates a specification for controlling data storage for each substep, activating storage of the specified solution item for the specified substeps of the solution and suppressing storage of that item for all other substeps.

You can issue OUTRES multiple times in an analysis. After the initial command creating the storage specification, subsequent OUTRES commands modify the specification set for each substep. The command processes your specifications at each substep in the order in which you input them. If you specify a given solution item twice, output is based upon the last specification. Therefore, issue multiple OUTRES commands carefully and in the proper sequence.

In addition to OUTRES, these commands also control solution output: OUTPR, OUTGEOM, and OSRESULT.

You can issue up to 50 output-control commands for OUTRES, OUTPR, OUTGEOM in an analysis. There is no limit on the number of OSRESULT commands.

OUTRES,ERASE erases the existing output specifications and resets the counted number of OUTRES commands to zero. The ERASE argument works in a similar manner for OUTPR, OUTGEOM, and OSRESULT.

A given OUTRES command generally has no effect on solution items not specified. For example, an OUTRES,ESOL,LAST command does not affect NSOL data; that is, it neither activates nor suppresses NSOL data storage in any substep. An exception to this behavior involves the EANGL solution item.

OUTRES controls element Euler angle (EANGL) data output as follows:

Additional results in the Jobname.dsub file (DSUBres = ALL) can only be requested in the first load step.

To suppress all data at every substep, issue the OUTRES,ALL,NONE command. (OUTRES,ERASE does not suppress all data at every substep.)

The NSOL, RSOL, V, and A solution items are associated with nodes. The CINT solution item is associated with fracture. All remaining solution items are associated with elements.

Enabling nodal-averaged results (Item = NAR or any of the associated labels) generally reduces the results file size, provided the equivalent element-based results are concurrently disabled. When nodal-averaged results are enabled, element values for stress and strain are averaged and stored as nodal values. Some limitations apply when using nodal averaged results. For more information and an example, see Nodal-Averaged Results in the Element Reference.

The boundary conditions (constraints and force loads) are written to the results file only if either nodal or reaction loads (NLOAD or RSOL items) are also written.

For additive manufacturing analyses during the build step (AMSTEP,BUILD), Freq refers to the layer number (for example, output ALL layers, LAST layer, or every N^th layer).

If the minimum time step value is small (DELTIM,,DTMIN) while Freq contains a large value, then the time steps will not be written to the .rst file due to the resulting calculation of these set of values.

To specify selected results to output to the database, see OSRESULT.

OUTRES is also valid in PREP7.

Example

When issuing an OUTRES command, think of a matrix in which you set switches on and off. When a switch is on, a solution item is stored for the specified substep. When a switch is off, a solution item is suppressed for a specified substep.

Assuming a static (ANTYPE,STATIC) analysis, this example shows how the matrix looks after issuing each OUTRES command in this six-substep solution.

NSUBST,6
OUTRES,ERASE
OUTRES,NSOL,2
OUTRES,ALL,3
OUTRES,ESOL,4
SOLVE

To simplify the example, only a subset of the available solution items appears in the matrix.

OUTRES,ERASE -- After issuing this command, the default output specifications are in effect, as shown:

OUTRES,NSOL,2 -- This command modifies the initial specifications so that NSOL is enabled for substeps 2, 4 and 6, and disabled for substeps 1, 3 and 5, as shown:

OUTRES,ALL,3 -- This command further modifies the specifications so that ALL is enabled for substeps 3 and 6, and disabled for substeps 1, 2, 4 and 5, as shown:

OUTRES,ESOL,4 -- This command once again modifies the specifications so that ESOL is enabled for the fourth and last substeps, and disabled for substeps 1, 2, 3 and 5, as shown:

SOLVE

When obtaining the solution, results data are stored as follows:

Menu Paths