Filtering Output and Operating on Output in Abaqus/Explicit

You can define three types of low-pass Infinite Impulse Response filters as part of the model definition. Typical magnitude curves for analog type filters are presented in Figure 1, where ${\mathrm{\Omega }}_c$ represents the normalized cutoff frequency, which is the ratio of the cutoff frequency to the sampling frequency (the sampling frequency is the inverse of the time increment).

Figure 1. Typical magnitude curves for low-pass filters.

The Butterworth filter is very common; its response in the pass band is known as maximally flat. The Type I Chebyshev filter has a sharper transition between the pass band and the stop band, but it has a ripple in the pass band. The Type II Chebyshev filter also has a sharper transition between the pass band and the stop band than a Butterworth filter of the same order, but it has a ripple in the stop band. The higher the order of the filter, the narrower the transition band. However, the computational cost increases as the order increases. In addition, for high-order filters the phase lag, which is the time delay between the filtered and unfiltered signal, may become significant. For most applications filter orders of two or four are sufficiently accurate.

To define a Butterworth filter, you must specify the cutoff frequency, $f_c$ , and the filter order, N. Since the implementation of the filters is done using cascades of second-order sections, Abaqus expects an even number for the filter order. If you specify an odd number for the order, the order will be increased internally to the next even number. The default value for the order is two, and the highest order that can be prescribed is twenty. For the Chebyshev filters you must also specify an additional parameter, the ripple factor. The ripple factor is equal to $ϵ$ for a Type I Chebyshev filter and is equal to $1/A$ for a Type II Chebyshev filter (see Figure 1).

No checks are performed to ensure that the cutoff frequency is appropriate; for example, Abaqus does not check that only the noise of the signal is eliminated. You need to know the range of the physical frequencies that are expected in the solution, and you must prescribe a cutoff frequency greater than these frequencies. In addition, the cutoff frequency should be less than half the sampling frequency; otherwise, no filtering is performed. Abaqus internally remaps (using a quadratic interpolation) the output raw data so that the filtering can satisfy the constant time-increment (sampling) requirement.

FILTER, NAME=filter_name, TYPE=BUTTERWORTH 
FILTER, NAME=filter_name, TYPE=CHEBYS1
FILTER, NAME=filter_name, TYPE=CHEBYS2

Step module: ToolsFilterCreate: Name: filter_name; Butterworth, Type I Chebyshev, or Type II Chebyshev

FILTER, NAME=filter_name, TYPE=filter_type, START CONDITION=DC

FILTER, NAME=filter_name, TYPE=filter_type, 
START CONDITION=USER DEFINED

To pre-filter element, nodal, contact, or integrated history output or element and nodal field output based on one of the low-pass Infinite Impulse Response filters that you defined, you refer to this filter by name from the output request.

OUTPUT, FILTER=filter_name

Step module: field or history output request editor: Apply filter: filter_name

For history output you can request that Abaqus/Explicit create an antialiasing filter that is internally based on the time interval specified in the output request. The cutoff frequency is set internally to one-sixth of the time frequency (the time frequency is the inverse of the time interval, t, used for history output). If no time intervals are specified, the default number of history output intervals is used to create the cutoff frequency of the filter. You can also use antialiasing filters for a field output request, but in this case the cutoff frequency is set to one-sixth of a time frequency corresponding to two hundred time intervals per step if less than two hundred field frames are requested. If more than two hundred field frames are requested, the cutoff frequency is set to one-sixth of the requested time frequency. The antialiasing filter is a second-order Butterworth type and a filter definition is not required.

Abaqus/Explicit does not check whether the specified time interval for history output provides an appropriate cutoff frequency to build the internal filter. You should know approximately how many data points are required to describe your history curve (or signal) accurately, and Abaqus/Explicit will give you the most physical (un-aliased) representation of the signal for that number of points. Similarly for field output Abaqus/Explicit does not check whether the cutoff corresponding to two hundred sampling intervals or more (if you request more than two hundred frames) is appropriate for your analysis. If a lower (or higher) cutoff frequency is needed, you should define the filter in the model data.

