Abaqus to OptiStruct Conversion Mapping

The Abaqus to OptiStruct conversion uses an open conversion scheme; you can specify different mappings in the configuration file.

Care has to be taken so that the element and property mappings are consistent. A valid mapping scheme is provided in the ConfigurationFile.txt file. This document explains the scope and limitations of the mapping scheme.

Contact and Pretension Groups

  • Contacts
    • NLPARM card is automatically created and assigned to a nonlinear quasi-static subcase for models containing contacts.
    • *SURFACE INTERACTION property with clearance/pressure vs conductivity is mapped to PCONTHT with TABLED1 cards.
    • *MODELCHANGE conversion is supported for both element set and contact group.
    • *CONTACT PAIR will be mapped to FINITE when SMALL SLIDING is not defined.
    • *CONTACT PAIR will be mapped to its default (SLIDE) when SMALL SLIDING is defined.
    • *CONTACT CONTROLS are converted to CNTSTB and is mapped to loadstep.
  • Bolt Pretension
    • *PRETENSION SECTION group maps to a PRETENS entity set with reference to a 1D pretension element or a 3D pretension surface (SURF).
    • *CLOAD applied to a pretension node converts to PTFORCE.
    • *BOUNDARY applied to a pretension node converts to PTADJST.
    • *BOUNDARY, FIXED option in step converts to STATSUB(PRETENS) on a preceding pretension subcase.
Table 1. Supported Contact and Pretension Group Mappings
Abaqus type HM config, OptiStruct type
*SURFACE (node based) set, SET
*SURFACE (element based) contact surface, SURF
*CONTACT PAIR group, CONTACT
*TIE group, TIE
*TIE (1D) group, TIE(N2N)
*PRETENSION SECTION set, PRETENS

contact surface, SURF

*SURFACE INTERACTION, Separation, No/Yes Property ,PCONT, Separation, No/Yes
*CONTACT CONTROLS Load collector, CNTSTB
*MODEL CHANGE MODCHG
* RIGID BODY rbody, RBODY
*SHELL TO SOLID COUPLING Group, TIE

Elements

HyperMesh elements have two basic attributes – configuration (or config) and type. The "config" defines the basic geometrical shape of an element. For example, tria3 configuration is a 3 node triangular element and hexa8 is an 8-node hexahedral element. The "type" defines the solver specific element type of a particular configuration. For example, the 4-node quadrilateral (quad4) element in Abaqus can be any of the following types: S4, S4R, M3D4, R3D4, and so on. The Element Types panel shows all supported element configurations and their types for a user profile.

