Command Default

The OUTRES command writes the specified solution results item for every substep. The exceptions to the default behavior are as follows:

Notes

The OUTRES command allows you to specify the following:

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

You can issue multiple OUTRES commands 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.

Besides OUTRES, another output-control command named OUTPR exists which controls solution printout. You can issue up to 50 output-control commands (either OUTRES or OUTPR, or some combination of both) in an analysis.

Issuing OUTRES,ERASE erases the existing output specifications and resets the counted number of OUTRES commands to zero. Issuing OUTPR,ERASE affects the OUTPR command in the same way.

A given OUTRES command has no effect on results 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.

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 an OUTRES,ALL,NONE command. (An OUTRES,ERASE command does not suppress all data at every substep.)

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

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.

When specifying a Freq value, observe the following:

For a coupled-field analysis using the ANSYS Multi-field Solver, Freq cannot be NONE for Item = NSOL or ESOL because interface loads have to be retrieved from the database.

The OUTRES command 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 results item is stored for the specified substep. When a switch is off, a results 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 turned on for substeps 2, 4 and 6, and turned off for substeps 1, 3 and 5, as shown:

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

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

SOLVE

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

Menu Paths