An analysis history is defined in Abaqus by:
dividing the problem history into steps;
specifying an analysis procedure for each step; and
prescribing loads, boundary conditions, base motions, and output requests for each step.
A basic concept in Abaqus is the division of the problem history into steps. A step is any convenient phase of the history—a thermal transient, a creep hold, a dynamic transient, etc. In its simplest form a step can be just a static analysis in Abaqus/Standard of a load change from one magnitude to another. You can provide a description of each step that will appear in the data (.dat) file; this description is for convenience only.
| Abaqus/CAE Usage: | Step module: Create Step: Description |
For each step you choose an analysis procedure. This choice defines the type of analysis to be performed during the step: static stress analysis, dynamic stress analysis, eigenvalue buckling, transient heat transfer analysis, etc. The available analysis procedures are listed below and are described in the sections that follow. Only one procedure is allowed per step. Within Abaqus/Standard or Abaqus/Explicit, any combination of available procedures can be used from step to step. However, Abaqus/Standard and Abaqus/Explicit procedures cannot be used in the same analysis. See “Transferring results between Abaqus analyses: overview,” Section 9.2.1, for information on importing results from one type of analysis to another.
The rest of the step definition consists of load, boundary, and output request specifications (see “Applying loads: overview,” Section 32.4.1; “Boundary conditions in Abaqus/Standard and Abaqus/Explicit,” Section 32.3.1; and “Output,” Section 4.1.1).
| Input File Usage: | The procedure definition option must immediately follow the *STEP option. |
| Abaqus/CAE Usage: | Step module: Create Step: choose the procedure type |
There are two kinds of steps in Abaqus: general analysis steps, which can be used to analyze linear or nonlinear response, and linear perturbation steps, which can be used only to analyze linear problems. General analysis steps can be included in an Abaqus/Standard or Abaqus/Explicit analysis; linear perturbation analysis steps are available only in Abaqus/Standard. In Abaqus/Standard linear analysis is always considered to be linear perturbation analysis about the state at the time when the linear analysis procedure is introduced. This linear perturbation approach allows general application of linear analysis techniques in cases where the linear response depends on preloading or on the nonlinear response history of the model. See “General and linear perturbation procedures,” Section 6.1.2, for more details.
In general analysis steps Abaqus/Standard calculates the solution for a single set of applied loads. This is also the default for linear perturbation steps. However, for static, direct steady-state dynamic, and SIM-based steady-state dynamic linear perturbation steps it is possible to find solutions for multiple load cases. See “Multiple load case analysis,” Section 6.1.3, for a description of this capability.
The analysis procedure can be changed from step to step in any meaningful way, so you have great flexibility in performing analyses. Since the state of the model (stresses, strains, temperatures, etc.) is updated throughout all general analysis steps, the effects of previous history are always included in the response in each new analysis step. Thus, for example, if natural frequency extraction is performed after a geometrically nonlinear static analysis step, the preload stiffness will be included. Linear perturbation steps have no effect on subsequent general analysis steps.
The most obvious reason for using several steps in an analysis is to change analysis procedure type. However, several steps can also be used as a matter of convenience—for example, to change output requests, contact pairs in Abaqus/Explicit, boundary conditions, or loading (any information specified as history, or step-dependent, data). Sometimes an analysis may have progressed to a point where the present step definition needs to be modified. Abaqus provides for this contingency with the restart capability, whereby a step can be terminated prematurely and a new step can be defined for the problem continuation (see “Restarting an analysis,” Section 9.1.1).
Optional history data (see “Defining a model in Abaqus,” Section 1.3.1) prescribing the loading, boundary conditions, output controls, and auxiliary controls will remain in effect for all subsequent general analysis steps, including those that are defined in a restart analysis, until they are modified or reset. Abaqus will compare all loads and boundary conditions specified in a step with the loads and boundary conditions in effect during the previous step to ensure consistency and continuity. This comparison is expensive if the number of individually specified loads and boundary conditions is very large. Hence, the number of individually specified loads and boundary conditions should be minimized, which can usually be done by using element and node sets instead of individual elements and nodes. For linear perturbation steps only the output controls are continued from one linear perturbation step to the next if there are no intermediate general analysis steps and the output controls are not redefined (see “Output,” Section 4.1.1).
A large class of stress analysis problems can be solved with Abaqus. A fundamental division of such problems is into static or dynamic response; dynamic problems are those in which inertia effects are significant.
Abaqus/Standard offers complete flexibility in making the distinction between static and dynamic response; the same analysis can contain several static and dynamic phases. Thus, a static preload might be applied, and then the linear or nonlinear dynamic response computed (as in the case of vibrations of a component of a rotating machine or the response of a flexible offshore system that is initially moved to an equilibrium position subject to buoyancy and steady current loads and then is excited by wave loading). Similarly, the static solution can be sought after a dynamic event (by following a dynamic analysis step with a step of static loading). See “Static stress/displacement analysis,” Section 6.2, and “Dynamic stress/displacement analysis,” Section 6.3, for information on these types of procedures. In addition to static and dynamic stress analysis, Abaqus/Standard offers the following analysis types:
Abaqus/Explicit solves dynamic response problems using an explicit direct-integration procedure. See “Dynamic stress/displacement analysis,” Section 6.3, for more information on the explicit dynamic procedures available in Abaqus. Abaqus/Explicit also provides heat transfer and acoustic analysis capabilities: see “Heat transfer and thermal-stress analysis,” Section 6.5, and “Acoustic and shock analysis,” Section 6.10, for details.
Abaqus/CFD solves a broad range of incompressible flow problems using a second-order projection method. See “Fluid dynamic analysis,” Section 6.6, for details on the incompressible flow procedures available in Abaqus.
Multiphysics is a coupled approach in the numerical solution of multiple interacting physical domains. Native Abaqus multiphysics capabilities solve the physics by adding degrees of freedom representing each of the physical fields and using a single solver.
Abaqus provides the following built-in fully coupled procedures to solve multidisciplinary simulations, where all physics fields are computed by Abaqus:
“Fully coupled thermal-electrical-structural analysis,” Section 6.7.4
“Coupled pore fluid diffusion and stress analysis,” Section 6.8.1
“Acoustic, shock, and coupled acoustic-structural analysis,” Section 6.10.1
The following analysis techniques are available in Abaqus/Standard, Abaqus/Explicit, and Abaqus/CFD:
Results can be transferred between Abaqus/Standard and Abaqus/Explicit (“Transferring results between Abaqus analyses: overview,” Section 9.2.1).In addition, the following analysis techniques are provided in Abaqus/Standard and Abaqus/Explicit as indicated below:
By default, Abaqus assumes that external parameters, such as load magnitudes and boundary conditions, are constant (step function) or vary linearly (ramped) over a step, depending on the analysis procedure, as shown in Table 6.1.1–1. Some exceptions in Abaqus/Standard are discussed below.
Table 6.1.1–1 Default amplitude variations for time domain procedures.
| Procedure | Default amplitude variation |
|---|---|
| Coupled pore fluid diffusion/stress (steady-state) | Ramp |
| Coupled pore fluid diffusion/stress (transient) | Step |
| Coupled thermal-electrical (steady-state) | Ramp |
| Coupled thermal-electrical (transient) | Step |
| Direct-integration dynamic | Step (exception: Ramp if quasi-static application type is specified) |
| Fully coupled thermal-electrical-structural in Abaqus/Standard (steady-state) | Ramp |
| Fully coupled thermal-electrical-structural in Abaqus/Standard (transient) | Step |
| Fully coupled thermal-stress in Abaqus/Standard (steady-state) | Ramp |
| Fully coupled thermal-stress in Abaqus/Standard (transient) | Step |
| Fully coupled thermal-stress in Abaqus/Explicit | Step |
| Incompressible flow | Step |
| Mass diffusion (steady-state) | Ramp |
| Mass diffusion (transient) | Step |
| Quasi-static | Step |
| Static | Ramp |
| Steady-state transport | Ramp |
| Transient modal dynamic | Step |
| Uncoupled heat transfer | Ramp |
| Uncoupled heat transfer (transient) | Step |
No default amplitude variation is defined for a direct cyclic analysis step; for each applied load or boundary condition, the amplitude must be defined explicitly.
For displacement or rotation degrees of freedom prescribed in Abaqus/Standard using displacement-type boundary conditions or displacement-type connector motions, the default amplitude variation is a ramp function for all procedure types; the default amplitude is a step function for all procedure types when using velocity-type boundary conditions or velocity-type connector motions.
For motions prescribed using a predefined displacement field, the default amplitude variation is a ramp function for all procedure types; the default amplitude is a step function when using a predefined velocity field for all procedures except steady-state transport.
The default amplitude variation is a step function for fluid flux loading in all procedure types.
When a displacement or rotation boundary condition is removed, the corresponding reaction force or moment is reduced to zero according to the amplitude defined for the step. When film or radiation loads are removed, the variation is always a step function.
You can define complicated time variations of loadings, boundary conditions, and predefined fields by referring to an amplitude curve in the prescribed condition definition (see “Amplitude curves,” Section 32.1.2). User subroutines are also provided in Abaqus/Standard and Abaqus/Explicit for coding general loadings (see “User subroutines: overview,” Section 17.1.1).
In Abaqus/Standard you can change the default amplitude variation for a step (except the removal of film or radiation loads, as noted above).
| Input File Usage: | In Abaqus/Standard use the following option to change the default amplitude variation for a step: |
*STEP, AMPLITUDE=STEP or RAMP |
| Abaqus/CAE Usage: | In Abaqus/Standard use the following input to change the default amplitude variation for a step: |
Step module: step editor: Other: Default load variation with time: Instantaneous or Ramp linearly over step |
Boundary conditions applied during an explicit dynamic response step should use appropriate amplitude references to define the time variation. If boundary conditions are specified for the step without amplitude references, they are applied instantaneously at the beginning of the step. Since Abaqus/Explicit does not admit jumps in displacement, the value of a nonzero displacement boundary condition that is specified without an amplitude reference will be ignored, and a zero velocity boundary condition will be enforced.
The default amplitude is a step function for transient analysis procedures (fully coupled thermal-stress, fully coupled thermal-electrical-structural, coupled thermal-electrical, direct-integration dynamic, uncoupled heat transfer, and mass diffusion). Care should be exercised when the nondefault ramp amplitude variation is specified for transient analysis procedures since unexpected results may occur. For example, if a step of a transient heat transfer analysis uses the ramp amplitude variation and temperature boundary conditions are removed in a subsequent step, the reaction fluxes generated in the previous step will be ramped to zero from their initial values over the duration of the step. Therefore, heat flux will continue to flow through the affected boundary nodes over the entire subsequent step even though the temperature boundary conditions were removed.
Each step in an Abaqus analysis is divided into multiple increments. In most cases you have two choices for controlling the solution: automatic time incrementation or user-specified fixed time incrementation. Automatic incrementation is recommended for most cases. The methods for selecting automatic or direct incrementation are discussed in the individual procedure sections.
The issues associated with time incrementation in Abaqus/Standard, Abaqus/Explicit, and Abaqus/CFD analyses are quite different. The time increments are generally much smaller in Abaqus/Explicit than in Abaqus/Standard, while the time increments for Abaqus/CFD may be similar to those in Abaqus/Standard in many situations.
In nonlinear problems Abaqus/Standard will increment and iterate as necessary to analyze a step, depending on the severity of the nonlinearity. In transient cases with a physical time scale, you can provide parameters to indicate a level of accuracy in the time integration, and Abaqus/Standard will choose the time increments to achieve this accuracy. Direct user control is provided because it can sometimes save computational cost in cases where you are familiar with the problem and know a suitable incrementation scheme. Direct control can also occasionally be useful when automatic control has trouble with convergence in nonlinear problems.
You can define the upper limit to the number of increments in an Abaqus/Standard analysis. In a direct cyclic analysis procedure, this upper limit should be set to the maximum number of increments in a single loading cycle. The default is 100. The analysis will stop if this maximum is exceeded before the complete solution for the step has been obtained. To arrive at a solution, it is often necessary to increase the number of increments allowed by defining a new upper limit.
| Input File Usage: | *STEP, INC=n |
| Abaqus/CAE Usage: | Step module: step editor: Incrementation: Maximum number of increments |
In nonlinear analyses Abaqus/Standard uses extrapolation to speed up the solution. Extrapolation refers to the method used to determine the first guess to the incremental solution. The guess is determined by the size of the current time increment and by whether linear, displacement-based parabolic, velocity-based parabolic, or no extrapolation of the previously attained history of each solution variable is chosen. Displacement-based parabolic extrapolation is not relevant for Riks analyses, and velocity-based parabolic extrapolation is available only for direct-integration dynamic procedures. Linear extrapolation (the default for all procedures other than a direct-integration dynamic procedure using the transient fidelity application setting) uses 100% extrapolation (1% for the Riks method) of the previous incremental solution at the start of each increment to begin the nonlinear equation solution for the next increment. No extrapolation is used in the first increment of a step.
In some cases extrapolation can cause Abaqus/Standard to iterate excessively; some common examples are abrupt changes in the load magnitudes or boundary conditions and if unloading occurs as a result of cracking (in concrete models) or buckling. In such cases you should suppress extrapolation.
Displacement-based parabolic extrapolation uses two previous incremental solutions to obtain the first guess to the current incremental solution. This type of extrapolation is useful in situations when the local variation of the solution with respect to the time scale of the problem is expected to be quadratic, such as the large rotation of structures. If parabolic extrapolation is used in a step, it begins after the second increment of the step: the first increment employs no extrapolation, and the second increment employs linear extrapolation. Consequently, slower convergence rates may occur during the first two increments of the succeeding steps in a multistep analysis.
Velocity-based parabolic extrapolation uses the previous displacement incremental solution to obtain the first guess to the current incremental solution. It is available only for direct-integration dynamic procedures, and it is the default if the transient fidelity application setting is specified as part of this procedure (see “Implicit dynamic analysis using direct integration,” Section 6.3.2). This type of extrapolation is useful in situations with smooth solutions—i.e., when velocities do not display so called “saw tooth” patterns—and in such cases it may provide a better first guess than other extrapolations. If velocity-based parabolic extrapolation is used in a step, it begins after the first increment of the step; the first increment employs initial velocities.
| Input File Usage: | Use the following option to choose linear extrapolation: |
*STEP, EXTRAPOLATION=LINEAR (default for all procedures other than a direct-integration dynamic procedure using the transient fidelity application setting) Use the following option to choose displacement-based parabolic extrapolation: *STEP, EXTRAPOLATION=PARABOLIC Use the following option to choose velocity-based parabolic extrapolation: *STEP, EXTRAPOLATION=VELOCITY PARABOLIC (default for a direct-integration dynamic procedure using the transient fidelity application setting) Use the following option to choose no extrapolation: *STEP, EXTRAPOLATION= NO |
| Abaqus/CAE Usage: | Step module: step editor: Other: Extrapolation of previous state at start of each increment: Linear, Parabolic, Velocity parabolic, None, or Analysis product default |
The time increment used in an Abaqus/Explicit analysis must be smaller than the stability limit of the central-difference operator (see “Explicit dynamic analysis,” Section 6.3.3); failure to use a small enough time increment will result in an unstable solution. Although the time increments chosen by Abaqus/Explicit generally satisfy the stability criterion, user control over the size of the time increment is provided to reduce the chance of a solution going unstable. The small increments characteristic of an explicit dynamic analysis product make Abaqus/Explicit well suited for nonlinear analysis.
Abaqus/Standard distinguishes between regular, equilibrium iterations (in which the solution varies smoothly) and severe discontinuity iterations (SDIs) in which abrupt changes in stiffness occur. The most common of such severe discontinuities involve open-close changes in contact and stick-slip changes in friction. By default, Abaqus/Standard will continue to iterate until the severe discontinuities are sufficiently small (or no severe discontinuities occur) and the equilibrium (flux) tolerances are satisfied. Alternatively, you can choose a different approach in which Abaqus/Standard will continue to iterate until no severe discontinuities occur.
For contact openings with the default approach, a force discontinuity is generated when the contact force is set to zero, and this force discontinuity leads to force residuals that are checked against the time average force in the usual way, as described in “Convergence criteria for nonlinear problems,” Section 7.2.3. Similarly, in stick-to-slip transitions the frictional force is set to a lower value, which also leads to force residuals.
For contact closures a severe discontinuity is considered sufficiently small if the penetration error is smaller than the contact compatibility tolerance times the incremental displacement. The penetration error is defined as the difference between the actual penetration and the penetration following from the contact pressure and pressure-overclosure relation. In cases where the displacement increment is essentially zero, a “zero penetration” check is used, similar to the check used for zero displacement increments (see “Convergence criteria for nonlinear problems,” Section 7.2.3). The same checks are used for slip-to-stick transitions in Lagrange friction.
To make sure that sufficient accuracy is obtained for contact between hard bodies, it is also required that the estimated contact force error is smaller than the time average force times the contact force error tolerance. The estimated contact force error is obtained by multiplying the penetration by an effective stiffness. For hard contact this effective stiffness is equal to the stiffness of the underlying element, whereas for softened/penalty contact the effective stiffness is obtained by adding the compliance of the contact constraint and the underlying element.
Forcing the iteration process to continue until no severe discontinuities occur is the more traditional, conservative method. However, this method can sometimes lead to convergence problems, particularly in large problems with many contact points or situations where contact conditions are only weakly determined. In such cases excessive iteration may occur and convergence may not be obtained
| Input File Usage: | *STEP, CONVERT SDI=NO |
| Abaqus/CAE Usage: | Step module: step editor: Other: Convert severe discontinuity iterations: Off |
Abaqus/Standard generally uses Newton's method to solve nonlinear problems and the stiffness method to solve linear problems. In both cases the stiffness matrix is needed. In some problems—for example, with Coulomb friction—this matrix is not symmetric. Abaqus/Standard will automatically choose whether a symmetric or unsymmetric matrix storage and solution scheme should be used based on the model and step definition used. In some cases you can override this choice; the rules are explained below.
Usually it is not necessary to specify the matrix storage and solution scheme. The choice is available to improve computational efficiency in those cases where you judge that the default value is not the best choice. In certain cases where the exact tangent stiffness matrix is not symmetric, the extra iterations required by a symmetric approximation to the tangent matrix use less computer time than solving the nonsymmetric tangent matrix at each iteration. Therefore, for example, Abaqus/Standard invokes the symmetric matrix storage and solution scheme automatically in problems with Coulomb friction where every friction coefficient is less than or equal to 0.2, even though the resulting tangent matrix will have some nonsymmetric terms. However, if any friction coefficient is greater than 0.2, Abaqus/Standard will use the unsymmetric matrix storage and solution scheme automatically since it may significantly improve the convergence history. This choice of the unsymmetric matrix storage and solution scheme will consider changes to the friction model. Thus, if you modify the friction definition during the analysis to introduce a friction coefficient greater than 0.2, Abaqus/Standard will activate the unsymmetric matrix storage and solution scheme automatically. In cases in which the unsymmetric matrix storage and solution scheme is selected automatically, you must explicitly turn it off if so desired; it is recommended to do so if friction prevents any sliding motions.
| Input File Usage: | *STEP, UNSYMM=YES or NO |
| Abaqus/CAE Usage: | Step module: step editor: Other: Storage: Use solver default or Unsymmetric or Symmetric |
The following rules apply to matrix storage and solution schemes in Abaqus/Standard:
Since Abaqus/Standard provides eigenvalue extraction only for symmetric matrices, steps with eigenfrequency extraction or eigenvalue buckling prediction procedures always use the symmetric matrix storage and solution scheme. You cannot change this setting. In such steps Abaqus/Standard will symmetrize all contributions to the stiffness matrix.
In all steps except those with eigenfrequency extraction or eigenvalue buckling procedures, Abaqus/Standard uses the unsymmetric matrix storage and solution scheme when any of the following features are included in the model. You cannot change this setting.
Heat transfer convection/diffusion elements (element types DCCxxx)
General shell sections with unsymmetric section stiffness matrices (“Three-dimensional conventional shell element library,” Section 28.6.7)
User-defined elements with unsymmetric element matrices (“User-defined elements,” Section 31.15.1)
User-defined material models with unsymmetric material stiffness matrices (“User-defined mechanical material behavior,” Section 25.7.1, or “User-defined thermal material behavior,” Section 25.7.2)
User-defined surface interaction models with unsymmetric interface stiffness matrices (“User-defined interfacial constitutive behavior,” Section 35.1.6)
The following features all trigger the unsymmetric matrix storage and solution scheme for the step. You cannot change this setting.
Fully coupled thermal-stress analysis, except when a separated solution scheme is specified for the step (“Fully coupled thermal-stress analysis,” Section 6.5.4)
Coupled thermal-electrical analysis, except when a separated solution scheme is specified for the step (“Coupled thermal-electrical analysis,” Section 6.7.3)
Fully coupled thermal-electrical-structural analysis (“Fully coupled thermal-electrical-structural analysis,” Section 6.7.4)
Coupled pore fluid diffusion/stress analysis with absorption or exsorption behavior (“Coupled pore fluid diffusion and stress analysis,” Section 6.8.1)
Coupled pore fluid diffusion/stress analysis (steady-state)
Coupled pore fluid diffusion/stress analysis (transient with gravity loading)
Mass diffusion analysis (“Mass diffusion analysis,” Section 6.9.1)
Radiation viewfactor calculation controls (“Cavity radiation,” Section 39.1.1)
By default, the unsymmetric matrix storage and solution scheme is used for the complex eigenvalue extraction procedure. You can change this setting.
In all other cases you can control whether a symmetric or a full matrix storage and arithmetic solution is chosen. If you do not specify the matrix storage and solution scheme, Abaqus/Standard utilizes the value used in the previous general analysis step.
If you do not specify the matrix storage and solution scheme in the first step of an analysis, Abaqus/Standard will choose the unsymmetric scheme when any of the following are used:
Any Abaqus/Aqua load type
The concrete damaged plasticity material model
Friction with a friction coefficient greater than 0.2
The default value in the first step is the symmetric scheme for all other cases, except those covered by rules 2 and 3 above and for cases in which a friction coefficient is increased above 0.2 after the first step.
For radiative heat transfer surface interactions (“Thermal contact properties,” Section 35.2.1), certain follower forces (such as concentrated follower forces or moments), three-dimensional finite-sliding analyses, any finite sliding in coupled pore fluid diffusion/stress analyses, and certain material models (particularly nonassociated flow plasticity models and concrete) introduce unsymmetric terms in the model's stiffness matrix. However, Abaqus/Standard does not automatically use the unsymmetric matrix storage and solution scheme when radiative heat transfer surface interactions are used. Specifying that the unsymmetric scheme should be used can sometimes improve convergence in such cases.
Coupled structural-acoustic and uncoupled acoustic analysis procedures in Abaqus/Standard generally use symmetric matrix storage and solution. Exceptions are the subspace-based steady-state dynamics or complex frequency procedures used for coupled structural-acoustic problems, where unsymmetric matrices are a consequence of the coupling procedure used in these cases. Using acoustic infinite elements or the acoustic flow velocity option triggers the unsymmetric matrix storage and solution scheme in Abaqus/Standard, except for natural frequency extraction using the Lanczos eigensolver, which uses symmetric matrix operations.
You can choose a double-precision executable (with 64-bit word lengths) for Abaqus/Explicit on machines with a default, single-precision word length of 32 bits (see “Abaqus/Standard, Abaqus/Explicit, and Abaqus/CFD execution,” Section 3.2.2). Most new computers have 32-bit default word lengths even though they may have 64-bit memory addressing. The single-precision executable typically results in a CPU savings of 20% to 30% compared to the double-precision executable, and single precision provides accurate results in most cases. Exceptions in which single precision tends to be inadequate include analyses that require greater than approximately 300,000 increments, have typical nodal displacement increments less than 10–6 times the corresponding nodal coordinate values, include hyperelastic materials, or involve multiple revolutions of deformable parts; the double-precision executable is recommended in these cases (for example, see “Simulation of propeller rotation,” Section 2.3.15 of the Abaqus Benchmarks Manual).
You can also run only a part of Abaqus/Explicit using double precision, while using single precision for the rest (see “Abaqus/Standard, Abaqus/Explicit, and Abaqus/CFD execution,” Section 3.2.2). These options are described below.
If double=explicit is used or the double option is specified without a value, the Abaqus/Explicit analysis will run in double precision, while the packager will run in single precision. While this choice would satisfy higher precision needs in most analyses, the data are written to the state (.abq) file in single precision. Moreover, analysis-related computations performed in the packager will still be executed in single precision. Thus, new steps, restart, and import analyses will commence from data that are stored/computed in single precision despite the fact that calculations during the step are performed in double precision. Thus, in general, one can expect somewhat noisy solutions at the beginning of the first step, at step transitions, upon restart, and after import.
If double=both is used, both the Abaqus/Explicit packager and analysis will run in double precision. This is the most expensive option but will ensure the highest overall execution precision. Analysis database floating point data will be written to the state (.abq) file at the end of packager or of a given step in double precision, thus ensuring in most cases the smoothest transition at step boundaries, upon restart, and after an import.
There may be cases where the default single precision analysis is inadequate, while the double=both option is too expensive. These are typically models that have complex links of constraints (such as a complex mechanism with connector elements, complex combinations of distributed/kinematic couplings, tie constraints and multi-point constraints, or interactions of such constraints with boundary conditions). For such models it is desirable to solve only the constraints in the model in double precision while the rest of the model is solved in single precision. This combination gives the desired accuracy of the solution while increasing performance compared to a full double precision analysis.
If double=constraint is used, the constraint packager and constraint solver are executed in double precision, while the remainder of the Abaqus/Explicit packager and analysis are executed in single precision.
If double=off is used or the double option is omitted (default), both the Abaqus/Explicit packager and the analysis will run in single precision. The double=off option is useful when you want to override the setting in the environment file.
The significance of the precision level is indicated by comparing the solutions obtained with single and double precision. If no significant difference is found between single- and double-precision solutions for a particular model, the single-precision executable can be deemed adequate.