HyperMesh and BatchMesher

Unsupported Cards by Solver

Unsupported Cards by Solver

Previous topic Next topic Expand/collapse all hidden text  

Unsupported Cards by Solver

Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function  
hmtoggle_arrow1RADIOSS

The following D00 cards are not supported for RADIOSS 5.1 and 9.0:

 

/ADMESH/STATE/SHELL

/ADMESH/STATE/SH3N

/ALE/CLOSE

/ANIM/VERS

/BCS/LAGMUL

/BEM/FLOW

/BOX

/BOX/BOX

/EBCS/MONVOL

/EULER/MAT

/EIG

/EOS/GRUNEISEN

/EOS/POLYNOMIAL

/EOS/TILLOTSON

/EXTERN/LINK

/FAIL/POWER_DAM

/FAIL/XFEM_FLD

/FAIL/XFEM_JOHNS

/FAIL/XFEM_TBUTC

/FXBODY

/GJOINT

/GAUGE

/IBVEL

/IMPLICIT

/INICONT

/INIVOL

/IMPVEL/LAGMUL

/INIBRI

/INIQUA

/INTER/HERTZ

/INTER/HERTZ/TYPE17

/INTER/LAGDT

/INTER/LAGDT/TYPE7

/INTER/LAGMUL/TYPE2

/INTER/LAGMUL/TYPE16

/INTER/LAGMUL/TYPE17

/KEY

/LAGMUL

/MADYMO/EXFEM

/MADYMO/LINK

/MPC

/PROP/TYPE25 (SPR_AXI)

/PROP/TYPE28 (NSTRAND)

/PROP/TYPE35 (STITCH)

/PROP/USER4

/RBODY/LAGMUL

/RWALL/LAGMUL

/SHEL16

/STATE/STR_FILE

/SUBMODEL

/SURF/MDELLIPS

/TH/FXBODY

/TH/GAUGE

/TH/NSTRAND

/TH/PART

/UNIT/name

/XELEM

/XREF

 

hmtoggle_arrow1OptiStruct, Nastran

This interface is the same for both Nastran and Radioss (Bulk), and can handle unsupported cards in several ways.  There are three basic types of unsupported cards: Fully unsupported cards, partially supported cards and forced unsupported cards.

Fully unsupported cards are read in and written out with the UNSUPPORTED_CARDS control card.  This is described in more detail below.
Partially unsupported cards are keywords that are recognized, but may have new or unrecognized fields within the card.  HyperMesh will read the card and all supported fields, but will ignore any unrecognized fields (meaning that unrecognized data will be lost).
Forced unsupported cards are manually added to the UNSUPPORTED_CARDS control card through the use of $HM_BEGIN_UNSUPPORTED and $HM_END_UNSUPPORTED HyperMesh comments in the input deck itself.  These are described in more detail below.

 

Unsupported Cards


Cards that are not recognized by the HyperMesh interface are automatically written into one of three [two for Radioss] control cards depending on where they exist within the input file.  They only receive simple supported as text, and are written in and out of the same section of the input file.

EXEC_UNSUPPORTED_CARDS [Nastran only]

Unrecognized cards starting from the top of the input file until the CEND keyword are stored in this control card, and written back out to the same part of the file.  This is known as the executive control section.

 

CASE_UNSUPPORTED_CARDS

Unrecognized cards between the CEND keyword and the BEGIN BULK keyword are stored in this control card, and written back out to the same part of the file.  This is known as the case control section.

 

BULK_UNSUPPORTED_CARDS

Unrecognized cards between the BEGIN BULK keyword and the ENDDATA keyword are stored in this control card, and written back out to the same part of the file.  This is known as the bulk data section.

 

Forced Unsupported Cards


Any block of text in an input file can be forced into any of the UNSUPPORTED_CARDS by bracketing the text with $HM_BEGIN_UNSUPPORTED and $HM_END_UNSUPPORTED.

nastran_radbulk_forceunsupportedcards

For example, consider the DTPL card shown above with a new field that is not supported in HyperMesh.  Without forcing the entire card into UNSUPPORTED_CARDS, the NEWFIELD would become lost during import/export.

 

