Field Names

The Field names drop-down menu allows you to select fields to be used in a Templex expression. The available options change depending on the attachment type selected from the Attach to drop-down menu, as well as the post-processing that has been applied.

Each field name has a Templex expression assigned to it. Below is a brief description of the Templex expressions that relate to the Window and Entity attachment types.

Window

{window.modeltitle}
The title of the currently loaded model.
{window.loadcase}
The label of the current subcase.
{window.simulationstep}
The label of the current simulation step.
{window.modelfilename}
Displays the path of the current model file.
{window.shortmodelfilename}
Displays the current model file name only (without the path).
{window.resultfilename}
Displays the path of the current result file.
{window.shortresultfilename}
Displays the current result file name only (without the path).
{window.loadcasefilename}
Displays the path of the file name for the current loadcase. This option is useful when loading multiple result files on a single model.
Note: In the case of a derived loadcase, which could be created from several result files, the expressions are shown as N/A.
{window.shortloadcasefilename}
Displays the file name (without the path) for the current loadcase. This option is useful when loading multiple result files on a single model.
Note: In the case of a derived loadcase, which could be created from several result files, the expressions are shown as N/A.
{window.frame}
Displays the current result frame number for the model.
Multiple Model info
{for (i = 0; i != numpts(window.modeltitlelist); ++i) }
{window.modelidlist[i]}: {window.modeltitlelist[i]}
{window.loadcaselist[i]} : {window.simulationsteplist[i]} : {window.framelist[i]}
Displays information about all of the models loaded in a window. This expression block is located within a for loop.
Note:
  • The individual expressions within the loop are similar in syntax to the ones used for displaying information related to the current model, with the addition of a list[i] at the end. For example, to request the model title, the expression for the current model is {window.modeltitle}, whereas to request the titles of all of the models, the expression is {window.modeltitlelist[i]}.
  • {window.modelidlist[i]} is a new expression.
  • In previous versions, changes have been made to the model info content as a result of which the result file name is no longer shown by default. This can be easily modified should you wish to do so by adding the expression {window.resultfilenamelist[i]} within the for loop. This modification can be done either at the session level, or globally in the Preference file.
Active Model info
{window.modelid}: {window.modeltitle}
{window.loadcase} : {window.simulationstep} : {window.frame}
Displays important information about the current model.

Entity

{entity.id}
The ID of the entity the note is attached to.
{entity.label}
The label of the entity the note is attached to. Returns “Element” for element, “Node” for node, and the label of the "part" for part (component).
{entity.pool}
The pool name to which the entity belongs to.
{entity.coords}
The global coordinates of the entity the note is attached to. In the case of parts and elements, it is the centroid coordinates of the entity.
{parent.id}
The ID of the parent of the entity the notes is attached to. For example, part (component) is the parent for nodes and assembly is the parent to part (component).
{parent.label}
The label of the parent of the entity the note is attached to.
{parent.pool}
The pool name of the parent of the entity the note is attached to.
{entity.contour_val}
The contour value of the entity the note is attached to.
Note: From version 2019, this expression returns the underlying numeric value instead of subcase or simulation information in the case of envelope subcase/simulation trace plot.

To display subcase or simulation information in a note, please use the new expressions, entity.envelope_subcase or entity.envelope_simulation.

Older session files, when loaded in version 2019, will automatically be updated to use the new expressions.

{entity.contour_max}
For a "part" (component) entity type, it corresponds to the max contour value of the entity the note is attached to.

This does not have any significance for nodes/elements. It is the same as the contour value at that node/element.

{entity.contour_min}
For a "part" (component) entity type, it corresponds to the min contour value of the entity the note is attached to.

This does not have any significance for nodes/elements. It is the same as the contour value at that node/element.

{contour.datatype}
The name of the data type which is contoured currently (for example: Displacement).
{contour.component}
The data type component which is contoured currently (for example: Mag).
{contour.layer}
Returns the layer name for which the result is contoured (for example: z1, z2, mid).
{contour.legend_min}
The current minimum of the static legend in the contour panel.
{contour.legend_max}
The current maximum of the static legend in the contour panel.
{contour.legend_localmin}
The current minimum of the dynamic legend in the contour panel.
{contour.legend_localmax}
The current maximum of the dynamic legend in the contour panel.
{entity.envelope_subcase}
The subcase to which the value belongs. Applicable only in the case of envelope load case trace plots.
{entity.envelope_simulation}
The simulation to which the value belongs. Applicable only in the case of envelope load case trace plots (except for a subcase trace plot).
Note: Whenever there is a tensor plot or a vector plot applied on the model, the Templex expression could potentially use tensor or vector, instead of contour. For example: {entity.tensor_val}, {entity.vector_val}, {tensor.datatype}, {vector.dataype}, etc.