Description: You can create and apply three types of Infinite Impulse Response low-pass filters to ABAQUS/Explicit history output requests: Butterworth, Type I Chebyshev, and Type II Chebyshev. Use real-time filtering to avoid aliasing your history output; aliasing can occur when data are saved with a sampling frequency (the time interval between saves) that is not at least double the highest frequency of interest in the analysis. Without real-time filtering you can ensure that there is no aliasing only if you save every analysis increment to the output database. You can also filter history output to eliminate the noise (the high-frequency—and, thus, undesirable—content of your output). You can specify the cutoff frequency when defining the filter; any frequencies above the cutoff frequency will be eliminated from your output. With filtering applied, you can safely reduce the sampling frequency for your output, which in turn may reduce the size of the output database. An antialiasing filter can be also invoked on saved history output without explicitly defining the filter; the filter is built internally by ABAQUS.

New nodal output variables are available in both ABAQUS/Explicit and ABAQUS/Standard. You can specify that you are interested in only the translational or rotational components of displacements, velocities, and accelerations; and you can specify that you are interested in only the reaction forces or reaction moments. You can also suppress the output of material orientations to reduce the size of the output database. You can now request element field output in ABAQUS/Explicit for certain section points in shell and beam elements, just as you can in ABAQUS/Standard.

You can apply filters when you create a history output request and access the new variables and output options when you create a field output request in ABAQUS/CAE. You must select the output that you want ABAQUS to save during the analysis; you can toggle on Preselected defaults, if desired, to get the default output for the current type of step. The output database is reduced in size by saving only the results that you request and by filtering prior to saving the data.

Step module:
   ToolsFilterCreate
   OutputField Output RequestsCreate
   OutputHistory Output RequestsCreate