Radioss Interface
Overview of the Radioss interface.
HyperWorks provides a complete pre-processing environment for preparing Radioss data decks for analysis.
HyperWorks can read existing Radioss decks, create a model, display and edit Radioss cards as they will look in the deck, and write a deck for analysis.
To create Radioss decks in HyperWorks, you must load the Radioss user profile with the appropriate template to access the full pre-processing capability.
Import and Export
- HyperWorks supports Radioss solver versions for import and export till Radioss 2020.
- Solver specific import options are available in the Import Options dialog.
- HyperWorks supports Radioss Dummy models.
- Most IDs in the solver deck are preserved in HyperWorks. If a keyword is not supported in a dedicated HyperWorks entity to ensure its unique ID-Pool, then HyperWorks renumbers those keywords when ID conflicts are detected. The new IDs are posted during the import process.
- The Radioss interface supports a smart, reliable FE input reader that warns you when your input deck contains unsupported fields and unsupported data lines.
- HyperWorks supports undefined entities. These are entity IDs which are referenced in keywords (for example a Material ID in a *PART) but not defined in the deck. In this case, HyperWorks creates a default card (for example a material of type elastic is then created) in order to preserve the ID. This keyword has the Defined checkbox toggled off and is automatically not exported.
Duplicate ID’s
- Several Radioss keywords are mapped to one HyperWorks entity in some instances. By default, the Radioss interface does not allow duplicate IDs within the same HyperWorks entity, with the exception of elements. Radioss does allow duplicate IDs across cards mapped to one HyperWorks entity. In HyperWorks, ID flexibility similar to Radioss can be enabled from the Preferences dialog by selecting the Meshing tab and activating Allow duplicate IDs.
- Duplicate IDs are supported for the following HyperWorks entities in the Radioss user profile: elements, properties, entity sets, and sensors.
Rigid Body Management
Any RBODY created with less than 10000 slave nodes is shown with the spider connecting the master node to the slave nodes. If the RBODY has more than 10000 slave nodes, then it is shown with a single link connecting the master node to one of the slave node. All other options are similar for both.