Requesting Field Output
Contact surface output, element output, nodal output, and radiation output are available as field output in Abaqus/Standard and Abaqus/Explicit.
ProductsAbaqus/StandardAbaqus/Explicit Field output and history output are controlled by output database requests as described in this section. A subset of the diagnostic information that is written to the message file for Abaqus/Standard analyses and to the status and message files for Abaqus/Explicit analyses is included in the output database.
Output database requests can be repeated as often as necessary within a step to produce both field and history output at multiple frequencies. Requesting Field OutputContact surface output, element output, nodal output, and radiation output are available as field output in Abaqus/Standard and Abaqus/Explicit. Requesting History OutputContact surface output, element output, energy output, integrated output, time incrementation output, modal output, nodal output, and radiation output are available as history output in Abaqus/Standard and Abaqus/Explicit. Requesting large amounts of history output (more than 1000 output requests) may cause performance to degrade in Abaqus/Standard and will cause performance to degrade in Abaqus/Explicit. For vector- or tensor-valued output variables each component is considered to be a single request. In the case of element variables history output will be generated at each integration point. For example, requesting history output of the tensor variable S (stress) for a C3D10M element will generate 24 history output requests: (6 components) × (4 integration points). When requesting history output of vector- and tensor-valued variables, it is recommended that individual components be selected where available. Requesting Diagnostic InformationBy default, a subset of the diagnostic information that is written to the message file for Abaqus/Standard analyses and to the status and message files for Abaqus/Explicit analyses is also written to the output database. |