Include Files


Include files can also handle unsupported cards in the same way as the master file as described above.

hmtoggle_arrow1Abaqus

The Abaqus interface can handle several types of unsupported cards.

Unsupported materials
Unsupported cards (model part)
Unsupported step data (history part)

 

Unsupported material

Unsupported materials can be handled in two ways.

Automatically detect materials that contain certain cards that are currently unsupported. Once detected, those cards are preserved as simple text within the material card. On export, they will be written within the original material block and labeled with the comment **HM_UNSUPPORTED_MATERIAL
Declare entire materials as unsupported. To handle unsupported materials by this method:
-Insert the comment **HM_GENERIC_MATERIAL before each *MATERIAL card that contains unsupported keywords. Only materials with the comment will be imported as plain text.

or

-Select the Generic material check box on the Options panel of the Utility Menu. All material cards will be set as unsupported.

 

If a supported material card has a parameter that is currently unsupported, the card will be imported but the parameter will be ignored. You will receive a warning message during the import process.

Contents of unsupported or generic materials can be reviewed or edited with the card editor in the Model browser.

 

Unsupported cards (model data)

In addition to the unsupported material card and the generic material there are three places where currently unsupported keywords can be stored. All concerned cards placed before the first *NODE card will go to the UNSUPPORTED_CARDS_START, those between *NODE and last *MATERIAL block are placed in UNSUPPORTED_CARDS_MIDDLE card and all other unsupported cards of the model part can be found in UNSUPPORTED_CARDS after import. Once unsupported cards are detected you will receive a warning message during import.

The cards and their contents can be reviewed in the control cards area or in the Model browser.

On export, a comment is inserted before each type of unsupported card:

**HM_UNSUPPORTED_CARDS_START
**HM_UNSUPPORTED_CARDS_MIDDLE
**HM_UNSUPPORTED_CARDS

 

The start of unsupported cards will be placed before the first node card, the middle part behind the last *MATERIAL card and the last part will be placed directly before the Step definition.

However, there is one special case for unsupported model data cards. Abaqus provides several type options for the *INITIAL CONDITIONS card. Currently, the VELOCITY, TEMPERATURE, and FLUID PRESSURE types are supported. For these cards, a load collector will be created on import. However, in cases where the type parameter value is not one of these supported values, this card will be handled as an unsupported card according to the rules described above.

 

Unsupported step data (history data)

If unknown keywords are detected within a *STEP definition, they will be placed in the unsupported cards section within the step. There is an unsupported card available in every *STEP. New unsupported cards can also be added and exported by the Step Manager.

 

hmtoggle_arrow1Exodus

INP_UNSUPPORTED_CARDS

INP_UNSUPPORTED_CARDS2

hmtoggle_arrow1LS-DYNA

The complete list of LS-DYNA keywords that are not supported are listed below.

 

*ALE_FSI_PROJECTION

*ALE_FSI_SWITCH_MMG_ID

*ALE_UP_SWITCH

*BOUNDARY_ACOUSTIC_COUPLING

*BOUNDARY_CONVECTION_SEGMENT

*BOUNDARY_CYCLIC

*BOUNDARY_ELEMENT_METHOD_CONTROL

*BOUNDARY_ELEMENT_METHOD_OPTION

*BOUNDARY_ELEMENT_METHOD_FLOW

*BOUNDARY_ELEMENT_METHOD_NEIGHBOR

*BOUNDARY_ELEMENT_METHOD_SYMMETRY

*BOUNDARY_ELEMENT_METHOD_WAKE

*BOUNDARY_FLUX_OPTION

*BOUNDARY_MCOL

*BOUNDARY_PRESCRIBED_ACCELEROMETER_RIGID

*BOUNDARY_PRESCRIBED_ORIENTATION_RIGID_ANGLES

*BOUNDARY_PRESCRIBED_ORIENTATION_RIGID_DIRCOS

*BOUNDARY_PRESCRIBED_ORIENTATION_RIGID_EULERP

*BOUNDARY_PRESSURE_OUTFLOW_SEGMENT

*BOUNDARY_PRESSURE_OUTFLOW_SET

