2022 API Programmer's Guide

Constraints Renamed to Mechanismconstraints

The creation and modification of the new entity mechanismconstraints (constraints earlier) must be done using *createentity and *setvalue commands.

Any scripts that rely on using constraints entity for creating and modifying mechanisms and bodies entities in different user profiles, should be updated to use mechanismconstraints entity.

To create and set values to a mechanismconstraints entity, valid configs are 15, 16 and 17:

*createentity mechanismconstraints config=16 name="mechanismconstraints1"
*setvalue mechanismconstraints id=4 STATUS=2 pointnode={nodes 7052608} body1={bodies 2}

To set this created mechanismconstraints entity with ID 4 as part of a mechanism entity:

*setvalue mechanisms id=1 constraints={mechanismconstraints 4}

This change is also affecting the HMASCII and solver template commands. Both commands, formerly named *constraints(), have been renamed to *mechanismconstraints().

It is important to note that the constraints entity and the corresponding HMASCII and solver template commands remain valid. They have been reintroduced as a new entity representing surface and node-based coupling constraints in Abaqus solver interface.

Properties to Frictions

The PAM-CRASH keyword FRICT has been mapped from the property entity to the friction entity. See the frictions data names documentation for more details.

Scripts that created or queried the property entity for these keywords must be updated to use the friction entity.

To create a FRICT keyword, create a friction entity with config 401:

*createentity frictions config=401

To set the value of the frict1 field on a FRICT card:

*setvalue frictions id=1 STATUS=1 frict1=11.5

To query the value of the frict1 field on a FRICT card:

hm_getvalue frictions id=1 dataname=frict1

Properties to Integrationrules

The LS-DYNA keywords *INTEGRATION_BEAM and *INTEGRATION_SHELL have been mapped from the property entity to the new integrationrule entity. See the integrationrules data names documentation for more details.

Scripts that created or queried the property entity for these keywords must be updated to use the integrationrules entity.

To create an *INTEGRATION_BEAM keyword, create an integrationrule entity with config 101:

*createentity integrationrules config=101

To create an *INTEGRATION_SHELL keyword, create an integrationrule entity with config 102:

*createentity integrationrules config=102

To set the value of the NIP field in *INTEGRATION_BEAM or *INTEGRATION_SHELL card:

*setvalue integrationrules id=1 STATUS=1 NIP=1

To query the value of the NIP field in *INTEGRATION_BEAM or *INTEGRATION_SHELL card:

hm_getvalue integrationrules id=1 dataname=NIP

Properties to Perturbations

The LS-DYNA keywords *DEFINE_STOCHASTIC_VARIATION and *DEFINE_STOCHASTIC_VARIATION_PROPERTIES have been mapped from the property entity to the new perturbation entity. See the perturbations data names documentation for more details.

Scripts that created or queried the property entity for these keywords must be updated to use the perturbation entity.

To create a *DEFINE_STOCHASTIC_VARIATION keyword, create a perturbation entity with config 101:

*createentity perturbations config=101

To set the value of the R1 field in *DEFINE_STOCHASTIC_VARIATION card:

*setvalue perturbations id=1 STATUS=1 S_R1=1.1

To query the value of the R1 field on *DEFINE_STOCHASTIC_VARIATION card:

hm_getvalue perturbations id=1 dataname=S_R1

New Commands

Modified Commands

Deprecated Commands

• General/Core
  • hm_attributebehavior
  • hm_attributeentitytypename
  • hm_attributeindexbehavior
  • hm_attributestatus

Removed Commands

The following commands/options have been removed and are no longer available for use in scripts:

• Data Names
  • airbags
  • airbagfolds
  • airbagfoldingsequences
• HMASCII
  • *airbags()
  • *airbagfolds()
  • *airbagfoldingsequences()
• Template Commands
  • *airbags()
  • *airbagfolds()
  • *airbagfoldingsequences()