Open animation files, measure various distances and angles between entities, and use the Results Browser to view the model structure and find, display, and edit entities.
Create and edit user-defined data type expressions, derived load cases, and systems. You can also plot a forming limit
diagram, generate streamlines, track entities during animation, and create and import/export sets of entities.
The list of available operators is controlled by the template file selected when loading a model and result, and it can
be modified by adding or removing <using /> statements in the template.
A result manipulation library that enables user-defined data types to be added to a result, and transitions complex data
manipulation tasks from HyperView to a reusable, modifiable set of libraries that focus solely on result processing tasks.
Use the FLD tool a plot a Forming Limit Diagram (FLD) based on a material Forming Limit Curve (FLC) and the major and
minor strain output results of a forming simulation.
Query entities, create or edit free body diagrams, construct multiple curves and plots from a single result file, and
create and plot stress linearization.
Create and edit user-defined data type expressions, derived load cases, and systems. You can also plot a forming limit
diagram, generate streamlines, track entities during animation, and create and import/export sets of entities.
When an argument is passed as a constant, it is converted to a constant value table by
the Expression Builder.
In order to do so, the argument must meet the following requirements:
The argument is a value table.
The argument is of a specific format (scalar, vector, or tensor).
The argument is bound to a specific entity type.
Operators that accept general value types will not accept constant value arguments.
Examples of operators that fail to meet these criteria are unary operators in the Math
Library (which accept scalar, vector, or tensor types, bound to any entity type). These
restrictions are necessary in order to create a constant value table.
The composite failure theory example below requires five material-bound scalar value tables
in order to function (Xt, Xc, Yt, Yc, and S).
These tables define the allowable stresses in tension, compression, and shear along the
fiber X and Y directions for a given material, and are passed to the Hill Failure Theory
operator below as scalar tables from resource #4 (default arguments not shown):
In cases where tables are not available for an operation and a constant value would
suffice, value tables can be replaced with constants. For the example above, the operator
HillFT could be called as follows (default values not shown):