Controlling the Output Frequency in Abaqus/Standard
Abaqus/Standard provides several options for controlling the output frequency, depending on whether the analysis is in the time domain (e.g., general statics), frequency domain (e.g., steady state dynamics), or mode domain (e.g., natural frequency extraction). These options can be used to reduce the amount of output written and hence improve performance and disk space use as compared to the default output.
History output in Abaqus/Standard is buffered and is written to disk only after every 10 increments of history data output or when a step has completed. Therefore, history results may not be available immediately for postprocessing.
Default Output Frequency
If you do not specify the output frequency, field and history output will be written at every increment of the analysis for all procedure types except dynamic and modal dynamic analyses for which output will be written every 10 increments.
Controlling Output Frequency in a Frequency Domain Analysis
In frequency domain procedures, you only can control the frequency of output by specifying the frequency of output in increments. The data will be written at this frequency as well as at the end of each step of the analysis. Specify an output frequency of zero to suppress output.
Input File Usage
OUTPUT, FREQUENCY=n
Abaqus/CAE Usage
Step module: field or history output request editor: Frequency: Every n increments: n
Controlling Output Frequency in a Mode Domain Analysis
In an eigenvalue extraction or eigenvalue buckling analysis, you can select the modes at which output is desired. If you do not specify a list of modes, output is produced for all of the modes.
Input File Usage
OUTPUT, FIELD, MODE LIST
Abaqus/CAE Usage
Step module: field output request editor: Frequency: Specify modes: list of modes
Controlling Output Frequency in a Time Domain Analysis
In time domain analyses, you can control the frequency of output by specifying the output frequency in terms of increments, the number of intervals during the step, the size of regular time intervals throughout the step, or time points throughout the step. The different options are described in more detail below.
Whichever option is chosen, the output will always be written at the zero-increment and last increment of the analysis and, for a low-cycle fatigue analysis, at the end of each cycle. The zero-increment output represents the initial conditions for the current analysis step and is essential for sequential thermal-stress analyses and analyses involving submodeling, for which a complete solution history (including the solution state at the beginning of the step) is needed to ensure proper interpolation in time. The zero-increment state is written at the beginning of the step, before the solution of the incremental nonlinear finite-element equations for the step commences, and is therefore in general not an equilibrium solution. Particular examples where the solution is not in equilibrium include the first step of an analysis in which an initial stress state is defined and when loads or boundary condition changes are discontinuous between steps.
Usually, the zero-increment output in any step corresponds to the base state, which is the state of the model at the end of the last general step. The exception to this is modal transient dynamic analysis, where the zero-increment output represents the linear perturbation response at time zero.
By default, when convergence difficulties are encountered in a general step, output is written for the last converged increment. To recover the requested results variables for this last converged increment, a new attempt is performed. There is no message written to the status file or the message file to show this additional attempt. In the output database file you will see an extra attempt and an additional frame. If the previous increment was written to the output database and convergence difficulties are encountered during the current increment, the last converged increment is still written to the output database, which will result in a duplicate output frame at the end of the analysis.
Time Domain Analysis: Specifying Output Frequency in Increments
You can specify how frequently you want output in terms of increments. Specify an output frequency of zero to suppress output.
Input File Usage
OUTPUT, FREQUENCY=n
Abaqus/CAE Usage
Step module: field or history output request editor: Frequency: Every n increments: n
Time Domain Analysis: Specifying Output Frequency in Number of Intervals
You can specify the output frequency in number of intervals, n. The specified number of intervals must be a positive integer.
By default, Abaqus/Standard adjusts the time increment (in some cases Abaqus/Standard might violate the minimum time increment specified) to ensure that data are written at the exact times calculated by dividing the step into n equal intervals. Alternatively, you can specify that the data be written immediately after each time mark. In this case no adjustment of the time increment is necessary.
Input File Usage
Use the following option to request results at the exact time intervals:
OUTPUT, NUMBER INTERVAL=n, TIME MARKS=YES
Use the following option to request results at the increments ending immediately after each time interval:
OUTPUT, NUMBER INTERVAL=n, TIME MARKS=NO
Abaqus/CAE Usage
Use the following option to request results at the exact time intervals:
Step module: field or history output request editor: Frequency: Evenly spaced time intervals, Interval: n, Timing: Output at exact times
Use the following option to request results at the increments ending immediately after each time interval:
Step module: field or history output request editor: Frequency: Evenly spaced time intervals, Interval: n, Timing: Output at approximate times
Time Domain Analysis: Specifying Output Frequency in Regular Time Interval Size
You can write the results at specified regular intervals throughout the step as well as at the end of the step.
By default, Abaqus/Standard will adjust the time increment (in some cases Abaqus/Standard might violate the minimum time increment specified) to ensure that data will be written at the exact times, as defined by multiples of the time interval, t. Alternatively, the data can be written immediately after each time mark. In this case no adjustment of the time increment is necessary.
Input File Usage
Use the following option to request results at the exact time intervals:
OUTPUT, TIME INTERVAL=t , TIME MARKS=YES
Use the following option to request results at the increments ending immediately after each time interval:
OUTPUT, TIME INTERVAL=t , TIME MARKS=NO
Abaqus/CAE Usage
Use the following option to request results at the exact time intervals:
Step module: field or history output request editor: Frequency: Every x units of time: t, Timing: Output at exact times
Use the following option to request results at the increments ending immediately after each time interval:
Step module: field or history output request editor: Frequency: Every x units of time: t, Timing: Output at approximate times
Time Domain Analysis: Specifying Output Frequency in Time Points
You can write the results at specified time points throughout the step.
By default, Abaqus/Standard adjusts the time increment (in some cases Abaqus/Standard might violate the minimum time increment specified) to ensure that data are written at the exact time points specified. Alternatively, you can specify that the data be written immediately after each time point. In this case no adjustment of the time increment is necessary.
Input File Usage
Use the following options to request results at the exact time points:
TIME POINTS, NAME=time points name OUTPUT, TIME POINTS=time points name, TIME MARKS=YES
Use the following options to request results at the increments ending immediately after each time point:
TIME POINTS, NAME=time points name OUTPUT, TIME POINTS=time points name, TIME MARKS=NO
Abaqus/CAE Usage
Use the following option to request results at the exact time points:
Step module: field or history output request editor: From time points, Name: time points name, Timing: Output at exact times
Use the following option to request results at the increments ending immediately after each time point:
Step module: field or history output request editor: From time points, Name: time points name, Timing: Output at approximate times
Time Domain Analysis: Time Incrementation
If the output frequency is specified at exact times and in terms of the number of intervals, in regular time intervals, or in time points, Abaqus/Standard adjusts the time increments to ensure that data are written at the exact time points. In some cases Abaqus may use a time increment smaller than the minimum time increment allowed in the step in the increment directly before a time point. However, Abaqus will not violate the minimum time increment allowed for consolidation, transient mass diffusion, transient heat transfer, transient couple thermal-electrical, transient coupled temperature-displacement, and transient coupled thermal-electrical-structural analyses. For these procedures if a time increment smaller than the minimum time increment is required, Abaqus will use the minimum time increment allowed in the step and will write output data at the first increment after the time point.
When the output frequency is specified at exact times and in terms of the number of intervals, in regular time intervals, or in time points, the number of increments necessary to complete the analysis might increase, which might adversely affect performance.