Browsers supply a great deal of view-related functionality by listing the parts of a model in a tabular and/or tree-based
format, and providing controls inside the table that allow you to alter the display of model parts.
FE geometry is topology on top of mesh, meaning CAD and mesh exist as a single entity. The purpose of FE geometry
is to add vertices, edges, surfaces, and solids on FE models which have no CAD geometry.
Tools and workflows that are dedicated to rapidly creating new parts for specific use cases, or amending existing
parts. The current capabilities are focused on stiffening parts.
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.
Operators are designed such that they must be passed to all of
the necessary tables and arguments in order to function. They are stateless and have no access
to the tables in the model, or result, or the relationship between. This design maximizes
their maintainability and flexibility and enables them to operate on any valid input, with the
only restriction being that the arguments fulfill the requirements of the operator. The side
effect of this design is that argument lists can be lengthy. In order to mitigate this,
Operators and the Expression Builder populate as many arguments with default values as
possible.
When an operator is inserted into the expression, the defaulted argument list is
hidden:
In the example above, a failure theory operator is inserted, however since the
Hide Default Arguments is checked, only the parameters that do not have a default value are
shown. This mode effects how the operator will be inserted into the expression text, and
will not change any existing text. An expression can consist of Operators that have default
values shown, in addition to ones that have default values hidden. Additional arguments can
be added to the inserted Operator, by simply adding a comma-separated list of parameters.
The Operator above will appear as follows with the Hide Default Arguments option
deactivated: