General Capability for Importing External Fields

You can import external fields from an output database (.sim) file, also referred to as a SIM database (see The Output Database), or from another output database for which a Reader process is available. Once imported, the external field can be used to define distributions, initial conditions, and history-dependent fields (such as loads, boundary conditions, and predefined fields). External fields can also be used for node-based submodeling as discussed in About Submodeling.

The external field can be evaluated at nodes, integration points, or element centers. Conservative mapping is performed automatically if the fields are evaluated at different locations or if the meshes are different. Importing an external field is supported for most two-dimensional and three-dimensional continuum elements. When used to define distributions and initial conditions, external fields are also supported for three-dimensional conventional shell elements made of a single material. All field quantities are exchanged in the global Cartesian coordinate system.

Abaqus offers alternate interfaces for sequential coupling (see Predefined Fields for Sequential Coupling, Sequentially Coupled Thermal-Stress Analysis, and Predefined Loads for Sequential Coupling). These interfaces are limited to importing temperatures, normalized concentrations, and electromagnetic loads of a previous Abaqus analysis.

External fields can be read from various supported output databases. A reader process, an executable designed to read a particular database format, is started by the Abaqus driver to read and transfer the field data. By default, the SIM database (.sim file) reader is used.

You can import external fields from a SIM database (.sim) file. You specify the file name (including the file extension) from which to import external fields.

You can import history-dependent fields from a supported non-SIM database. You must specify the reader executable name and database file name. Consult the respective solver manual to install and determine the reader executable name.

EXTERNAL FIELD, FILE=file name.sim

EXTERNAL FIELD, READER=reader executable name, FILE=file name

You can import external fields to define distributions (see Defining Distributions by Importing Field Data from an Output Database File). A common case is an injection molding manufacturing process where a molten fibrous material is injected into a mold. You can use injection molding software to model the manufacturing process and then import the section and material properties (such as local element orientation and fiber dispersion) into a subsequent stress-displacement simulation.

DISTRIBUTION, TABLE=distribution table name
 , field data
EXTERNAL FIELD, FILE=file name
DISTRIBUTION TABLE, NAME=distribution table name

You can import an external field to adjust nodal coordinates.

One common case is to introduce a geometric imperfection into a model for a postbuckling analysis. In this case, the previous analysis must contain the mode shapes from an eigenfrequency extraction analysis or nodal displacements from a static or dynamic analysis. Mapping is performed if the postbuckling analysis uses a dissimilar mesh. The imperfection is introduced by adjusting the nodal coordinates using the imported modal shapes or nodal displacements.

Another common case is to adjust nodal coordinates using the deformed configuration from a previous analysis. In this case, the previous analysis must write the nodal displacements to a SIM database.

ADJUST, NODE SET=nset, DISTRIBUTION=distribution name
DISTRIBUTION, NAME=distribution name, TABLE=distribution table name
 , field data
EXTERNAL FIELD, FILE=file name, MODE=mode number
DISTRIBUTION TABLE, NAME=distribution table name

ADJUST, NODE SET=nset, DISTRIBUTION=distribution name
DISTRIBUTION, NAME=distribution name, TABLE=distribution table name
 , field data
EXTERNAL FIELD, FILE=file name
DISTRIBUTION TABLE, NAME=distribution table name

You can import an external field to define initial conditions (see Initial Conditions). A common case is a geomechanics analysis where you import an initial pore pressure field. You can compute a pore pressure field using a reservoir code and then import the field into a subsequent geostatic stress state procedure (see Geostatic Stress State). This procedure is used to compute the equilibrium state before performing a geotechnical analysis using the coupled pore fluid diffusion and stress analysis procedure in Abaqus (see Coupled Pore Fluid Diffusion and Stress Analysis). In this case, the reservoir code must write the pore pressure to a SIM database.

INITIAL CONDITIONS
EXTERNAL FIELD, FILE=file name

You can import external fields to define loads, boundary conditions, and predefined fields. A common case is a sequential thermal-stress analysis, where you first perform a heat transfer analysis (see Uncoupled Heat Transfer Analysis) to compute a temperature field and then import the temperatures into a subsequent stress-displacement analysis (see Static Stress Analysis).

You can import external fields for the following time-based analysis procedures:

• Static Stress Analysis

• Implicit Dynamic Analysis Using Direct Integration

• Explicit Dynamic Analysis

• Uncoupled Heat Transfer Analysis

• Fully Coupled Thermal-Stress Analysis

• Piezoelectric Analysis

• Coupled Thermal-Electrical Analysis

• Eddy Current Analysis

• Coupled Pore Fluid Diffusion and Stress Analysis

• Mass Diffusion Analysis

External fields can be imported only in one analysis step per analysis. The analysis step must be a general analysis (nonperturbation) step. For any subsequent analysis steps, the applied external fields remain constant based on the last imported values.

FIELD IMPORT
EXTERNAL FIELD, FILE=file name

If the previous analysis is an Abaqus analysis, you request the source fields to write to the output database (.sim) file. When importing external fields over a time range, you must request output at a frequency to achieve sufficient solution accuracy (see Controlling the Frequency of Output to the Output Database).

When importing an external field, you define the target and source fields. The target field is the field defined in the current analysis. The source field is the field computed in a previous analysis. A field is a physical quantity that spans a region. The field is a node-based field if evaluated at nodes or an element-based field if evaluated at element centroids, integration points, or surface facets. You define a region by specifying a node set, an element set, or a surface regardless of where the field is evaluated.

When a node-based field is imported and an element set from the previous model is specified, the field is extracted from nodes of the elements in the specified element set. Similarly, when a node-based field is imported and a surface from the previous model is specified, the field is extracted from the nodes belonging to the surface facets of the specified surface. When an element-based field is imported and a node set from the previous model is specified, the element field is extracted from elements containing the nodes in the node set. Elements connected to nodes that are not in the node set are not included.

When importing an external field, you specify the region name space, the region name, and the physics quantity for the target field and the source field. The region name space specifies whether the region is a node set, an element set, or a surface. The region name is the name of a node set, element set, or surface.

When specifying the target field and source field parameters, you should consider the following conditions:

• The source field region name is optional. If it is not specified, the entire model is used. However, you are encouraged to provide the source field region name to reduce the computational cost associated with mapping and data transfer. Abaqus has complex naming conventions, especially for assembly definitions. The source file name must correspond to the name written to the SIM results file when reading from a previous Abaqus analysis.
• When defining initial conditions, the target field region name space and physics quantities are defined by the initial condition definition and, consequently, are not used.
• When defining distributions, the target field region name space, region name, and physics quantities are defined by the distribution definition and, consequently, are not used.
• When used for node-based submodeling, the target region is a node set.

The physics quantities for the target field and the source field are defined using identifiers. The physics quantity identifiers for the target field depend on the analysis procedure and are the same identifiers used for co-simulation for imported fields. Table 1 lists the supported identifiers, and detailed information is provided in Identifying the Fields Exchanged across a Co-Simulation Interface). Most field-type quantities can be extracted from the output database file. If the source analysis is an Abaqus analysis, the identifiers are defined in Abaqus/Standard output variable identifiers and Abaqus/Explicit Output Variable Identifiers. Certain output variables are inconsistent between Abaqus solvers. For example, Abaqus/Standard uses the variable NT and Abaqus/Explicit uses the variable NT11 to output nodal temperatures. You should visualize the results database to obtain the appropriate field name.

Fields are mapped automatically when the source and target meshes are topologically different. However, Abaqus performs a mesh check internally before importing distributions and initial conditions, and, if the following conditions are satisfied, no mapping is performed:

• All of the nodes and elements in the target region are found in the source output database (.sim) file with matching labels.
• Matching elements in the target region and the source .sim file have the same connectivities and element types.
• Source data are requested at the same location (nodes or element integration points) where distributions are specified.

FIELD IMPORT
EXTERNAL FIELD, FILE=file name
NODES or ELEMENTS or SURFACE, target region, target quantity ID, NODES or ELEMENTS or SURFACE, source region, source quantity ID

FIELD IMPORT
EXTERNAL FIELD, FILE=thermalAnalysis.sim, START TIME=0, END TIME=3600
ELEMENTS, ESTRESS, NT, ELEMENTS, ETHERMAL, NT

When importing field variables and temperature as a field variable, you might notice differences when you compare the source and target fields. There are two possible causes of these differences:

• Field variables and temperature as a field variable are mapped accurately and imported at nodes. However, when saved to the output database, these quantities are interpolated to element integration points. When contouring, some averaging can occur depending on the contouring parameters selected.
• For fully integrated first-order elements, a selective reduced-integration technique is employed (see Solid isoparametric quadrilaterals and hexahedra). In this case field variables and temperature as a field variable are averaged at the element center and saved to the output database.

The values correctly reflect the internal magnitudes used by Abaqus.

If you are reading from a SIM database to define distributions or initial conditions, you can specify the step and the increment from which to extract the field values. You must ensure that the field is saved to the SIM database at the specified step and increment. If the increment is omitted, the values at the end of the step are imported.

EXTERNAL FIELD, STEP=analysis step, INC=increment

EXTERNAL FIELD, STEP=analysis step

You can import fields at a specified snap-shot point. For a time-domain analysis, a snap-shot point is a specified time. For a frequency-domain analysis, a snap-shot point is a specified frequency or mode number. Frequency-domain results can be imported only from a non-SIM database. If the snap-shot point does not coincide with when the fields were saved, Abaqus linearly interpolates the field values between the snap-shot points available to obtain the field values at the request time or frequency.

You can specify the analysis step. In this case the time refers to the step time to extract field values in the output database, Otherwise, time refers to the total time.

To import the last saved values of an analysis step or of the analysis, do not specify any of the time or frequency parameters. This might be useful when reading from a linear perturbation step or from a steady-state analysis where time has no physical meaning.

EXTERNAL FIELD, TYPE=SNAP SHOT, FILE=file name, TIME=total time

