The averaging options allow you to limit the averaging of results to only a group of elements that are considered to be
bound by same feature angle or face.
The Free Body Diagram (FBD) tool facilitates the extraction and post-processing of Grid Point Force (GPFORCE) results
and can be used create and edit Free Body Diagrams (FBD).
Starting in version 2021, the Stress Linearization tool has been renamed as Extract-Linearize and will support both the
Extract Data and Stress Linearization methods.
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.
The fatigue manager allows you to write stress and strain results from a finite element analysis to an external file that
can be used to set up a fatigue analysis.
The fatigue configuration file is a user-defined external ASCII-file through which the data groups from results of static/modal/transient analysis of different solvers can be read.
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.