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.
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.
Constant value tables are created from the Constant operator in the Math
library.
When performing operations on value tables using
binary operators, it is sometimes necessary to do so with a constant value. Constant value
tables have the following properties:
All record lookups will return a value, regardless of the ID.
The number of records in a constant value table is 0.
The following snippet demonstrates the usage of a constant value table:
For every record contained in the table in “A”, a scalar quantity of 4.0 will be
returned from the table “econst” with a matching ID. Supporting constant values in this way
allows constant value tables to be interchangeable with “resource” value tables. Constant
value tables are widely used with binary operators, and will fail if passed as both the
lhs and rhs parameters due to the fact that there
are no records.
Important: Constant value tables must always operate with
non-constant value tables in binary operations.