EXTERNAL FIELD,  TYPE=SNAP SHOT, STEP=analysis step, TIME=step time

EXTERNAL FIELD,  TYPE=SNAP SHOT, STEP=analysis step

EXTERNAL FIELD,  TYPE=SNAP SHOT

EXTERNAL FIELD,  TYPE=SNAP SHOT, FREQ=frequency

EXTERNAL FIELDTYPE=SNAP SHOT, MODE=mode number

You can import fields over a specified time range when importing fields to define history-dependent fields. You specify the start time and end time to define the time range in the upstream analysis to import fields.

Typically, data corresponding to the time points (increments of the downstream analysis) are not present in the output database. In this case field values are linearly interpolated between the time points stored in the output database to obtain values at the required time. Because the interpolation is linear, you must ensure that sufficient data is available in the output database to achieve sufficient accuracy.

If you are reading from a SIM database, you can specify the analysis step. In this case the time range refers to the step time to extract field values in the output database. Otherwise, time refers to the total time.

To import results over an analysis step or the entire analysis, do not specify a start and end time. If you omit the end time, results are imported as follows:

• If you specified an analysis step, results are imported to the end of the analysis step.
• If you omitted the analysis step, results are imported to the end of the analysis.

EXTERNAL FIELD, FILE=file name, TYPE=TIME RANGE, START TIME=start time, END TIME=end time

EXTERNAL FIELD, FILE=file name,  TYPE=TIME RANGE, STEP=analysis step, START TIME=start time,  END TIME=step end time

EXTERNAL FIELD, FILE=file name,  TYPE=TIME RANGE

EXTERNAL FIELD, FILE=file name, TYPE=TIME RANGE, START TIME=start time

EXTERNAL FIELD, FILE=file name,  TYPE=TIME RANGE, STEP=analysis step, START TIME=start time, END TIME=step end time

When importing fields over a time range, Abaqus performs no time scaling by default. Specifically, if the upstream analysis time range is larger than the downstream analysis time range, Abaqus imports only the partial upstream fields. When the upstream analysis is shorter than the downstream analysis, Abaqus keeps the last imported field values constant for the remaining duration of the downstream analysis step.

For certain multiphysics simulations, the physics time scales might be different when performing a sequential analysis. For example, you can perform an electromagnetic analysis followed by a thermal-stress analysis importing heat losses. The time scale for the electromagnetic analysis might be significantly shorter than the time scale for conduction in the thermal-stress analysis. When the requested time range of the upstream analysis is different from the analysis step time of the downstream analysis, you can scale time such that the requested upstream analysis range is mapped over the entire downstream analysis step. In this case you must provide an end time value explicitly.

EXTERNAL FIELD, FILE=file name, TYPE=TIME RANGE, TIME SCALING=ON, START TIME=start time, END TIME=end time

Typically, the source and target regions have different meshes. Fields are mapped conservatively between the source and target meshes, and Abaqus selects the most appropriate mapping algorithm based on the field properties. For most cases, the default settings for the mapping algorithm are adequate, but you can modify the mapper settings by specifying field mapper controls when importing distributions and initial conditions.

Missing members might be reported during the mapping operation. Missing members are nodes or elements for which the mapper cannot find a correspondence between source and target meshes. Consequently, the mapper does not compute field values at these locations. In this case, you can modify the default search tolerances or specify how to treat missing members. A zero value is applied automatically for missing members when importing history-dependent flux quantities (that is, forces, pressure, tractions, and heat fluxes) and no treatment is required.

FIELD MAPPER CONTROLS, NAME=field mapper controls name
EXTERNAL FIELD, FILE=file name
 , , , , , , field mapper controls name

You can apply one or more field operations when importing fields.

You can scale a field by a constant value by providing a scale factor. The scaling factor is intended to scale a field by a physical constant. It is not intended for unit conversion; for example, where you might need additional parameters to convert a temperature field.

You can extract a component of a vector or tensor field by providing a component index, i. The i^th component of the source vector or tensor field is extracted and then mapped and imported as a scalar field. The components are extracted in the local coordinate system of the source field. You can apply component extraction when importing distributions, initial conditions, and history-dependent fields; it cannot be used for a submodel analysis.

If a region in the previous analysis is not colocated with the region in the current analysis, you must specify the translation and rotation to reposition the source region before field values are imported. You specify a rotation by giving two points, a and b, to define a rotation axis and a right-handed angular rotation about the axis. Local coordinate systems defined within the source region are translated and rotated according to the specified positioning data.

FIELD OPERATIONS, NAME=name, SCALE FACTOR=scale factor
EXTERNAL FIELD, FILE=file name
 , , , , , , , field operation name

FIELD OPERATIONS, NAME=name, COMPONENT=index
EXTERNAL FIELD, FILE=file name
 , , , , , , , field operation name

FIELD OPERATIONS, NAME=field operation name
x, y, z
x1, y1, z1, x2, y2, z2, rotation
EXTERNAL FIELD, FILE=file name
 , , , , , , , field operation name