moments
Unless otherwise specified, data names are accessible in level 3 only.
- engineering_type
- The engineering type of load. Engineering loads act on set entities. Valid values are:
The following data names are available for both classic and engineering loads:
- attributesmax
- The number of attributes owned by this entity.
- collector
- Pointer to the collector that owns the element.
- config
- The configuration of the entity.
- definedentity
- True if the entity is defined, false otherwise.
- entityid
- The ID of the entity the load is attached to.
- entitytype
- The type of the entity to which the load is applied.
- 1 - node
- 3 - comp
- 10 - set
- 27 - point
- entitytypename
- The string type of the entity to which the load is applied.
- nodes
- comps
- sets
- points
- id
- The ID of the entity.
- include
- The ID of the include file the entity is organized in.
- includeid
- The ID of the include file the entity is organized in.
- internalid
- The ID of the entity.
- internalname
- The internal name of the entity.
- moduleid
- The module ID of the entity.
- poolid
- The pool number of the entity.
- poolname
- The pool name of the entity.
- set
- Pointer to the set when the load is applied to a set.
- solver_id
- The solver ID of the entity.
- solverkeyword
- The name of the solver keyword.
- solvername
- The solver name of the entity for entities enabled for name pool, otherwise the internal name of the entity.
- type
- The solver dependent type code for the entity.
- typename
- The solver dependent type name for the entity.
- vectorx
- The x component of the unit vector.
- vectory
- The y component of the unit vector.
- vectorz
- The z component of the unit vector.
The following data names are available for classic loads:
- baselocation
- The coordinates where the load on a component or set should display. Valid for hm_getvalue query only.
- baselocationx
- The x-coordinate where the load on a component or set should display.
- baselocationy
- The y-coordinate where the load on a component or set should display.
- baselocationz
- The z-coordinate where the load on a component or set should display.
- comp1
- The x component of the vector in the global coordinate system.
- comp2
- The y component of the vector in the global coordinate system.
- comp3
- The z component of the vector in the global coordinate system.
- component
- Pointer to the component when the load is applied to a component.
- curveid
- The ID of the curve defining the load magnitude when a curve has been used to define the load.
- inputsystem
- Pointer to the reference system.
- inputsystemid
- The ID of the reference system.
- local_comp1
- The x component of the vector in the local coordinate system.
- local_comp2
- The y component of the vector in the local coordinate system.
- local_comp3
- The z component of the vector in the local coordinate system.
- local_vector
- The load vector in the local coordinate system.
- local_vectorx
- The x component of the unit vector in the local coordinate system.
- local_vectory
- The y component of the unit vector in the local coordinate system.
- local_vectorz
- The z component of the unit vector in the local coordinate system.
- location
- The ID of the node where the load is applied. Valid for hm_getvalue query only.
- magnitude
- The magnitude of the vector.
- mappedid
- The ID of the original load on geometry.
- node
- Pointer to the node when the load is applied to a node.
- vector
- The component of the unit vector. Valid for hm_getvalue query only.
- xscale
- The x scale or time scale of the load curve when a curve has been used to define the load.
The following data names are available for engineering loads:
- compx
- The dot product of the load vector projected on the global x axis.
- compy
- The dot product of the load vector projected on the global y axis.
- compz
- The dot product of the load vector projected on the global z axis.
- distribution_table_count
- The number of rows of a non-uniform engineering load.
- field
- The field entity that stores the tabular load data.
- location_unit_node
- The nodes for which the data is stored in the table for a non-uniform engineering load.
- orient
- The load orientation vector.
- orientx
- The x component of the load orientation vector.
- orienty
- The y component of the load orientation vector.
- orientz
- The z component of the load orientation vector.
- resultant_magnitude
- The resultant scalar component of the load vector in the global coordiante system.
The following data names are available for ADVC engineering loads:
- displayname
- The text for the title entry.
- distribution
- The distribution type:
- expanded_form_flag
- Flag to export loads on nodes.
- keyword_name
- Flag to specify if the title entry is enabled.
- load_step_id
- The ID of the referred loadstep.
- magnitude
- The scale factor (default 1.0).
- prev_bc
- Flag to hold previously applied boundary conditions.
- vector
- The direction of the force vector. At lesat one of the vector components must be non-zero.
The following data names are available for LS-DYNA engineering loads:
- crash_dir_flag
- Input flag to determine if directions can be input using vector or using crash direction semantics.
- curveid
- The load curve ID.
- follower_load
- Flag that activates the follower load options.
- force_ev_fn
- Flag that activates force as a function of the absolute value of the rigid body displacement.
- inputsystem
- The coordinate system ID.
- load_dof
- Applicable degree-of-freedom for LOAD_NODE (type=1) and LOAD_RIGID_BODY (type=2).
- magnitude
- The load curve scale factor (default 1.0).
- plane_node1
- The node 1 ID for LOAD_NODE (type=1) and LOAD_RIGID_BODY (type=2). Only necessary if load_dof=8.
- plane_node2
- The node 2 ID for LOAD_NODE (type=1) and LOAD_RIGID_BODY (type=2). Only necessary if load_dof=8.
- plane_node3
- The node 3 ID for LOAD_NODE (type=1) and LOAD_RIGID_BODY (type=2). Only necessary if load_dof=8.
- rigid_part
- The part ID of the rigid body.
- vector
- Force load vector components in the coordinate system CID.
The following data names are available for Nastran and OptiStruct engineering loads:
- distribution
- The distribution type:
- inputsystem
- The coordinate system ID. A value of 0 or blank references the basic coordinate system.
- magnitude
- For MOMENT, the scale factor.
- os_g1
- The grid point ID.
- os_g2
- The grid point ID.
- vector
- The direction of the moment vector measured in the system defined by CID. At lesat one of the vector components must be non-zero.
The following data names are available for OptiStruct engineering loads:
- curveid
- The ID of the MBCRV entries giving load versus independent variable measured in the coordinate system defined by CID.
- expanded_form_flag
- Flag to export loads on nodes.
- os_eid
- The ID of the MBVAR for the independent variable expression.
- os_intrp_type
- The interpolation type. Valid values are AKIMA (default), CUBIC or LINEAR.
The following data names are available for Radioss engineering loads:
- curveid
- The ID of the curve defining the time function identifier.
- crash_dir_flag
- Specifies if directions can be input using vector or crash direction semantics:
- crash_dofstring
- The sring that outputs the computed DOF directions, useful if the direction is specified using a string vector.
- displayname
- The text for the title entry.
- inputsystem
- The system ID for the skew or frame identifier.
- magnitude
- The ordinate scale factor (default 1.0).
- rad_dir
- The direction in translation. Valid values are X, Y and Z for forces and XX, YY and ZZ for moments.
- rad_ivar_flag
- The flag to disregard the variation of velocity with respect to time for the calculation of the force.
- rad_sensor_id
- The ID of the sensor entity.
- xscale
- The abscissa (time) scale factor (default 1.0).
Version History
2020 - New support for engineering loads. Added new data names compx, compy, compz, crash_dir_flag, crash_dofstring, displayname, distribution, distribution_table_count, engineering_type, expanded_form_flag, field, local_comp1, local_comp2, local_comp3, local_vector, local_vectorx, local_vectory, local_vectorz, location, location_unit_node, orient, orientx, orienty, orientz, os_eid, os_g1, os_g2, os_intrp_type, rad_dir, rad_ivar_flag, rad_sensor_id and resultant_magnitude.
2020.1 - Added new data name solverkeyword.
2021 - Added new data names keyword_name, load_step_id and prev_bc. New ADVC support.
2021.1 – Added new data names for LS-DYNA engineering loads: crash_dir_flag, curveid, follower_load, force_ev_fn, inputsystem, load_dof, magnitude, plane_node1, plane_node2, plane_node3, rigid_part and vector.
2021.1 - Added new data names moduleid, poolid, poolname, and solver_id.
2021.2 - Added new data names internalname and solvername.