OUTRES

OUTRES, Item, Freq, Cname, -- , NSVAR, DSUBres
Controls the solution data written to the database.

Compatible Products: – | Pro | Premium | Enterprise | Ent PP | Ent Solver | –

Item

Results item for database and file write control:

ALL

 — 

All solution items except LOCI and SVAR. This behavior is the default.

CINT

 — 

All available results generated by the CINT command

ERASE

 — 

Resets OUTRES specifications to their default values.

STAT

 — 

Lists the current OUTRES specifications.

BASIC

 — 

Write only NSOL, RSOL, NLOAD, STRS, FGRAD, and FFLUX records to the results file and database.

NSOL

 — 

Nodal DOF solution.

RSOL

 — 

Nodal reaction loads.

V

 — 

Nodal velocity (applicable to structural full transient analysis only (ANTYPE,TRANS)).

A

 — 

Nodal acceleration (applicable to structural full transient analysis only (ANTYPE,TRANS)).

ESOL

 — 

Element solution (includes all items following):

NLOAD

 — 

Element nodal, input constraint, and force loads (also used with the /POST1 commands PRRFOR, NFORCE, and FSUM to calculate reaction loads).

STRS

 — 

Element nodal stresses.

EPEL

 — 

Element elastic strains.

EPTH

 — 

Element thermal, initial, and swelling strains.

EPPL

 — 

Element plastic strains.

EPCR

 — 

Element creep strains.

EPDI

 — 

Element diffusion strains.

FGRAD

 — 

Element nodal gradients.

FFLUX

 — 

Element nodal fluxes.

LOCI

 — 

Integration point locations.

SVAR

 — 

State variables (used only by UserMat).

MISC

 — 

Element miscellaneous data (SMISC and NMISC items of the ETABLE command).

Freq

Specifies how often (that is, at which substeps) to write the specified solution results item. The following values are valid:

ValueDescription
nWrites the specified results item every nth (and the last) substep of each load step.
-nWrites up to n equally spaced solutions.

The time range is divided into equally spaced time points. The first solution at or just past the time point is written. If the time steps span two time points, only one is written.​

NONESuppresses writing of the specified results item for all substeps.
ALLWrites the solution of the specified solution results item for every substep. This value is the default for a harmonic analysis (ANTYPE,HARMIC) and for any expansion pass (EXPASS,ON).
LASTWrites the specified solution results item only for the last substep of each load step. This value is the default for a static (ANTYPE,STATIC) or transient (ANTYPE,TRANS) analysis.
%array%Where array is the name of an n x 1 x 1 dimensional array parameter defining n key times, the data for the specified solution results item is written at those key times.

Key times in the array parameter must appear in ascending order. Values must be greater than or equal to the beginning values of the load step, and less than or equal to the ending time values of the load step.

For multiple-load-step problems, either change the parameter values to fall between the beginning and ending time values of the load step or erase the current settings and reissue the command with a new array parameter.

For more information about defining array parameters, see the *DIM command documentation.

Cname

The name of the component, created with the CM command, defining the selected set of elements or nodes for which this specification is active. If blank, the set is all entities. A component name is not allowed with the ALL, BASIC, or RSOL items.

--

Reserved for future use.

NSVAR

The number of user-defined state variables (TB,STATE) to be written to the results file. Valid only when Item = SVAR and user-defined state variables exist. The specified value cannot exceed the total number of state variables defined; if no value is specified, all user-defined state variables are written to the results file. This argument acts on all sets of user-defined state variables that exist for the model.

DSUBres

Specifies whether to write additional results in Jobname.DSUB during a substructure or CMS use pass in transient or harmonic analysis.

Blank

 — 

Write the nodal DOF solution in Jobname.DSUB (default).

ALL

 — 

In addition to the nodal DOF solution, also write necessary data to compute quantities using nodal velocity and nodal acceleration (damping force, inertial force, kinetic energy, etc.) in the subsequent expansion pass. For more information, see Step 3: Expansion Pass in the Substructuring Analysis Guide.

Command Default

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

  • For static (ANTYPE,STATIC) or transient (ANTYPE,TRANS) analyses, the default is to write the specified solution results item for the last substep of each load step.

  • For a harmonic analysis (ANTYPE,HARMIC) and any expansion pass, the default is to write the specified solution results item for every substep.

  • For mode-superposition transients, the default is to write the reduced displacements file for every 4th substep (as well as the last substep); however, if gap conditions exist, the default is to write the specified solution results item of every substep.

Notes

The OUTRES command allows you to specify the following:

  • The solution item (Item) to write to the database (and to the reduced displacement and results files)

  • The frequency (Freq) at which the solution item is written (applicable to static, transient, or full harmonic analyses)

  • The set of elements or nodes (Cname) to which your specification applies.

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.


Important:  In the results-item hierarchy, certain items are subsets of other items. For example, element solution (ESOL) data is a subset of all (ALL) solution data. An OUTRES,ALL command can therefore affect ESOL data. Likewise, an OUTRES command that controls ESOL data can affect a portion of all data.

The example OUTRES commands illustrate the interrelationships between results items and the necessity of issuing the OUTRES command thoughtfully.


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 modal analysis, the only valid values are NONE or ALL.

  • If you issue multiple OUTRES commands during an analysis, you cannot specify a key time array parameter (%array%) in a given OUTRES command and then specify a different Freq option in a subsequent OUTRES command.

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:

SubstepResults Item Specification
ALL
BASIC
NSOLRSOLESOL
NLOADSTRSFGRADEPELEPTH
1offoffoffoffoffoffoff
2offoffoffoffoffoffoff
3offoffoffoffoffoffoff
4offoffoffoffoffoffoff
5offoffoffoffoffoffoff
6ONONONONONONON

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:

SubstepResults Item Specification
ALL
BASIC
NSOLRSOLESOL
NLOADSTRSFGRADEPELEPTH
1offoffoffoffoffoffoff
2ONoffoffoffoffoffoff
3offoffoffoffoffoffoff
4ONoffoffoffoffoffoff
5offoffoffoffoffoffoff
6ONONONONONONON

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:

SubstepResults Item Specification
ALL
BASIC
NSOLRSOLESOL
NLOADSTRSFGRADEPELEPTH
1offoffoffoffoffoffoff
2offoffoffoffoffoffoff
3ONONONONONONON
4offoffoffoffoffoffoff
5offoffoffoffoffoffoff
6ONONONONONONON

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:

SubstepResults Item Specification
ALL
BASIC
NSOLRSOLESOL
NLOADSTRSFGRADEPELEPTH
1offoffoffoffoffoffoff
2offoffoffoffoffoffoff
3ONONoffoffoffoffoff
4offoffONONONONON
5offoffoffoffoffoffoff
6ONONONONONONON

SOLVE

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

SubstepResults Items Stored
1No data
2No data
3NSOL and RSOL data
4ESOL data
5No data
6ALL data

Menu Paths

Main Menu>Preprocessor>Loads>Analysis Type>Sol'n Controls>Basic
Main Menu>Preprocessor>Loads>Load Step Opts>Output Ctrls>DB/Results File
Main Menu>Solution>Analysis Type>Sol'n Controls>Basic
Main Menu>Solution>Load Step Opts>Output Ctrls>DB/Results File

Release 17.0 - © SAS IP, Inc. All rights reserved.