/EXTERN/LINK in the Starter input file defines the interfaces between the current model and other domains. It is specific to Multi-Domain Multiple Input (available as of version 9.0).
The number of external links in RADIOSS model is not limited. The only restriction is that different links should not contain common nodes. Each link defines a distinct interface between current model and external world.
The links do not specify the corresponding domains. Each model is independent and may be replaced by another one having the same frontier nodes. This approach allows a modular approach to modeling, for example testing runs with equivalent domains with different mesh size (multigrid approach).
The Master program is launched at the following command prompt:
> rad2rad “input_file”
The Master Input file is a text file defining all RADIOSS domains and cross-connections (interfaces links) between them. The syntax is similar to RADIOSS. Comments are admitted – comment lines must begin with # character.
Groups |
Keywords |
Description |
---|---|---|
Multi-Domain Multi Input File Format |
Specifies the RADIOSS model name and the list of external links defined in its Starter input deck. |
|
Defines the interfaces between the current model and other domains in the Starter input deck. |
||
It has to be set at the end of the Multi-Domain. |
||
Defines the type of connection used and the interface cross-references between specified domains. |
||
Defines the space of Lagrange multipliers in the case of incompatible meshes. |
||
Activates the multi-scale time step option, which allows each domain to use its own time step. |
||
Specifies the RAD2RAD printout frequency. |
||
Specifies the number of Processors used by the RAD2RAD executable. |
||
Specifies the value of the search radius. |
||
Specifies the value of the timeout parameter for the establishment of the connection between RAD2RAD and RADIOSS Engine. |
To activate multi-domain coupling, the RADIOSS Engine input file must contain /RAD2RAD/ON.
See Also:
RD-3160: Setting up Multi-Domain Analysis using HyperCrash