OUTPUT, FIELD, FILTER=ANTIALIASING, TIME INTERVAL=t

OUTPUT, HISTORY, FILTER=ANTIALIASING, TIME INTERVAL=t

Step module: field or history output request editor: Frequency: Every x units of time: t, Apply filter: Antialiasing

OUTPUT, FIELD, FILTER=ANTIALIASING, NUMBER INTERVAL=n

Step module: field output request editor: Frequency: Evenly spaced time intervals, Interval: n, Apply filter: Antialiasing

You can apply a filter to a field output request or a history output request to obtain the maximum, minimum, or absolute maximum values for each variable in the output request. The absolute maximum option enables you to obtain the largest absolute value, negative or positive, for each variable in the output request. Abaqus evaluates maximum, minimum, or absolute maximum values at every increment during the analysis and reports these values at the time given by the output interval specified in the output request. For field output requests the last output frame will contain the maximum (or absolute maximum) value and minimum value over the entire step; the intermediate frames will show the maximum, minimum, or absolute maximum value up to the frame time. An additional output variable containing the time when the maximum, minimum, or absolute maximum occurred is output automatically for each output variable requested. This time output is written by default (and it cannot be suppressed).

For field output requests Abaqus filters by default each component of tensor and vector quantities of output variable independently and provides separate maximum, minimum, or absolute maximum values for each component of the variable. You can, however, request the maximum or minimum value or apply a limit value to an invariant such as Mises stress for element output or magnitude for nodal output (see Applying Bounding Values to Invariants).

FILTER, TYPE=filter_type, OPERATOR=MAX
FILTER, TYPE=filter_type, OPERATOR=MIN
FILTER, TYPE=filter_type, OPERATOR=ABSMAX

FILTER, OPERATOR=MAX
FILTER, OPERATOR=MIN
FILTER, OPERATOR=ABSMAX

You can apply a filter to a field output request or a history output request to prescribe a bounding value for the variables in the output request. If any of the variables in the output request reach a value higher than the maximum limit, lower than the minimum limit, or greater than the absolute maximum limit, Abaqus returns the limiting value. The time at which the limit was reached is output separately for each requested variable. This time output is written by default (and it cannot be suppressed). You can also request an additional field output frame when the limiting value is reached.

FILTER, TYPE=filter_type, OPERATOR=operator_type, LIMIT=value

FILTER, OPERATOR=operator_type, LIMIT=value

FILTER, OPERATOR=operator_type, LIMIT=value, EXTRA OUTPUT FRAME=YES or NO

You can apply a filter to a field output request or a history output request that stops the analysis or concludes a step when the value of any variable in the output request reaches a specified upper bound or lower bound.

FILTER, TYPE=filter_type, OPERATOR=operator_type, LIMIT=value, HALT=ANALYSIS or STEP

FILTER, OPERATOR=operator_type, LIMIT=value, HALT=ANALYSIS or STEP

By default, each component of a tensor or vector quantity is filtered individually and the maximum, minimum, or absolute maximum value and the limiting values are reported separately for each component. You can, however, apply a filter directly to an invariant. In this case Abaqus internally monitors the invariant you specified. Abaqus still writes the components to the output database, but these components correspond to the maximum, minimum, or limiting values of the invariant. Table 1 shows which invariants are available for output variable categories.

FILTER, TYPE=filter_type, OPERATOR=operator_type, LIMIT=value, INVARIANT=FIRST, SECOND, MAXP, INTERMP, or MINP

FILTER, OPERATOR=operator_type, LIMIT=value, INVARIANT= FIRST or SECOND

Low-pass Infinite Impulse Response filters such as Butterworth and Chebyshev filters are intended for filtering of output variables susceptible to noise, such as accelerations and reaction forces or, to a lesser degree, stress and strain. However, digital filtering is allowed for most element and nodal output variables, and you can apply bounding values on unfiltered data for nearly all element and nodal output variables. Table 2 shows the set of output variables that cannot be digitally filtered but to which you can apply bounding values, and Table 3 shows the set of output variables for which neither digital filtering nor application of bounding values are allowed.