Writing Default Output to the Output Database

If no output database requests are specified, the preselected field and history output variables are written automatically to the output database.

This page discusses:

In Abaqus/Standard the default variables are written at every increment for both field and history output for all procedure types except dynamic and modal dynamic analyses; the default frequency for field and history output for these procedure types is every 10 increments. In Abaqus/Explicit the default variables are written at 20 intervals for field output and 200 intervals for history output.

 

See Also
About Output
*OUTPUT

Turning off Default Output

You can turn these defaults off by using the odb_output_by_default environment file parameter; see Environment File Settings for details. Furthermore, specifying new output database requests in a step (see Specifying New Output Requests) overrides the default field and history output requests for that step. For large models the default output to the output database may increase the solution time and required disk space considerably. In such cases you are encouraged to review carefully the relevance of the default output variables for the proposed analysis. A C++ program is available that creates a smaller copy of a large output database by copying data from only selected frames; for more information, see .

The odb_output_by_default environment file parameter is ignored in a restart analysis. If no output requests are defined in a restart analysis, the output requests are those that propagate from the original analysis.

Abaqus/Explicit Output as a Result of Analysis Termination

When an Abaqus/Explicit analysis encounters a fatal error in an increment, the preselected variables applicable to the current procedure are written automatically to the output database as field data. The analysis will go through an additional increment with a zero time increment size before writing these data.