2017 API Programmer's Guide

Groups to Rigidwalls

The LS-DYNA keywords *RIGIDWALL_GEOMETRIC_CYLINDER, *RIGIDWALL_GEOMETRIC_CYLINDER_DISPLAY, *RIGIDWALL_GEOMETRIC_CYLINDER_MOTION, *RIGIDWALL_GEOMETRIC_CYLINDER_MOTION_DISPLAY, *RIGIDWALL_GEOMETRIC_FLAT, *RIGIDWALL_GEOMETRIC_FLAT(FINITE), *RIGIDWALL_GEOMETRIC_FLAT_DISPLAY, *RIGIDWALL_GEOMETRIC_FLAT_DISPLAY(FINITE), *RIGIDWALL_GEOMETRIC_FLAT_MOTION, *RIGIDWALL_GEOMETRIC_FLAT_MOTION(FINITE), *RIGIDWALL_GEOMETRIC_FLAT_MOTION_DISPLAY, *RIGIDWALL_GEOMETRIC_FLAT_MOTION_DISPLAY(FINITE), *RIGIDWALL_GEOMETRIC_PRISM, *RIGIDWALL_GEOMETRIC_PRISM(FINITE), *RIGIDWALL_GEOMETRIC_PRISM_DISPLAY, *RIGIDWALL_GEOMETRIC_PRISM_DISPLAY(FINITE), *RIGIDWALL_GEOMETRIC_PRISM_MOTION, *RIGIDWALL_GEOMETRIC_PRISM_MOTION(FINITE), *RIGIDWALL_GEOMETRIC_PRISM_MOTION_DISPLAY, *RIGIDWALL_GEOMETRIC_PRISM_MOTION_DISPLAY(FINITE), *RIGIDWALL_GEOMETRIC_SPHERE, *RIGIDWALL_GEOMETRIC_SPHERE_DISPLAY, *RIGIDWALL_GEOMETRIC_SPHERE_MOTION, *RIGIDWALL_GEOMETRIC_SPHERE_MOTION_DISPLAY, *RIGIDWALL_PLANAR, *RIGIDWALL_PLANAR_FINITE, *RIGIDWALL_PLANAR_FINITE_FORCES, *RIGIDWALL_PLANAR_FINITE_MOVING, *RIGIDWALL_PLANAR_FINITE_MOVING_DISPLAY, *RIGIDWALL_PLANAR_FINITE_MOVING_FORCES, *RIGIDWALL_PLANAR_FINITE_MOVING_FORCES_DISPLAY, *RIGIDWALL_PLANAR_FORCES, *RIGIDWALL_PLANAR_MOVING, *RIGIDWALL_PLANAR_MOVING_DISPLAY, *RIGIDWALL_PLANAR_MOVING_FORCES, *RIGIDWALL_PLANAR_MOVING_FORCES_DISPLAY, *RIGIDWALL_PLANAR_ORTHO, *RIGIDWALL_PLANAR_ORTHO_FINITE, *RIGIDWALL_PLANAR_ORTHO_FINITE_FORCES and *RIGIDWALL_PLANAR_ORTHO_FORCES have been mapped from the group entity to the new rigidwalls entity. See the rigidwalls data names documentation for more details.

Scripts that created or queried the group entity for these keywords must be updated to use the rigidwalls entity. Note that solver ID pools are no longer required with this new entity type as well. Below are a few examples.

To create a *RIGIDWALL_PLANAR keyword, create a rigidwall entity with config 102:
*createentity rigidwalls config=102
To update the values of different data names like geometrytype, NodeSet_ID, excludeNodeSet_ID and Block_ID:
*setvalue rigidwalls id=$id geometrytype=$geometry_type
*setvalue rigidwalls id=$id NodeSet_ID=$NodeSet_ID
*setvalue rigidwalls id=$id excludeNodeSet_ID=$excludeNodeSet_ID
*setvalue rigidwalls id=$id Block_ID=$Block_ID

Masking of Solid Surfaces

The masking of individual surfaces of solids has thus far not been supported. To mask a solid surface, the solid must first be deleted, and then individual surfaces can be masked. In addition, user scripts may have come to rely that when a solid is displayed, all of its surfaces are also displayed. However, masking of individual surfaces of solids will be supported starting with the 2018 release. It is important for users to take action to update the logic in their scripts now, so that they will continue to work when the new support is available.

Removal of hm_solverconvert command

This command will be deprecated and removed with the 2018 release. It is important for users to take action to update their scripts to use *solverconvert now, so that they will continue to work when hm_solverconvert is removed.

New Commands

Modified Commands

The following commands have new options or enhanced capabilities. Existing scripts are not affected and only need to be updated if usage of the new functionality is desired:
  • Data Names
    • beamsects
      • shell – Added new data name beamsect_nonstandard.
      • solid – Added new data name beamsect_nonstandard.
      • standard – Added new data names beamsect_dim1, beamsect_dim2, beamsect_dim3, beamsect_dim4, beamsect_dim5, beamsect_dim6, beamsect_dim7, beamsect_dim8, beamsect_dim9 and sectiontype. Changed the datatype of standard_subtype from integer to string.
    • modules – Added new data names creator_tag, library_revision, library_udm_uid, major_revision, PDM_PartNumber, prototype_id and study_revision.
    • opticontrols - Added new data names ddvopt and ddvopttoggle.
    • optiresponses – Added new data name spwld.
  • General/Core
  • Meshing
    • *sphgenerate_new – Execution in all user profiles now supported, without the creation of solver data.