OptiStruct sets are represented in HyperMesh as either entity sets (when composed of integers) or as the control card SET (when composed of real values).
For real value sets, values are manually entered on the control card SET.
For integer sets, represented as entity sets in HyperMesh, the following five different compositions are allowed:
|
1. sets of nodes - |
exported as SET |
|
2. sets of elems - |
exported as SET |
|
3. sets of comps - |
exported as PSET |
|
4. sets of props - |
exported as PSET |
|
5. sets of sets - |
exported as PSET (only sets of comps and sets of props are supported for sets of sets); on export, IDs of the constituent sets will be concatenated. Only one level of hierarchy is supported. |
In addition to the definition of entity sets through the explicit selection of the constituents, it is possible to define a set of nodes or a set of elements through a combination of formulaic expressions.
|
OptiStruct Keyword |
Notes |
|
SET |
Sets of integer values are supported as entity sets. When reading input decks that do not have HyperMesh comments, HyperMesh attempts to create two sets for each set found (a node set and an element set). Set references are updated appropriately. Unnecessary sets can then deleted by the user after import. Sets of real values are supported as the control card SET. |
|
PSET |
Supported as entity sets. When reading input decks that do not have HyperMesh comments, HyperMesh attempts to create three sets for each set found (a component set, a property set and a combined set of these sets). References are updated appropriately. Unnecessary sets can be manually deleted after import. |
|
Note: |
Sets that are created in HyperMesh are maintained on I/O by using $HMSET comment cards. |
How do I…
Go To
Interfacing with Altair HyperMesh