For a specific configuration, you can map any supported Abaqus element type to any supported OptiStruct element type, or vice versa. For example, for an Abaqus to OptiStruct direction, several 2-noded element configurations such as spring, rigid, bar2, rid, and so on, are supported. Because all of them are 2-noded elements, conversion across these configurations is also allowed for some element types. For example, CBUSH is of "spring" configuration in the OptiStruct user profile and CONN3D2 is of "rod" configuration in the Abaqus user profile. It is possible to map a CBUSH to CONN3D2 even though their configurations are different. The element mapping scheme must be under the *ElemTypeConversion block in the ConfigurationFile.txt file. You need to provide both configuration and type information to specify the element mapping scheme.
Table 2. Supported Element Mappings
HM configuration Abaqus OptiStruct type
Mass MASS CONM2
ROTARYI CONM2
SPRING1 CELAS1, CELAS2, CBUSH
DASHPOT1 CDAMP1
CONN3D2 CBUSH
CONN2D2 CBUSH
rigid BEAM RBE2
LINK RBE2
PIN RBE2
TIE RBE2
KINCOUP RBE2
COUP_KIN RBE2
COUP_DIS RBE2
RB3D2 RBE2
R2D2 RBE2
RAX2 RBE2
RB2D2 RBE2
rbe3 DCOUP3D RBE3
COUP_DIS RBE3
DCOUP2D RBE3
rigidlink KINCOUP RBE2
RB3D2 RBE2
BEAM RBE2
LINK RBE2
PIN RBE2
TIE RBE2
COUP_KIN RBE2
COUP_DIS RBE3
R2D2 RBE2
RAX2 RBE2
RB2D2 RBE2
spring SPRING2 CELAS1, CBUSH
SPRINGA CBUSH
DASHPOT2 CDAMP1, CBUSH
DASHPOTA CBUSH
JOINTC CBUSH
bar2 B31 CBAR,CBEAM
B31H CBAR,CBEAM
B33 CBAR,CBEAM
B33H CBAR,CBEAM
B31OS CBAR,CBEAM
B31OSH CBAR,CBEAM
PIPE31 CBAR,CBEAM
PIPE31H CBAR,CBEAM
ELBOW31 CBAR,CBEAM
ELBOW31B CBAR,CBEAM
ELBOW31C CBAR,CBEAM
AC1D2 CBAR,CBEAM
GK3D2 CBAR,CBEAM
GK3D2N CBAR,CBEAM
SAX1 CBAR,CBEAM
B21 CBAR,CBEAM
B21H CBAR,CBEAM
B23 CBAR,CBEAM
B23H CBAR,CBEAM
PIPE21 CBAR,CBEAM
PIPE21H CBAR,CBEAM
F2D2 CBAR,CBEAM
FAX2 CBAR,CBEAM
bar3 B32 CBAR,CBEAM
B32H CBAR,CBEAM
B32OS CBAR,CBEAM
B32OSH CBAR,CBEAM
PIPE32 CBAR,CBEAM
PIPE32H CBAR,CBEAM
ELBOW32 CBAR,CBEAM
AC1D3 CBAR,CBEAM
MGAX2 CBAR,CBEAM
SFMAX2 CBAR,CBEAM
SFMGAX2 CBAR,CBEAM
SAX2 CBAR,CBEAM
B22 CBAR,CBEAM
B22H CBAR,CBEAM
PIPE22 CBAR,CBEAM
PIPE22H CBAR,CBEAM
rod T3D2 CROD
T3D2H CROD
T3D2T CROD
T3D2E CROD
MGAX1 CROD
SFMAX1 CROD
SFMGAX1 CROD
CONN3D2 CBUSH
T2D2 CROD
T2D2H CROD
T2D2T CROD
T2D2E CROD
GK2D2 CROD
GK2D2N CROD
CONN2D2 spring CELAS1,CELAS2,CBUSH
gap GAPUNI CGAP
GAPCYL CGAP
GAPSPHER CGAP
tria3 S3 CTRIA3,CTRIAR
S3R CTRIA3,CTRIAR
STRI3 CTRIA3,CTRIAR
M3D3 CTRIA3,CTRIAR
SFM3D3 CTRIA3,CTRIAR
R3D3 CTRIA3,CTRIAR
DS3 CTRIA3,CTRIAR
CPE3 CTRIA3,CTRIAR
CPE3H CTRIA3,CTRIAR
CPE3E CTRIA3,CTRIAR
CPS3 CTRIA3,CTRIAR
CPS3E CTRIA3,CTRIAR
CAX3 CTRIA3,CTRIAR
CAX3H CTRIA3,CTRIAR
CAX3E CTRIA3,CTRIAR
CGAX3 CTRIA3,CTRIAR
CGAX3H CTRIA3,CTRIAR
AC2D3 CTRIA3,CTRIAR
ACAX3 CTRIA3,CTRIAR
DCAX3 CTRIA3,CTRIAR
DCAX3E CTRIA3,CTRIAR
DC2D3 CTRIA3,CTRIAR
DC2D3E CTRIA3,CTRIAR
quad4 S4 CQUAD4,CQUADR
S4R CQUAD4,CQUADR
S4R5 CQUAD4,CQUADR
M3D4 CQUAD4,CQUADR
M3D4R CQUAD4,CQUADR
SFM3D4 CQUAD4,CQUADR
SFM3D4R CQUAD4,CQUADR
R3D4 CQUAD4,CQUADR
DS4 CQUAD4,CQUADR
GK3D4L CQUAD4,CQUADR
GK3D4LN CQUAD4,CQUADR
F3D4 CQUAD4,CQUADR
CPE4I CQUAD4,CQUADR
CPE4 CQUAD4,CQUADR
CPE4H CQUAD4,CQUADR
CPE4IH CQUAD4,CQUADR
CPE4R CQUAD4,CQUADR
CPE4RH CQUAD4,CQUADR
CPE4T CQUAD4,CQUADR
CPE4HT CQUAD4,CQUADR
CPE4E CQUAD4,CQUADR
CPS4 CQUAD4,CQUADR
CPS4I CQUAD4,CQUADR
CPS4R CQUAD4,CQUADR
CPS4T CQUAD4,CQUADR
CPS4E CQUAD4,CQUADR
CAX4 CQUAD4,CQUADR
CAX4H CQUAD4,CQUADR
CAX4I CQUAD4,CQUADR
CAX4IH CQUAD4,CQUADR
CAX4R CQUAD4,CQUADR
CAX4RH CQUAD4,CQUADR
CAX4T CQUAD4,CQUADR
CAX4HT CQUAD4,CQUADR
CAX4E CQUAD4,CQUADR
CAXA4N CQUAD4,CQUADR
CAXA4HN CQUAD4,CQUADR
CAXA4RN CQUAD4,CQUADR
CAXA4RHN CQUAD4,CQUADR
CGAX4 CQUAD4,CQUADR
CGAX4H CQUAD4,CQUADR
CGAX4R CQUAD4,CQUADR
CGAX4RH CQUAD4,CQUADR
AC2D4 CQUAD4,CQUADR
ACAX4 CQUAD4,CQUADR
DC2D4 CQUAD4,CQUADR
DC2D4E CQUAD4,CQUADR
DCAX4 CQUAD4,CQUADR
DCAX4E CQUAD4,CQUADR
DCCAX4 CQUAD4,CQUADR
DCCAX4D CQUAD4,CQUADR
GKPS4 CQUAD4,CQUADR
GKPE4 CQUAD4,CQUADR
GKPS4N CQUAD4,CQUADR
tria6 STRI65 CTRIA6
M3D6 CTRIA6
SFM3D6 CTRIA6
DS6 CTRIA6
CPE6 CTRIA6
CPE6H CTRIA6
CPE6M CTRIA6
CPE6MH CTRIA6
CPS6 CTRIA6
CPS6M CTRIA6
AC2D6 CTRIA6
ACAX6 CTRIA6
DCAX6 CTRIA6
DC2D6 CTRIA6
DCAX6E CTRIA6
DC2D6E CTRIA6
CAX6 CTRIA6
CAX6H CTRIA6
CAX6M CTRIA6
CAX6MH CTRIA6
CGAX6 CTRIA6
CGAX6H CTRIA6
quad8 S8R CQUAD8
S8R5 CQUAD8
S8RT CQUAD8
M3D8 CQUAD8
M3D8R CQUAD8
SFM3D8 CQUAD8
SFM3D8R CQUAD8
DS8 CQUAD8
CPE8 CQUAD8
CPE8H CQUAD8
CPE8R CQUAD8
CPE8RH CQUAD8
CPS8 CQUAD8
CPS8R CQUAD8
AC2D8 CQUAD8
ACAX8 CQUAD8
DC2D8 CQUAD8
DCAX8 CQUAD8
DCAX8E CQUAD8
DC2D8E CQUAD8
CAX8 CQUAD8
CAX8H CQUAD8
CAX8HT CQUAD8
CAX8R CQUAD8
CAX8RH CQUAD8
CAX8RHT CQUAD8
CAX8RT CQUAD8
CGAX8 CQUAD8
CGAX8H CQUAD8
CGAX8R CQUAD8
CGAX8RH CQUAD8
CAXA8N CQUAD8
CAXA8HN CQUAD8
CAXA8PN CQUAD8
CAXA8RN CQUAD8
CAXA8RHN CQUAD8
CAXA8RPN CQUAD8
tetra4 C3D4 CTETRA
C3D4H CTETRA
C3D4E CTETRA
AC3D4 CTETRA
DC3D4 CTETRA
DC3D4E CTETRA
C3D4T CTETRA
penta6 AC3D6 CPENTA
C3D6 CPENTA
C3D6H CPENTA
DC3D6 CGASK6
DC3D6E CGASK6
GK3D6 CPENTA
GK3D6N CPENTA
SC6R CPENTA
COH3D6 CPENTA
hex8 C3D8I CHEXA
C3D8 CHEXA
C3D8T CHEXA
C3D8H CHEXA
C3D8HT CHEXA
C3D8IH CHEXA
C3D8R CHEXA
C3D8RH CHEXA
C3D8E CHEXA
AC3D8 CHEXA
DC3D8 CHEXA
DC3D8E CHEXA
DCC3D8 CHEXA
DCC3D8D CHEXA
GK3D8 CGASK8
GK3D8N CGASK8
SC8R CHEXA
COH3D8 CHEXA
tetra10 C3D10 DC3D10
C3D10H DC3D11
C3D10M DC3D12
C3D10MH DC3D13
C3D10E DC3D14
DC3D10E DC3D15
AC3D10 DC3D16
DC3D10 DC3D17
penta15 C3D15H CPENTA
C3D15E CPENTA
AC3D15 CPENTA
DC3D15 CPENTA
DC3D15E CPENTA
hex20 C3D20 CHEXA
C3D20H CHEXA
C3D20R CHEXA
C3D20RH CHEXA
C3D20E CHEXA
C3D20RE CHEXA
C3D20T CHEXA
C3D20HT CHEXA
C3D20RT CHEXA
C3D20RHT CHEXA5
DC3D20 CHEXA
AC3D20 CHEXA
DC3D20E CHEXA
Pyramid C3D8I CPYRA
Abaqus CONN3D2 connector C3D20R elements are converted to OptiStruct CBUSH, PBUSH or JOINTG using the following guidelines:
  • Connector1 types converted:
    • AXIAL: Active = [1], Rigid = [-]
    • CARTESIAN, PROJECTION CARTESIAN: Active = [123], Rigid = [-]
    • JOIN: Active = [-], Rigid = [123]
    • RADIAL-THRUST: Active = [13]*, Rigid = [-]
      Note: Requires cylindrical system
    • SLIDE-PLANE: Active = [23], Rigid = [1]
    • SLOT: Active = [1], Rigid = [23]
  • Connector2 types converted:
    • ALIGN: Active = [-], Rigid = [456]
    • CARDAN, EULER, ROTATION, FLEXION-TORSION, PROJECTION FLEXION-TORSION: Active = [456], Rigid = [-]
    • REVOLUTE: Active = [4], Rigid = [56]
  • Special assembled Connector1 types:
    • BEAM, WELD = (JOIN + ALIGN): Active = [-], Rigid = [123456]
    • CYLINDRICAL = (SLOT + REVOLUTE): Active = [14], Rigid = [2356]
    • HINGE = (JOIN + REVOLUTE): Active = [4], Rigid = [12356]
    • PLANAR = (SLIDE-PLANE + REVOLUTE): Active = [234], Rigid = [156]
    • TRANSLATOR = (SLOT + ALIGN): Active = [1], Rigid = [23456]
    • BUSHING = (PROJECTION CARTESIAN + PROJECTION FLEXION-TORSION): Active = [123456], Rigid = [-]
  • PBUSH stiffness and damping values (Ki, Bi) for active DOFs are mapped from *CONNECTOR BEHAVIOR material data. Rigid DOFs map to RIGID option inside PBUSH.
  • CBUSH orientation is mapped from *CONNECTOR SECTION Orientation system.
    • Only 1 Orientation system can be mapped to CBUSH CID.
    • If 2 Orientation systems are present in the Abaqus card, HyperMesh only maps the first one.

