10.0 API Programmer's Guide

2D/3D Properties

In HyperMesh v10.0, solver group #2 (Radioss, ANSYS, LS-DYNA, PAM-CRASH, Permas) solvers have converted from using attributes to assign properties components to using core HyperMesh references. This completes the 2D/3D properties project started in 9.0 for both solver groups.

For solver group #1 (OptiStruct, Abaqus, Nastran) the following diagram and rules apply for property assignment to components and elements:

• If property assigned to the element, that element is assigned the element property.
• If no property is assigned to the element, that element is assigned its component property.
• If no property is assigned to the element or component, that element is assigned no property.
• Materials are always assigned to properties and each element is assigned the material of its property.

For solver group #2 (Radioss, ANSYS, LS-DYNA, PAM-CRASH, Permas) the following diagram and rules apply for property assignment to components and elements:

• Property and materials are assigned to components only. Ignores any property assigned to elements.
• All elements within a component are assigned the component property and the component material.

New and Updated Tcl Commands for 2D/3D Properties

• Elements and components now have data names for referenced properties:
  1. a) property (pointer)
  2. b) propertyid
• To query the property and material assigned to a component or an element for solver group #1:
  1. hm_getentityvalue comps $id property.id 0
  2. hm_getentityvalue elems $id property.id 0
  3. hm_getentityvalue elems $id property.material.id 0
• To query the property and material assigned to a component or an element for solver group #2:
  1. hm_getentityvalue comps $id material.id 0
  2. hm_getentityvalue comps $id property.id 0
  3. hm_getentityvalue elems $id collector.material.id 0
  4. hm_getentityvalue elems $id collector.property.id 0
  Note: If an element has been assigned a property directly it is still possible to query these values even though the solver group is not using them.
• *propertyupdate entity_type mark_id property_name
  • This command assigns/updates/unassigns the property associated with components and elements. This same command is used by the assign subpanel in both the Comps and Properties panels.
• *createmark/*appendmark/hm_createmark/hm_appendmark
  • These options are available for components and elements:
    • "by property"
    • "by property id"
    • "by property name"
• *createmark/*appendmark/hm_createmark/hm_appendmark
  • These options are available for components, elements, and properties:
    • "by material"
    • "by material id"
    • "by material name"
• hm_getthickness entity_type entity_id ?ply_id?\
  • This command returns the thickness associated with the passed components and elements. The optional ply_id argument allows for additional control for querying the thickness of individual plies of composites. The thicknesses returned by this command follow the specific solver interface rules described above.
• hm_getcompthickness
  • This command will return the same values as in 8.0, the thickness assigned to the property assigned to the component for both solver groups #1 and #2. However, these may not be the expected values as properties for solver group #1 can be assigned to the elements as of 9.0. The continuing usage is of this command is not recommended, instead, use the command hm_getthickness with the appropriate options. This command will be deprecated.

Scripting Considerations

• Card images on components have been moved to properties for solver group #1.

  For example, the OptiStruct PSHELL card image is now a property card image instead of a component card image. Any scripts that create components and assign these card images must now create a property and assign the property to the component or to the elements.

• Both elements and components can have property references for solver group #1.
  • Scripts that either set or query properties (thickness for example) must now consider that elements within the component can also have properties assigned directly to them.
  • Properties on components are now core references instead of template attributes for solver group #2. Instead of using the template attributes, scripts must now be updated to use the core data reference.
• Scripts using hm_getcompthickness.
  • This command is no longer supported and continuing usage is not recommended. Instead, use the command hm_getthickness with the appropriate options.

When converting or switching between solver interfaces it is possible to have some “mixture” between the two methods shown above. It is important to know what the correct practice is for each solver interface in order to know when modifications are required. It is also important to know these practices in order to understand the values being returned from relevant Tcl commands.

New Commands

Modified Commands

Deprecated Commands

Removed Commands