This section describes the Engineering Solutions RADIOSS interface. Engineering Solutions provides a complete pre-processing environment for preparing RADIOSS data decks for analysis. Engineering Solutions 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. Although Engineering Solutions also offers limited post-processing capabilities in results translation you are strongly encouraged to exclusively use HyperView. To create RADIOSS decks in Engineering Solutions, you must load the RADIOSS user profile with the appropriate template to access the full pre-processing capability.
The following are general comments about the Engineering Solutions Interface for RADIOSS.
Import and Export
|
| • | The RADIOSS (Block Format) interface supports RADIOSS (Block Format) version 14.0 |
|
|
| • | The RADIOSS input translator can read solver decks with separate starter and engine file in the same folder or both starter and engine in one file. Also it can read separately starter and engine files. Use the Solver Options tab in the Import tab to enable reading both engine and starter information placed in separate files. |
| • | During export, the starter and engine files can be exported separately or merged as one file turning on corresponding check box in the Export tab. |
| • | The RADIOSS interface in HyperMesh does not support RBODY definitions that are defined using GRNOD/BOX. Therefore, upon import they will be realized into sets GRNOD/NODE and exported with corresponding set. |
|
|
| • | Although the majority of RADIOSS keywords are supported, any existing unsupported material and property in the deck are read into HyperMesh and exported maintaining its associative. All other unsupported portions of the deck are mapped to unsupported cards in HyperMesh and are appended at the end of deck during export. |
|
| • | Most of IDs in the solver deck are preserved with introduction of ID pool concepts in HyperMesh. However solver cards mapped to load collectors, groups, sensors, and airbags are renumbered if there is a conflict of ID among the keywords mapped to a HyperMesh entity. The new IDs are posted during the import process. |
|
| • | RADIOSS keywords GRNOD,GRSHEL, GRSH3N,GRBRIC,GRBEAM, GRTRUSS, GRSPRING are mapped across two HyperMesh entities, namely entity sets and blocks. To avoid duplicate IDs in the deck, keywords mapped to the block entity are renumbered during export. |
| • | RADIOSS solver interface does not support positioning of dummies. |
|
|
|
Duplicate ID’s
|
| • | Several RADIOSS keywords are mapped to one HyperMesh entity in some instances. By default the RADIOSS interface does not allow duplicate IDs within the same HyperMesh entity, with the exception of elements. RADIOSS does allow duplicate IDs across cards mapped to one HyperMesh entity. In HyperMesh, ID flexibility similar to RADIOSS can be enabled by switching on the Duplicate ID option in the Preferences menu. |
| • | Duplicate IDs are supported for the following HyperMesh 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. |
|
|
Mass Calculation
|
| • | The mass of each element is calculated by density * volume. Density is retrieved from the material associated with the element’s component. Currently mass calculation for RBODY, RBE3, RBE2 is not supported. |
|
See Also:
Model browser
Solver browser
Connector browser
Include Files
Using the RADIOSS Utility menu
Supported RADIOSS Keywords
Unsupported RADIOSS Keywords
Solver Conversion
