Highlights
This release includes several usability improvements for HyperMesh LS-DYNA interface: A new entity is introduced for Constrained Extra Nodes and SET of type COLLECT are now supported.
The constrained extra nodes entity is newly introduced in 14.0. The following keywords are mapped to this entity: *CONSTRAINED_EXTRA_NODES_NODE; *CONSTRAINED_EXTRA_NODES_SET.
These keywords were supported prior to 14.0 but were mapped to a different entity (group).
Upon import the following behavior is implemented:
| • | Solver deck: these keywords will be automatically mapped to the new entity without loss |
| • | Legacy HyperMesh file: these keywords will be mapped from the old to the new entity without loss |
|
A number of enhancement have been made to the Model Checker:
| • | Invalid definition of *CONSTRAINED_RIGID_BODIES will be reported as an error |
| • | Unresolved IDs reference in set and components are now reported as warnings |
| • | Checking for untied nodes is faster and more accurate. In the right click contextual menu, added the possibility to create a set from the nodes found to be untied by HyperMesh |
|
| • | Upon import of the keyword *CONSTRAINED_RIGID_BODIES, HyperMesh will report a warning if the master and/or slave part ID are not defined. |
| • | When a field is unsupported but the value in this field is null, HyperMesh will not report a warning anymore. |
|
The Curve Editor now shows the curve ID and the X and Y scale factor applied on *DEFINE_CURVE. *DEFINE_TABLE is not listed in the Curve Editor anymore.
|
Set of type collect are now supported. The concept of master and child set collect is introduced to allow multiple sets of type collect to share the same ID. The COLLECT option is currently supported for all variants of the following set type:
|
Supported ALIAS (three digits numerical designation) for material. Earlier these were listed as unsupported cards upon reading. Now HyperMesh can read these materials and map them to the corresponding descriptive designation. For examples:
| • | *MAT_001 is equivalent to *MAT_ELASTIC |
| • | *MAT_009 is equivalent to *MAT_NULL |
| • | *MAT_020 is equivalent to *MAT_RIGID |
| • | *MAT_024 is equivalent to *MAT_PIECEWISE_LINEAR_PLASTICITY |
|
| • | *AIRBAG_SHELL_REFERENCE_GEOMETRY (I/O only) |
| • | *DAMPING_FREQUENCY_RANGE_DEFORM |
| • | *DEFINE_STOCHASTIC_VARIATION |
| • | *ELEMENT_SHELL_COMPOSITE_LONG |
| • | *EOS_TABULATED_COMPACTION (*EOS) |
| • | *INITIAL_VELOCITY_GENERATION_START_TIME |
| • | *MAT_ADD_THERMAL_EXPANSION |
| • | *MAT_JOHNSON_COOK_STOCHASTIC |
| • | *MAT_PLASTICITY_WITH_DAMAGE_STOCHASTIC |
| • | *MAT_TAILORED_PROPERTIES (MAT_251) |
| • | *MAT_CONCRETE_DAMAGE_REL3 (*MAT_072R3) |
|
The following keywords were updated up to 971 R7:
| • | *AIRBAG_WANG_NEFSKE_OPTIONS |
| • | *CONSTRAINED_GENERALIZED_WELD |
| • | *CONSTRAINED_RIGID_BODIES |
| • | *CONTACT_FORCE_TRANSDUCER |
| • | *CONTACT (Optional card E) |
| • | *CONTACT_SURFACE_TO_SURFACE |
| • | *CONTROL_IMPLICIT_DYNAMICS |
| • | *CONTROL_THERMAL_TIMESTEP |
| • | *DAMPING_FREQUENCY_RANGE |
| • | *MAT_ELASTIC_PLASTIC_THERMAL (*MAT_004) |
| • | *MAT_ELASTIC_VISCOPLASTIC_THERMAL (*MAT_106) |
| • | *MAT_FORCE_LIMITED (*MAT_029) |
| • | *MAT_GENERAL_NONLINEAR_6DOF_DISCRETE_BEAM (*MAT_119) |
| • | *MAT_MODIFIED_PIECEWISE_LINEAR_PLASTICITY (*MAT_123) |
| • | *MAT_NONLINEAR_ORTHOTROPIC (*MAT_40) |
| • | *MAT_ORTHOTROPIC_VISCOELASTIC (*MAT_086) |
| • | *MAT_PIECEWISE_LINEAR_PLASTICITY (*MAT_24) |
| • | *MAT_PLASTICITY_COMPRESSION_TENSION (*MAT_124) |
| • | *MAT_SCHWER_MURRAY_CAP_MODEL (*MAT_145) |
| • | *MAT_SIMPLIFIED_RUBBER/FOAM (*MAT_181) |
| • | *MAT_SPOTWELD (*MAT_100) |
|
| • | The association between node/element ID and description in *DATABASE_HISTORY_OPTION_ID is maintained when some of these nodes/elements are deleted. |
| • | HyperMesh was expecting the options in *CONSTRAINED_JOINT (FAILURE, LOCAL…) to be defined in a specific sequence. The keyword will now be imported irrespective of the input sequence. |
| • | In the Export tab, an option allows you to control the export of the include file reference depending on the export status. This option does not apply to INCLUDE of type TRANSFORM. |
| • | The local coordinate system defined in *MAT_RIGID was not imported correctly if the components of the vector (V1,V2,V3) were equal to 0 instead of being blank. |
| • | The transformations were not applied in the correct sequence when both *NODE_TRANSFORM and *INCLUDE_TRANSFORM were used. |
| • | Unresolved elements were not supported in *DATABASE_HISTORY leading to loss of data in I/O. |
| • | Exporting a model with a large number of connectors was significantly slower than without. |
| • | *MECHANISM was exported before *END. |
| • | Resolved several I/O issues in the following keywords: |
| - | *SENSOR_DEFINE_CALC-MATH |
| - | *MAT_GENERAL_SPRING_DISCRETE_BEAM |
| • | The ID field was set to 8 instead of 10 for the following keywords: |
| • | Curves referenced in loads (*LOAD_NODE_POINT…) were not exported with the export “displayed” option. |
| - | Conversion of *DEFINE_VECTOR_NODES was incorrect and lead to loss of data |
| - | Old HyperMesh file containing *SET_SHELL are converted to *SET_SHELL_LIST |
| • | Conversion from OptiStruct and Nastran to LS-DYNA: |
| - | Converting connectors linked to assemblies was causing an application error |
| - | SET ELEM are now converted to *SET_SHELL_LIST instead of *SET_SHELL |
| - | Thickness visualization was not correct after conversion |
| - | Offset defined in QUAD4 elements was not considered |
| - | An application error occurred if there was empty components in the model |
| • | When converting a model from LS-DYNA to RADIOSS, an application error occurred if there was “unresolved id” in the model. |
|
