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.
Structural properties are meant to be placeholders that hold local information, that can change from one structural
element to another, useful for method evaluation. They usually contain extra information not directly available from
FE entities or results.
The Panel tool recognizes metallic panels or composite panels, which lead to two different configs as the structural
property and method available for these configs are different.
The Rivet tool recognizes rivets modelled as a collection of Shell-1D-Shell patterns. The body between two shells
is made of a single 1D element. However, it detects a rivet as a multi-layered connection.
Besides the creation of structural elements, you can reorganize existing entities in new designpointsets, the aim
being to collect structural elements on which the same set of methods will run (for a given set of loadcases).
Create designpointmethod entities in HyperMesh using a template definition. In such templates, method prototypes are defined as a reference to functions
where input arguments are mapped to attributes in the database.
To run methods on designpointset entities, the methods must first be assigned. Creating methods simply adds new designpointmethod
entities to the database, but no reference is added to any designpointset.
Use the Method Manager dialog to create new methods and populate libraries or import existing libraries from .xml files, as explained in previous chapters.
Designpointmethod entities can be evaluated, looping across loadcases, either directly on a selection of elements
(if valid) or collected in designpointsets.
Each designpointset can have a different set of methods (designpointmethod entities)
assigned to it.
Create Methods
Create designpointmethod entities in HyperMesh using a template definition. In such templates, method prototypes are defined as a reference to functions where input arguments are mapped to attributes in the database.
Assign Methods
To run methods on designpointset entities, the methods must first be assigned. Creating methods simply adds new designpointmethod entities to the database, but no reference is added to any designpointset.
Author Custom Methods
Register new methods and save/import existing libraries. The following chapter, Method Manager, shows these steps in more detail.
Method Manager
Use the Method Manager dialog to create new methods and populate libraries or import existing libraries from .xml files, as explained in previous chapters.
Built-In Library of Methods
By default, HyperMesh comes with a set of methods. These methods are always available even if you register your own custom methods.