It is possible to use a simplified conversion of Abaqus connectors (CONN3D2) to rbe2 elements when modifying ConfigurationFile.txt in the following way (change the entry for rod element type configuration: rod,CONN3D2 rigid,rbe2

CONN3D2 elements will now be converted to RBE2 elements. Depending on the connection type set in the CONNECTOR SECTION (such as AXIAL or HINGE), degrees of freedom will be set for the RBE2 element. If systems are associated to the connector elemental nodes they will be assigned to the nodes of the RBE2 as well. Not all connection types are supported. If a system is ignored by a particular CONNECTOR SECTION, it will not be assigned to the nodes of the RBE2 either.

These connector types are currently considered in conversion: AXIAL, JOIN, LINK, SLIDE-PLANE, SLOT, ALIGN, REVOLUTE, BEAM, CYLINDRICAL, HINGE, PLANAR, TRANSLATOR, WELD.

*KINEMATIC COUPLING constraints with element based surfaces (currently mapped to groups in HyperMesh) are converted into RBE2 rigid elements. *DISTRIBUTING COUPLING constraints are converted to RBE3 elements.

All SPRING and DASHPOT related conversions (including JOINTC) map to CELAS1, CDAMP1, or CBUSH/PBUSH using the following guidelines:
  • SPRING1/2 without ORIENTATION converts to CELAS1
  • SPRINGA or SPRING1/2 with ORIENTATION converts to CBUSH/PBUSH/PBUSHT with K/KN lines. For SPRING1/2, ORIENTATION maps to CBUSH, CID.
  • DASHPOT1/2 without ORIENTATION converts to CDAMP1
  • DASHPOTA or DASHPOT1/2 with ORIENTATION converts to CBUSH/PBUSH/PBUSHT with B line. For DASHPOT1/2, ORIENTATION maps to CBUSH, CID.
  • Convertor has an additional option: Convert *SPRING defined with Orientation to CBUSH. If this option is enabled, *SPRING is converted to CBUSH if not enabled to CELAS.
Refer to the following table for Connector Section values:
Connector Section Values
AXIAL AXIAL
AXIAL ALIGN AXIAORIE
AXIAL, ALIGN AXIAL, ORIENT
BEAM (JOIN + ALIGN) BALL + ORIENT OR CBUSH, Pbush (RIGID all)
LINK RROD
LINK ALIGN RLINORIE
LINK, ALIGN RROD, ORIENT
JOIN BALL
JOIN, ROTATION BALL, CARDAN
HINGE (JOIN + REVOLUTE) REVOLUTE, BALL
SLOT INLINE
SLOT CARDEN INLICARD
CYLINDRICAL (SLOT + REVOLUTE) INLINE + REVOLUTE
TRANSLATOR (SLOT + ALGIN) INLINE, ORIENT
CARTESIAN CARTESIAN
SLIDE-PLANE INLINE
UJOINT (JOIN + UNIVERSAL) BALL, UNIVERSAL
HINGE RBAR + REVOLUTE

Nodal thickness is mapped to respective grid post conversions.

HTML report supported for Joints.

Configuration file paths are selected in batch mode conversion. Conversion options can be used in batch mode conversion by editing the configuration file.

Sectional Properties

Some of the properties in one solver can be converted to two different sections in the other solver. For an Abaqus to OptiStruct conversion, for example, *DASHPOT can be converted to *PELAS or PDAMP. The property mapping scheme can be edited under the *PropertyConversion block in the ConfigurationFile.txt file.

The property conversion scheme and corresponding element conversion scheme must be consistent. For example, if you define *CONNECTOR SECTION to PBUSH at the property mapping scheme, the corresponding element CONN3D2 must map to CBUSH in the element mapping scheme.

For SOLID SECTION the converter will always convert to PSOLID unless the property has a data line indicating a cross-sectional area for a truss element. In this case conversion results in a PROD property.

For BEAM (GENERAL) SECTION the algorithm automatically decides which property to convert to depending on the element type chosen in the ElementTypeConversion section of the ConfigurationFile.txt. For example, if you want to convert B31 elements to CBAR, the beam property will get converted to a PBAR or PBARL property. If you choose to convert B31 elements to CBEAM, then the converter creates PBEAM or PBEAML properties accordingly. The same logic applies to B32 elements; the difference is that they are changed to first order beam elements first on conversion.

Table 3. Supported Sectional Property Mappings
Abaqus type OptiStruct type
*SURFACE INTERACTION PCONT
*SURFACE BEHAVIOR, PRESSURE -OVERCLOSURE = EXPONENTIAL PCONT SOFT YES + STFEXP
*FRICTION PCONT
*GASKET SECTION PGASK
*BEAM GENERAL SECTION PBAR(L), PBEAM(L)
*BEAM SECTION PBAR(L), PBEAM(L)
*CONNECTOR SECTION JOINTG
*CONNECTOR SECTION-JOIN JOINTG-BALL
*CONNECTOR SECTION-REVOLUTE JOINTG-REVOLUTE
*CONNECTOR SECTION-UNIVERSAL JOINTG-UNIVERSAL
*DASHPOT PELAS,PDAMP
*GAP PGAP
*MASS CONM2
*MEMBRANE SECTION PSHELL
*ROTARY INERTIA CONM2
*SHELL GENERAL SECTION PSHELL
*SHELL GENERAL SECTION PSHELL
*SHELL SECTION PSHELL
*SOLID SECTION PSOLID
*SPRING PELAS, PBUSH, PBUSHT
*SOLID SECTION (Homogeneous) PROD
*SHELL GENERAL SECTION (Homogeneous) PSHELL
*SHELL GENERAL SECTION (User) PSHELL
*SHELL SECTION (Composite) PCOMP, PCOMPG
*SHELL SECTION COMPOSITE Property, PCOMPLS
*SHELL GENERAL SECTION (Composite) PCOMP, PCOMPG

Materials

The material mapping scheme can be edited under *PropertyConversion block in the ConfigurationFile.txt file.
Table 4. Supported Material Mappings
Abaqus type OptiStruct type
*MATERIAL *ELASTIC, ISOTROPIC MAT1
*ELASTIC, ISOTROPIC

E, poisson's ratio, T

MATT1 with TABLEM1 for E and poisson's ratio
*ELASTIC, LAMINA MAT8
*PLASTIC

stress (x), plastic strain (y)

MATS1 with TYPSTRN=1 for plastic strain.

TABLES1 with stress (y) vs plastic strain (x)

*PLASTIC

stress (x), plastic strain (y), Temp

For each T, need a separate TABLES1.

TABLEST to define T and corresponding TABLES1.

*SPECIFIC HEAT MAT4, CP
*CONDUCTIVITY MAT4, K
*EXPANSION

expansion coeff, T

MATT1 with TABLEM1 for expansion coeff (A)
*GASKET BEHAVIOR *GASKET ELASTICITY, COMPONENT = MEMBRANE MGASK + MAT1
*GASKET ELASTICITY,

COMPONENT = TRANSVERSE SHEAR

MGASK + MAT1

GPL field of MGASK card

*GASKET THICKNESS BEHAVIOR, DIRECTION = LOADING

pressure (x), closure (y)

TABLES1 curve with pressure (y) vs closure (x) definition

TABLES1 referred in TABLED field of MGASK

*GASKET THICKNESS BEHAVIOR, DIRECTION = LOADING for TYPE = ELASTO-PLASTIC BEHAV = 0 in MGASK
*GASKET THICKNESS BEHAVIOR, DIRECTION = LOADING for TYPE = DAMAGE BEHAV = 1 in MGASK
*GASKET THICKNESS BEHAVIOR, DIRECTION=LOADING for TYPE = DAMAGE or ELASTO-PLASTIC with TENSILE STIFFNESS FACTOR EPL in MGASK
*GASKET THICKNESS BEHAVIOR, DIRECTION = UNLOADING

pressure, closure, Max closure

For "n" max/plastic closure values, creates "n" TABLES1 for individual unloading pressure vs closure curves.

TABLES1 referred in TABLU1

TABLUn fields in MGASK.

*EXPANSION

expansion coeff, T

 
*MATERIAL *CONDUCTIVITY MATT4,TABLEM1
*MATERIAL *HYPERELASTIC, MOONEY, RIVLIN, REDUCED, POLYNOMIAL, ARRUDA, BOYCE, YEOH, NEO HOOKE MATHE, MOONEY, RIVLIN, REDUCED, POLYNOMIAL, ARRUDA, BOYCE, YEOH, NEO HOOKE
*MATERIAL MATERIAL
*CREEP MATVP
*VISCOELASTIC MATVE
*ELASTIC, TYPE = ENGINEERING CONSTANTS MAT9ORT
*CONNECTOR BEHAVIOR PBUSH, PELAS

Loads

HM loads have two basic attributes – configuration (or config) and type. The supported load "configs" are: force, moment, constraint, pressure, temperature, flux, velocity, acceleration and equation. The load "type" defines the solver specific type of a particular configuration. For example, pressure load can be any of the following OptiStruct types: PLOAD, PLOAD2, or PLOAD4. The Load Types panel shows all supported load configurations and their types for a user profile.

The converter also converts distributed surfaces loads (*DLSOAD) applied on faces of shell or solid elements into pressure loads (PLOAD4).

Temperature with *INTIAL condition is converted to TEMP(INTIAL) and mapped to Global Case Control.

FILM loads are converted to CHBDYE elements, sink temperatures are converted to SPC and heat transfer coefficient(H) with PCONV.

SFILM loads are converted to CHBDYE elements, sink temperatures are converted to SPC and heat transfer coefficient(H) with PCONV.

Distributed surfaces loads (*DLSOAD) applied on faces of shell or solid elements into pressure loads (PLOAD4).

For a specific configuration, you can map any supported Abaqus load type to any supported OptiStruct load type. The conversion tool does not support conversion across load configurations. The load mapping scheme can be edited under the *BCsTypeConversion block in the ConfigurationFile.txt file. You need to provide both configuration and type information to specify the mapping scheme.

Abaqus *connector behavior STOP/LOCK with Elastic/Non-linear/RIGID convert to PJOINTG with STOP/LOCK with ELAS/NLELAS/RIGID.

Table 5. Supported Load Mappings
HM configuration Abaqus type OptiStruct type
temperature TEMPERATURE TEMP
pressure DLOAD PLOAD,PLOAD2,PLOAD4
pressure DLOAD, ROTA RACC
pressure CENTRIFUGAL RFORCE
pressure FILM SPC
SFILM SPC
DFLUX QBDY1
Constraint ACCELERATION SPCD
VELOCITY SPCD
BOUNDARY SPC,SUPORT
BOUNDARY on pretension node PTADJST
moment CLOAD MOMENT
force CLOAD FORCE
CLOAD on pretension node PTFORCE
equation EQUATION MPC
temperature BOUNDARY SPC
Connector Load CONNECTOR LOAD LOADJG
Connector Motion CONNECTOR MOTION MOTIONJG

Sets

Table 6. Supported Set Mappings
Abaqus type OptiStruct type
*NSET SET
*ELSET SET

Control Cards

  • Node set and element set from output block for displacement and stress are mapped.
  • PARAM, INREL, -2 is created if there is *INERTIA RELIEF in the OptiStruct deck.
  • PARAM, RBE3COL is created if there are rbe3 elements in the OptiStruct deck.

Systems

Table 7. Supported System Mappings
Abaqus type OptiStruct type
*ORIENTATION CORD2C,CORD2R,CORD2S
*SYSTEM CORD2C,CORD2R,CORD2S
*TRANSFORM CORD2C,CORD2R,CORD2S
*TRANSFORM- USER DEFINED NSET CORD2C,CORD2R,CORD2S

Control Cards

Displacement, Stress and Contact pressure output card is created on conversion and is mapped to respective loadstep.

Node set and element set from output block for displacement and stress are mapped if mapped to step.

PARAM,INREL,-2 is created if there is *INERTIA RELIEF in the Abaqus deck.

PARAM,RBE3COL is created if there are rbe3 elements in the Abaqus deck.

*PREPRINT,CONTACT=YES to OptiStruct CONTPRM,PREPRT,YES.

If OUTPUTBLOCK is not mapped to any loadstep these are updated in GLOBAL CASE CONTROL.

*RESTART,WRITE,OVRELAY is converted to OS RESTARTW= 1 ,COVER

Load Steps and Analysis Type

The conversion tool maps between Abaqus steps and OptiStruct subcases. It does not convert Abaqus analysis types to the solution type. You must define it manually using the Loadsteps Browser.

The converter converts *STEP into respective supported SUBCASE. Load collector references are maintained upon conversion. If multiple load collectors of a particular step have constraints, an SPCADD card is created automatically. Similarly, a LOAD card is created for homogeneous loads and mapped to step.

For models containing contacts, NLPARM card is automatically created and assigned to a nonlinear quasi-static subcase.

Abaqus models that contain both conductivity and temperature defined under *CONDUCTIVITY in *MATERIAL is converted to a non-linear Heat transfer (NLHEAT) analysis type in OptiStruct.

NLGEOM is set to YES in a loadstep with id 'i', CNTNLSUB will be set checked on, OPTION set to YES and SCID points to the previous loadstep in loadstep with id 'i+1'. The chain continues for the loadsteps.

*PERTURBUTION steps are converted to linear static.

*FREQUENCY RESIDUAL=YES is converted to RESVEC=YES on conversion.

*FREQUENCY (analysis type) is converted to normal modes with the EIGRL card (load collector) mapped in the loadstep on conversion.

*SELECTEIGENMODES converted OptiStruct MODESELECT.

SUBCASE (MONITOR) converted to MONITOR and updated in the Loadstep.

*STATIC load step wuth Int_INC is mapped to NLPARM load collector with NINC=1/Int_INC.

*STATIC load step with MinIcr is mapped to NLADAPT,DTMIN load collector.

*STATIC load step with MaxIncr is mapped to NLADAPT,DTMAX load collector.

*STEP with unsymm=yes is converted to PARAM, UNSYMSLV.

*ENDLOADCASE conversion supported.

Dynamic NLGEOM=yes to Transient Nonlinear analysis.