*BOUNDARY_RADIATION_SEGMENT

*BOUNDARY_RADIATION_SEGMENT_VF_CALCULATE

*BOUNDARY_RADIATION_SEGMENT_VF_READ

*BOUNDARY_RADIATION_SET_EF_CALCULATE

*BOUNDARY_RADIATION_SET_EF_READ

*BOUNDARY_RADIATION_SET_VF_CALCULATE

*BOUNDARY_RADIATION_SET_VF_READ

*BOUNDARY_SLIDING_PLANE

*BOUNDARY_SPH_SYMMETRY_PLANE

*BOUNDARY_SYMMETRY_FAILURE

*BOUNDARY_THERMAL_WELD

*BOUNDARY_USA_SURFACE

*CASE

*CASE_BEGIN_CIDn

*CASE_END_CIDN

*CONSTRAINED_ADAPTIVITY

*CONSTRAINED_BUTT_WELD

*CONSTRAINED_EULER_IN_EULER

*CONSTRAINED_GENERALIZED_WELD_COMBINED_ID

*CONSTRAINED_GENERALIZED_WELD_CROSS_FILLET_ID

*CONSTRAINED_INTERPOLATION_LOCAL

*CONSTRAINED_JOINT_CONSTANT_VELOCITY

*CONSTRAINED_POINTS

*CONSTRAINED_SPLINE

*CONTACT_COUPLING

*CONTACT_GEBOD_OPTION

*CONTACT_GUIDED_CABLE

*CONTACT_GUIDED_CABLE_SET

*CONTACT_SURFACE_TO_SURFACE_CONTRACTION_JOINT(ID)

*CONTACT_TIEBREAK_NODES_ONLY(ID)

*CONTACT_TIED_SURFACE_TO_SURFACE_TITLE(ID)

*CONTACT_TIED_SURFACE_TO_SURFACE_FAILURE TITLE(ID)

*CONTACT_1D

*CONTACT_2D_AUTOMATIC_NODE_TO_SURFACE

*CONTACT_2D_AUTOMATIC_SINGLE_SURFACE

*CONTACT_2D_AUTOMATIC_SURFACE_IN_CONTINUUM

*CONTACT_2D_AUTOMATIC_TIED

*CONTACT_2D_AUTOMATIC_TIED_ONE_WAY

*CONTACT_2D_PENALTY

*CONTACT_2D_PENALTY_FRICTION

*CONTROL_CHECK_SHELL

*CONTROL_FORMING_POSITION

*CONTROL_FORMING_PROJECTION

*CONTROL_FORMING_TEMPLATE

*CONTROL_FORMING_TRAVEL

*CONTROL_FORMING_USER

*CONTROL_NONLOCAL

*DATABASE_ADAMS

*DATABASE_H3OUT

*DATABASE_BINARY_D3PART

*DATABASE_BINARY_D3PROP

*DATABASE_BINARY_D3CRACK

*DATABASE_HISTORY_SPH_SET

*DEFINE_CONNECTION_PROPERTIES_ADD

*DEFINE_CONSTRUCTION_STAGES

*DEFINE_CONTACT_VOLUME

*DEFINE_CURVE_COMPENSATION

*DEFINE_CURVE_DRAWBEAD

*DEFINE_CURVE_ENTITY

*DEFINE_CURVE_FUNCTION

*DEFINE_DEATH_TIMES_NODES

*DEFINE_DEATH_TIMES_RIGID

*DEFINE_DEATH_TIMES_SET

*DEFINE_ERODING_SINGLE_SURFACE

*DEFINE_FRICTION_AUTOMATIC_GENERAL

*DEFINE_FRICTION_AUTOMATIC_NODES_TO_SURFACE

*DEFINE_FRICTION_AUTOMATIC_ONE_WAY_SURFACE_TO_SURFACE

*DEFINE_FRICTION_AUTOMATIC_SINGLE_SURFACE

*DEFINE_FRICTION_AUTOMATIC_SURFACE_TO_SURFACE

*DEFINE_FRICTION_SINGLE_SURFACE

*DEFINE_SET_ADAPTIVE

