Files
김경종 b7f84e1c0f
Tests / Hermetic test suite (push) Has been cancelled
Tests / Skill frontmatter validation (push) Has been cancelled
add documents
2026-05-29 15:59:56 +09:00

241 lines
17 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<!-- source-page: 491 -->
# 3.2.34 TRANSLATING RADIOSS INPUT FILES TO PARTIAL Abaqus INPUT FILES
Product: Abaqus/Explicit
# Reference
• “Execution procedure for Abaqus: overview,” Section 3.1.1
# Overview
The translator from RADIOSS to Abaqus converts certain keywords in a RADIOSS input file into their equivalent in Abaqus/Explicit.
# Using the translator
The translator requires an input file in block format created by RADIOSS Version 4.4 or 5.1. The input file can have any name and an optional extension.
The RADIOSS data entries that are translated are listed in the tables below. Other RADIOSS keywords and data are skipped over and noted in the log file.
The translator creates a partial Abaqus input file that contains only the model data and time history output data. You can provide additional output data to complete the input.
# Element numbering and grouping
All elements in the generated Abaqus input file will have unique element numbers. New element numbers will be assigned automatically to elements with non-unique element numbers in the RADIOSS input. Elements that are assigned the same PART identification number are grouped together in an element set.
Elements that have different material or properties must be given different PART identification numbers; that is, the same material and properties must be applicable to all elements grouped in the same element set.
If elements that result from the translation of SPRING have different element properties (such as skew systems used to define local directions) and are assigned the same PART identification number, the translator automatically separates them into different element sets.
# Material models
The translator supports only the material models shown in Table 3.2.341. All unsupported material models are translated as linear elastic if a stress-strain law definition is required. In these cases the translator provides nominal values for the material properties.
<!-- source-page: 492 -->
Table 3.2.341 Material data.
<table><tr><td>RADIOSS keyword</td><td>Abaqus equivalent</td></tr><tr><td>MAT / LAW01 (ELAST)</td><td>*ELASTIC</td></tr><tr><td>MAT / LAW02 (PLAS_JOHN)</td><td>*PLASTIC, HARDENING=JOHNSON COOK</td></tr><tr><td>MAT / LAW03 (HYDPLA)</td><td>*EOS, *TENSILE FAILURE, *DAMAGE INITIATION, and *DAMAGE EVOLUTION</td></tr><tr><td>MAT / LAW19 (FABRI)</td><td>*USER MATERIAL</td></tr><tr><td>MAT / LAW22 (DAMA)</td><td>*PLASTIC, HARDENING=JOHNSON COOK; *RATE DEPENDENT, TYPE=JOHNSON COOK; *DAMAGE INITIATION; and *DAMAGE EVOLUTION</td></tr><tr><td>MAT / LAW35 (FOAM_VISC)</td><td>*HYPERFOAM and *VISCOELASTIC</td></tr><tr><td>MAT / LAW36 (PLAS_TAB)</td><td>*PLASTIC, HARDENING=ISOTROPIC</td></tr></table>
Table 3.2.342 Property data.
<table><tr><td>RADIOSS keyword</td><td>Abaqus equivalent</td></tr><tr><td>PROP / TRUS</td><td>Truss element properties and grouping data</td></tr><tr><td>PROP / BEAM</td><td>Beam element properties and grouping data</td></tr><tr><td>PROP / SPRING</td><td>Connector behavior and grouping data</td></tr><tr><td>PROP / SPR_BEAM</td><td>Connector behavior and grouping data</td></tr><tr><td>PROP / SPR_GENE</td><td>Connector behavior and grouping data</td></tr><tr><td>PROP / SOLID</td><td>Solid element properties and grouping data</td></tr><tr><td>PROP / SOL_ORTH</td><td>Solid element properties and grouping data</td></tr><tr><td>PROP / SHELL</td><td>Shell element properties and grouping data</td></tr><tr><td>PROP / SH_ORTH</td><td>Shell element properties and grouping data</td></tr></table>
Table 3.2.343 Nodal data.
<table><tr><td>RADIOSS keyword</td><td>Abaqus equivalent</td></tr><tr><td>NODE</td><td>*NODE</td></tr><tr><td>ADMAS</td><td>*MASS and *ROTARY INERTIA</td></tr></table>
<!-- source-page: 493 -->
<table><tr><td>RADIOSS keyword</td><td>Abaqus equivalent</td></tr><tr><td>BCS</td><td>*BOUNDARY</td></tr><tr><td>IMPDISP</td><td>*BOUNDARY and *AMPLITUDE</td></tr><tr><td>IMPVEL</td><td>*BOUNDARY and *AMPLITUDE</td></tr><tr><td>INIVEL</td><td>*INITIAL CONDITIONS, TYPE=VELOCITY or ROTATING VELOCITY</td></tr><tr><td>CLOAD</td><td>*CLOAD and *AMPLITUDE</td></tr><tr><td>GRAV</td><td>*DLOAD and *AMPLITUDE</td></tr><tr><td>SKEW</td><td>*ORIENTATION and *TRANSFORM</td></tr><tr><td>FRAME</td><td>*ORIENTATION and *TRANSFORM</td></tr></table>
Table 3.2.344 Element data.
<table><tr><td>RADIOSS keyword</td><td>Abaqus equivalent</td></tr><tr><td>BRICK</td><td>C3D4/C3D6/C3D8R and *SOLID SECTION</td></tr><tr><td> $SHELL^1$ </td><td>S3RS/S4RS and *SHELL SECTION; or M3D3/M3D4/M3D4R and *MEMBRANE SECTION</td></tr><tr><td> $SH3N^1$ </td><td>S3RS and *SHELL SECTION; or M3D3 and *MEMBRANE SECTION</td></tr><tr><td>BEAM</td><td>B31 and *BEAM SECTION, SECTION=CIRC</td></tr><tr><td>TRUSS</td><td>T3D2 and *SOLID SECTION</td></tr><tr><td>SPRING</td><td>CONN3D2 and *CONNECTOR SECTION</td></tr><tr><td colspan="2"> $^1$ Shell elements with one integration point through the thickness are translated as membrane elements.</td></tr></table>
Table 3.2.345 Constraint data.
<table><tr><td>RADIOSS keyword</td><td>Abaqus equivalent</td></tr><tr><td>RWALL</td><td>*RIGID BODY and *CONTACT</td></tr><tr><td>RBODY</td><td>*RIGID BODY and/or *MPC (type BEAM)To define an element as a rigid body, enter all the element node numbers in the node group associated with the rigid body.</td></tr></table>
<!-- source-page: 494 -->
<table><tr><td>RADIOSS keyword</td><td>Abaqus equivalent</td></tr><tr><td>INTER / Type 2</td><td>*TIE and *FASTENER</td></tr><tr><td>INTER / Types 7, 10, 11</td><td>*CONTACT, *CONTACT CONTROLS ASSIGNMENT, *CONTACT FORMULATION, *CONTACT INCLUSIONS, *CONTACT EXCLUSIONS, *CONTACT PROPERTY ASSIGNMENT, *SURFACE INTERACTION, and *SURFACE PROPERTY ASSIGNMENT</td></tr><tr><td>CYL_JOINT</td><td>CONN3D2 and *CONNECTOR SECTION</td></tr></table>
Table 3.2.346 Group data.
<table><tr><td>RADIOSS keyword</td><td>Abaqus equivalent</td></tr><tr><td>SUBSET</td><td>*ELSET; data for elements to be grouped in a set using *ELSET</td></tr><tr><td>PART</td><td>*ELSET; data for elements to be grouped in a set using *ELSET</td></tr><tr><td>MAT</td><td>*ELSET; data for elements to be grouped in a set using *ELSET</td></tr><tr><td>PROP</td><td>*ELSET; data for elements to be grouped in a set using *ELSET</td></tr><tr><td>NODE</td><td>*NSET; data for elements to be grouped in a set using *NSET</td></tr><tr><td>SH3N</td><td>*ELSET; data for elements to be grouped in a set using *ELSET</td></tr><tr><td>SHEL</td><td>*ELSET; data for elements to be grouped in a set using *ELSET</td></tr><tr><td>GRNOD</td><td>*NSET; data for elements to be grouped in a set using *NSET</td></tr><tr><td>GRSH3N</td><td>*ELSET; data for elements to be grouped in a set using *ELSET</td></tr><tr><td>GRSHEL</td><td>*ELSET; data for elements to be grouped in a set using *ELSET</td></tr><tr><td>GRSPRI</td><td>*ELSET; data for elements to be grouped in a set using *ELSET</td></tr><tr><td>GENE</td><td>*NSET; data for elements to be grouped in a set using *NSET</td></tr></table>
<!-- source-page: 495 -->
<table><tr><td>RADIOSS keyword</td><td>Abaqus equivalent</td></tr><tr><td>SEG</td><td>*ELSET; data for elements to be grouped in a set using *ELSET</td></tr><tr><td>SURF</td><td>*ELSET and *NSET</td></tr></table>
Table 3.2.347 Monitored volume and seat belt data.
<table><tr><td>RADIOSS keyword</td><td>Abaqus equivalent</td></tr><tr><td>MONVOL / GASMONVOL / AIRBAG</td><td>*FLUID BEHAVIOR, *FLUID CAVITY, *FLUID EXCHANGE, *FLUID EXCHANGE ACTIVATION,*FLUID EXCHANGE PROPERTY, *FLUID INFLATOR,*FLUID INFLATOR ACTIVATION, *FLUID INFLATOR MIXTURE, *FLUID INFLATOR PROPERTY,*MOLECULAR WEIGHT, *CAPACITY, and *PHYSICAL CONSTANTS</td></tr><tr><td>SPRING with property SPR_PUL</td><td>*ELEMENT, TYPE=CONN3D2; *CONNECTOR SECTION; and *BOUNDARY</td></tr></table>
Table 3.2.348 Miscellaneous data.
<table><tr><td>RADIOSS keyword</td><td>Abaqus equivalent</td></tr><tr><td>TITLE</td><td>*HEADING</td></tr><tr><td>ACCEL</td><td>CONN3D2 and connector type ACCELEROMETER</td></tr><tr><td>FUNCT</td><td>Data for material properties and time-dependent parameters, such as *AMPLITUDE, *CONNECTOR ELASTICITY, *PLASTIC, and *FLUID EXCHANGE PROPERTY</td></tr><tr><td>SECT</td><td>*INTEGRATED OUTPUT SECTION</td></tr><tr><td>SENSOR / Type 0</td><td>Use activation time in *AMPLITUDE</td></tr><tr><td>TH</td><td>Data for time history output, such as *OUTPUT, HISTORY; *NODE OUTPUT; *ELEMENT OUTPUT; and *ENERGY OUTPUT</td></tr></table>
# Command summary
abaqus fromradioss
job=job-name input=input-file
[splitAirbagElements={OFF | ON}]
[readAbaqusDat=data-file] [userDefaultMass=real-number]
[userDefaultInertia=real-number] [userHistoryTime=real-number]
<!-- source-page: 496 -->
# Command line options
# job
This option is used to specify the name of the Abaqus input file to be output by the translator. The name of the Abaqus input file must be given without the .inp extension. Diagnostics created by the translator are written to a file named job-name\_fromradioss.log.
# input
This option is used to specify the name of the file containing the RADIOSS data. The file extension is optional.
# splitAirbagElements
This option is used to specify the splitting of 4-node airbag membrane elements into two 3-node airbag membrane elements. The default value is ON. Airbag membrane elements result from the translation of SHELL or SH3N with one integration point through the thickness. This option is valid only if the keyword MONVOL/AIRBAG is specified in the RADIOSS input file.
# readAbaqusDat
This option enables the use of an Abaqus data (.dat) file from a previous Abaqus analysis to reformulate spot weld definitions. The data file should identify spot welds that could not be formed. Using this option, the attachment points for the identified spot welds are translated using distributed coupling constraints.
# userDefaultMass
This option is used to specify the nodal mass that is assigned to additional nodes generated during the translation that require nonzero mass. This value should be small (typically 106 times the mass for the entire model). If this option is omitted, the default mass is set to 104 .
# userDefaultInertia
This option is used to specify the rotary inertia that is assigned to additional nodes generated during the translation that require nonzero rotary inertia. This value should be small (typically 106 times the inertia for the entire model). If this option is omitted, the default rotary inertia is set to 103 .
# userHistoryTime
This option is used to specify the time interval used for time history output. If this option is omitted, the time history interval is set to 105 .
<!-- source-page: 497 -->
# 3.2.35 TRANSLATING Abaqus OUTPUT DATABASE FILES TO NASTRAN OUTPUT2 RESULTS FILES
Product: Abaqus/Standard
# Reference
• “Execution procedure for Abaqus: overview,” Section 3.1.1
# Overview
The translator converts certain results from an Abaqus output database (.odb) file to the Nastran Output2 file format.
# Using the translator
The toOutput2 translator can only be used to translate Abaqus output database of a \*STATIC or \*FREQUENCY procedure. Results from an Abaqus analysis are written to the Abaqus output database by using the \*OUTPUT option. The following options should be included in the Abaqus input file to ensure that the results to be translated are available in the Abaqus output database:
```csv
*OUTPUT, FIELD
*NODE OUTPUT
U,
RF,
CF,
*ELEMENT OUTPUT
S,
E,
SF,
NFORC,
```
Results in the Abaqus output database other than those specified above are skipped during translation. Only results from spring elements and three-dimensional continuum, shell, membrane, beam, and truss elements are translated.
For shell elements, the translator treats stresses and strains at the lowest numbered section point as being at the bottom surface and stresses and strains at the highest numbered section point as being at the top surface. Midsurface stresses and strains translated to the Output2 file are computed as the averages of the stresses and strains at the bottom and top surfaces.
Nodal results are always in global coordinates. Element tensor results are in the Abaqus element coordinate system.
Model data from the output database (nodal coordinates, element topology, material properties, and element properties) are written to the Output2 file when applicable records exist.
<!-- source-page: 498 -->
Command summary
<table><tr><td>abaqus toOutput2</td><td>job=job-name[odb=odb-name] [step=step-number][increment=increment-number] [slim] [quad4corner]</td></tr><tr><td colspan="2">Command line options</td></tr></table>
# job
This option specifies the name of the Nastran Output2 file to be created by the translator. It is also the default name for the Abaqus output database.
# odb
This option specifies the name of the Abaqus output database if it is different from job-name.
#
This option specifies the step number of the Abaqus output database for the translator to translate. If the specified step contains multiple load cases, all of the load cases are translated. The default value is the last step of the analysis.
# increment
This option is valid only when used in conjunction with the step option. It is used to specify the increment number of the step in the Abaqus output database for the translator to translate. The default value is the last increment of the specified step.
# slim
This option is used to include data blocks required for postprocessing in the SLIM/VISION software (available from Third Millennium Productions, Inc.) in the Output2 file.
# quad4corner
This option is used to request shell output at corner nodes instead of at the centroid. This option is relevant for stress, strain, and section force output.
<!-- source-page: 499 -->
# 3.2.36 TRANSLATING LS-DYNA DATA FILES TO Abaqus INPUT FILES
Product: Abaqus/Explicit
# Reference
• “Execution procedure for Abaqus: overview,” Section 3.1.1
# Overview
The translator from LS-DYNA to Abaqus converts a set of supported keywords in an LS-DYNA input file into their equivalent in Abaqus.
# Using the translator
The translator supports translation of input files created by LS-DYNA Version 971 Rev 5 or earlier. The input file can have any name and an optional extension.
The LS-DYNA keywords that are supported are listed in the tables below. Other LS-DYNA keywords and data are skipped over and noted in the log file.
The translator creates an Abaqus input file that contains both the model data and history data. However, the translator does not create exact Abaqus equivalents for specific output quantities for nodal output, element output, and contact output; it uses preselected variables instead. You can provide additional output entities to complete the requests.
# Element numbering and grouping
All elements in the generated Abaqus input file have unique element numbers. New element numbers are assigned automatically to elements with non-unique element numbers in the LS-DYNA input; all element number reassignments are noted in the log file.
Elements that are assigned the same PART identification number are grouped together in an element set. Elements that have different material or properties must be given different PART identification numbers; that is, the same material and properties must be applicable to all elements grouped in the same element set.
When a PART references a rigid material, the part is considered rigid. The element set that corresponds to the part is used in the rigid body definition.
# Material models
The translator supports only the material models shown in Table 3.2.361. All unsupported material models are translated as linear elastic if a stress-strain law definition is required. In these cases the translator provides nominal values for the material properties.
<!-- source-page: 500 -->
# Mapping LS-DYNA elements that end in \_ID or \_TITLE
Many LS-DYNA keywords include the options \_ID, \_TITLE, or both of these options. Unless the LS-DYNA keyword with \_ID or \_TITLE is specified in the mapping tables in this document, the translator maps data from these options to the same Abaqus keywords specified for the main LS-DYNA keyword.
# Summary of LS-DYNA entities translated
The translator from LS-DYNA to Abaqus supports the mappings shown in the tables below.
Table 3.2.361 Material data.
<table><tr><td>LS-DYNA Keyword</td><td>Abaqus Equivalent</td></tr><tr><td>*MAT_BLATZ-KO_RUBBER</td><td>*HYPERELASTIC, NEO HOOKE</td></tr><tr><td>*MAT_CABLE_DISCRETE_BEAM</td><td>*ELASTIC</td></tr><tr><td>*MAT_DAMPER_NONLINEAR_VISCOUS</td><td>*CONNECTOR DAMPING, NONLINEAR</td></tr><tr><td>*MAT_DAMPER_VISCOUS</td><td>*CONNECTOR DAMPING</td></tr><tr><td>*MAT_ELASTIC</td><td>*ELASTIC</td></tr><tr><td>*MAT_ELASTIC_PLASTIC_THERMAL</td><td>*ELASTIC*PLASTIC*EXPANSION</td></tr><tr><td>*MAT_FU_CHANG_FOAM</td><td>*LOW DENSITY FOAM and*UNIAXIAL TEST DATA</td></tr><tr><td>*MAT_HONEYCOMB</td><td>Built-in VUMATuser material modelABQ_HONEYCOMB1</td></tr><tr><td>*MAT_JOHNSON_COOK</td><td>*PLASTIC, HARDENING=JOHNSON COOK*RATE DEPENDENT, TYPE=JOHNSON COOK*SHEAR FAILURE, TYPE=JOHNSON COOK*TENSILE FAILURE, TYPE=JOHNSON COOK</td></tr><tr><td>*MAT_LINEAR_ELASTIC_DISCRETE_BEAM</td><td>*CONNECTOR ELASTICITY and*CONNECTOR DAMPING</td></tr><tr><td>*MAT_LOW_DENSITY_FOAM</td><td>*HYPERFOAM and *UNIAXIAL TEST DATA</td></tr></table>