temperatures

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:
0 - Classic load
7 - Thermal engineering load
Type: unsigned integer

The following data names are available for both classic and engineering loads:

attributesmax
The number of attributes owned by this entity.
Type: unsigned integer
collector
Pointer to the collector that owns the load.
Type: pointer(levels 2, 3, and 4)
config
The configuration of the entity.
5 - Temperature
Type: unsigned integer
definedentity
True if the entity is defined, false otherwise.
Type: Boolean
entityid
The ID of the entity the load is attached to.
Type: integer
entitytype
The type of the entity to which the load is applied.
  • 1 - node
  • 2 - elem
  • 3 - comp
  • 10 - set
  • 27 - point
Type: integer
entitytypename
The string type of the entity to which the load is applied.
  • nodes
  • elems
  • comps
  • sets
  • points
Type: string
id
The ID of the entity.
Type: unsigned integer
include
The ID of the include file the entity is organized in.
Type: entity
includeid
The ID of the include file the entity is organized in.
Type: unsigned integer
internalid
The ID of the entity.
Type: unsigned integer
set
Pointer to the set when the load is applied to a set.
Type: pointer
solverkeyword
The name of the solver keyword.
Type: string
type
The solver dependent type code for the entity.
Type: integer
typename
The solver dependent type name for the entity.
Type: string

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.
Also used to convert the load vector components into local values for non-rectangular coordinate systems.
Type: triple double
baselocationx
The x-coordinate where the load on a component or set should display.
Also used to convert the load vector components into local values for non-rectangular coordinate systems.
Type: double
baselocationy
The y-coordinate where the load on a component or set should display.
Also used to convert the load vector components into local values for non-rectangular coordinate systems.
Type: double
baselocationz
The z-coordinate where the load on a component or set should display.
Also used to convert the load vector components into local values for non-rectangular coordinate systems.
Type: double
component
Pointer to the component when the load is applied to a component.
Type: pointer
curveid
The ID of the curve defining the load magnitude when a curve has been used to define the load.
Type: integer
inputsystem
Pointer to the reference system.
Type: pointer
inputsystemid
The ID of the reference system.
Type: integer
location
The ID of the node where the load is applied. Valid for hm_getvalue query only.
Type: entity
mappedid
The ID of the original load on geometry.
Type: integer
node
Pointer to the node when the load is applied to a node.
Type: pointer
temperature
The value of the temperature load.
Type: double
xscale
The x scale or time scale of the load curve when a curve has been used to define the load.
Type: double

The following data names are available for engineering loads:

distribution_table_count
The number of rows of a non-uniform engineering load.
Type: unsigned integer
field
The field entity that stores the tabular load data.
Type: entity
location_unit_element
The elements for which the data is stored in the table for a non-uniform engineering load.
Type: entity array
location_unit_node
The nodes for which the data is stored in the table for a non-uniform engineering load.
Type: entity array
resultant_magnitude
The resultant scalar component of the load vector in the global coordiante system.
Type: double

The following data names are available for ADVC engineering loads:

constraint_type
Flag to indicate that temperature is retained from the previous process. This is valid for temperature load when type is 3.
Type: Boolean
distribution
The distribution type:
0 - Uniform
1 - Non-uniform
Type: unsigned integer
expanded_form_flag
Flag to export loads on nodes.
Type: Boolean
load_step_flag
Flag to indicate if the load step ID needs to be attached to the load. This is valid for temperature load when type is 1.
Type: Boolean
load_step_id
The ID of the referred loadstep.
Type: entity
magnitude
The temperature value.
Type: double
prev_bc
Flag to hold previously applied boundary conditions.
Type: Boolean

The following data names are available for Nastran engineering loads:

nas_tempbc_type
STAT - Constant temperature boundary condition
TRAN - Time-varying temperature boundary condition
Type: Boolean

The following data names are available for OptiStruct engineering loads:

expanded_form_flag
Flag to export loads on nodes.
Type: Boolean

The following data names are available for OptiStruct and Nastran engineering loads:

distribution
The distribution type:
0 - Uniform
1 - Non-uniform
Type: unsigned integer
magnitude
The temperature.
Type: double
os_t1
The temperature at the lower surface of shell elements.
Type: double
os_t2
The temperature at the upper surface of shell elements.
Type: double
os_tempp1_flag
The temperature unit flag for TEMPP1:
0 - Thermal gradient
1 - Surface temperature
Type: integer
os_tprime
The effective linear thermal gradient.
Type: double

The following data names are available for Radioss engineering loads:

curveid
The ID of the curve defining the time function identifier.
Type: entity
displayname
The text for the title entry.
Type: string
distribution
The INITEMP flag:
0 - Initial temperature/node group
1 - Initial temperature/node
Type: unsigned integer
magnitude
The ordinate scale factor for fct_ID (default 1.0).
Type: double
rad_sensor_id
The ID of the sensor entity.
Type: entity
rad_tstart
The start time.
Type: double
rad_tstop
The stop time (default 10^30).
Type: double
xscale
The abscissa (time) scale factor for fct_IDT (default 1.0).
Type: double

Version History

2020 - New support for engineering loads. Added new data names displayname, distribution, distribution_table_count, engineering_type, expanded_form_flag, field, location, location_unit_element, location_unit_node, nas_tempbc_type, os_t1, os_t2, os_tempp1_flag, os_tprime, rad_sensor_id, rad_tstart, rad_tstop and resultant_magnitude.

2020.1 - Added new data name solverkeyword.

2021 - Added new data names constraint_type, load_step_flag, load_step_id and prev_bc. New ADVC support.