*DEFINE_SPOTWELD_FAILURE_RESULTANTS

*DEFINE_SPOTWELD_RUPTURE_PARAMETER

*DEFINE_SPOTWELD_RUPTURE_STRESS

*DEFINE_STAGED_CONSTRUCTION_PART

*EF_CONTROL

*EF_GRID

*EF_MATERIAL

*EF_TOGGLES

*ELEMENT_BEAM_WARPAGE

*ELEMENT_DIRECT_MATRIX_INPUT

*ELEMENT_SHELL_SOURCE_SINK

*ELEMENT_SOLID_DOF

*EOS_GASKET

*EOS_JWLB

*INCLUDE_BINARY

*INCLUDE_NASTRAN

*INCLUDE_STAMPED_PART_SET_MATRIX_INVERSE

*INCLUDE_STAMPED_SET

*INCLUDE_TRANSFORM_BINARY

*INITIAL_STRESS_DEPTH

*INITIAL_STRESS_SHELL_SET

*INITIAL_STRESS_TSHELL

*INTERFACE_JOY

*INTERFACE_LINKING_DISCRETE_NODE_NODE

*LOAD_ALE_CONVECTION

*LOAD_ALE_CONVECTION_ID

*LOAD_BODY_POROUS

*LOAD_DENSITY_DEPTH

*LOAD_HEAT_CONTROLLER

*LOAD_HEAT_GENERATION_SET

*LOAD_HEAT_GENERATION_SOLID

*LOAD_MOTION_NODE

*LOAD_MOVING_PRESSURE

*LOAD_REMOVE_PART

*LOAD_SEGMENT_NONUNIFORM_ID

*LOAD_SEGMENT_SET_NONUNIFORM_ID

*LOAD_SSA

*LOAD_STIFFEN_PART

*LOAD_SURFACE_STRESS

*LOAD_SURFACE_STRESS_SET

*LOAD_THERMAL_TOPAZ

*LOAD_VOLUME_LOSS

*NODE_SCALAR

*NODE_SCALAR_VALUE

*MAT_ALE_VACCUM

*MAT_ALE_VISCOUS

*MAT_ALE_GAS_MIXTURE

*MAT_ANISOTROPIC_THERMOELASTIC

*MAT_BRAIN_LINEAR_VISCOELASTIC

*MAT_CFD_OPTION

*MAT_COHESIVE_GENERAL

*MAT_COHESIVE_TH

*MAT_COMPOSITE_DIRECT

*MAT_COMPOSITE_MATRIX

*MAT_CONCRETE_BEAM

*MAT_CONCRETE_EC2

*MAT_DAMAGE_1

*MAT_DAMAGE_2

*MAT_DAMAGE_3

*MAT_DRUCKER_PRAGER

*MAT_EMMI

*MAT_FHWA_SOIL

*MAT_FHWA_SOIL_NBRASKA

*MAT_GURSON_RCDC

*MAT_HEART_TISSUE

*MAT_HYSTERIC_SOIL

*MAT_INV_HYPERBOLIC_SIN

*MAT_ISOTROPIC_SMEARED_CRACK

*MAT_JOHNSON_HOLMQUIST_CONCRETE

*MAT_JOINTED_ROCK

*MAT_LUNG_TISSUE

*MAT_MCCORMICK

*MAT_MODIFIED_FORCE_LIMITED

*MAT_MODIFIED_JOHNSON_COOK

*MAT_MOHR_COULOUMB

*MAT_MUSCLE

*MAT_ORTHO_ELASTIC_PLASTIC

*MAT_ORTHOTROPIC_SMEARED_CRACK

*MAT_PITZER_CRUSHABLE_FOAM

*MAT_PLASTIC_GREEN-NAGHDI_RATE

*MAT_PLASTIC_NONLINEAR_KINEMATIC

*MAT_PLASTICITY_COMPRESSION_TENSION_EOS

*MAT_POLYMER

*MAT_QUASILINEAR_VISCOELASTIC

*MAT_RAMBERG-OSGOOD

*MAT_RATE_SENSITIVE_COMPOSITE_FABRIC

*MAT_RATE_SENSITIVE_POLYMER

*MAT_RC_BEAM

*MAT_RS_SHEAR_WALL

*MAT_SEISMIC_BEAM

*MAT_SEISMIC_ISOLATOR

*MAT_SOIL_BRIC

*MAT_SOIL_CONCRETE

*MAT_SPECIAL_ORTHOTROPIC

*MAT_SPRING_MUSCLE

*MAT_SPRING_SQUAT_SHEARWALL

*MAT_SPRING_TRILINEAR_DEGRADING

*MAT_STEEL_CONCENTRIC_BRACE

*MAT_THERMAL_ISOTROPIC_TD

*MAT_THERMAL_ISOTROPIC_PHASE_CHANGE

*MAT_THERMAL_ORTHTROPIC_TD

*MAT_THERMAL_USER_DEFINED

*MAT_THERMO_ELASTO_VISCOPLASTIC_CREEP

*MAT_UNIFIED_CREEP

*MAT_VISCO_ELASTIC_THERMAL

*MAT_WTM_STM

*MAT_WTM_STM_PLC

*PART_ADAPTIVE_FAILURE

*PART_MODES

*PERTURBATION_NODE

*PERTURBATINO_SHELL_THICKNESS

*RAIL_TRACK

*RAIL_TRAIN

*SET_2D_SEGMENT(TITLE)

*SET_2D_SEGMENT_SET(TITLE)

*TERMINATION_BODY

*TERMINATION_CONTACT

*TERMINATION_CURVE

*TERMINATION_DELETED_SHELLS

*TERMINATION_DELETED_SHELLS_SET

*TERMINATION_NODE

*USER_LOADING

 

hmtoggle_arrow1MADYMO

DEFINE

CRDSYS_REF_1

CRDSYS_REF_2

hmtoggle_arrow1PAM-CRASH 2G

3D

AMCTRL /

ARGUMENT

CNTAD /

CONTACT

CPCTRL

CTCTRL /

DRAWB

END_MODULE

EXPORT /

FLCEL /

FUNCTION

H_POINT

IMPFIL /

IMPORT /

KELVIN

LINCO /

LOCAL_H

LOOKU /

MARK /

Material Type 19

Material Type 24

Material Type 35

Material Type 80-83

MAXWELL

MBSYS /

MDBODY

MGRID

MODULE /

MSTRM /

MUSC1 /

MUSCL /

OUTPUT

SCALEF_MGRID

SECURE /

SPCTRL /

SPHEL /

SUBCYCLE_ECL

SYMPL /

hmtoggle_arrow1PERMAS

The PERMAS interface can handle two different types of unsupported cards:

Materials
Solver cards

 

Depending on which bracket or variant they belong to, unsupported keywords are maintained as ASCII text within the HyperMesh database and are placed in the right place on export again.

 

Unsupported material

Unsupported materials can be handled in two ways.

Generic material
Unsupported material

 

If materials are completely unsupported, they will be read in as generic material, whereas unsupported cards which are dependent on a certain material will be imported as ‘unsupported material’ and can be reviewed from within the material card image. On export, a comment will be written before each generic material (!!HM_GENERIC_MATERIAL) or unsupported material (!!HM_UNSUPPORTED_CARDS).

Unsupported card mechanism

Cards

Generic material

$SANDWICH

$LAMINATE

$FLFSOLID

$MATERIAL TYPE= TRANS, ORTHO, MONOCLINIG, TRICLINIC, ANISO

Unsupported material

$DIELECTRIC

$ELCONDUCT

$FLDENS

$NLELASTIC

$NLKINHARD

$PERMEABILITY

$VISCOSITY

Unsupported cards

In addition to the unsupported material card and the generic material, other unsupported data will be maintained based on the location in their bracket/variant and placed there again on export. The following table shows in which entity an unsupported card will go. All information is accessible after import through the card editor and will be written out exactly the same as imported.

PERMAS Variant/Bracket

Entity

$SYSTEM

Control Card "System"

$STRUCTURE

Control Card "Unsupported_Structure"

$CONSTRAINTS

Load Step

$LOADING

Load Step

$RESULTS

Output Block