Advanced 3D Network Visualizer Settings and Optional Cosimulation
The following combinations relate to the architecture used in the API document, with the core Ovis API and the DES/GUI accessors. The DES accessor library works with the combination of 3D Network Visualizer and the High-Level Architecture functionality in a simulation.
3D Network Visualizer and Other Cosimulations
For the 3D Network Visualizer and other cosimulations:
- 3D Network Visualizer processing does not require any special ESA invocations. Thus, it can be combined with user-defined cosimulations.
- Appropriate HLA processing takes place between events to ensure that 3D Network Visualizer communicates correctly with the 3D display.
3D Network Visualizer without High-Level Architecture
3D Network Visualizer, when used without High-Level Architecture functionality, has the following characteristics:
- Simulation running in the cosimulation mode
- No esys module is needed in the network model
- HLA events received by the Riverbed application are handled by 3D Network Visualizer and do not result in esys interrupts
- Most preferences used for High-Level Architecture functionality are still applicable
- The same HLA preferences used for High-Level Architecture functionality are still applicable
- In particular, the “3dnv.federation_name” preference overrules the “HLA Federation Name” and the “HLA FED File Name” preferences
3D Network Visualizer and High-Level Architecture
The 3D Network Visualizer and High-Level Architecture functionality together have the following characteristics:
- Simulation running in cosimulation mode
- The esys module will receive interrupts when HLA events arrive at the simulation, allowing it to optionally process those events
- By default, the esys module uses HLA cosimulation process model
- HLA settings are controlled by the High-Level Architecture and 3D Network Visualizer preferences, with 3D Network Visualizer taking precedence. In particular, the “3dnv.federation_name” preference overrules the “HLA Federation Name” and “HLA FED File Name” preferences.
3D Network Visualizer and High-Level Architecture Interaction in Discrete Event Simulation
3D Network Visualizer is based on MÄK’s VR-Link, which in turn relies on an HLA RTI. Similarly, the Riverbed application can be viewed as an HLA federate using the High-Level Architecture functionality and the cosimulation infrastructure.
RTI Issues
The Riverbed application uses RTI to render two types of 3D objects:
- RTI objects whose type is mapped to some 3D model (tank, plane)
- 3D geometric objects (lines, text, spheres, etc.)
The Riverbed application creates the second group and passes it only to the viewer using the “control PDU” interaction. On the other hand, the first group corresponds to well-defined RTI entities in the RPR-FOM. This means that any entity created by DES not only is discovered by the viewer (which then can render it appropriately), but also by any other HLA federate in the federation. Later changes to such an entity (for example, position) are going to be broadcast to all federates. Furthermore, it is possible that the other federates are going to create similar entities. These entities will be discovered by 3D Network Visualizer and, potentially, DES.
One advantage of this architecture is that other federates can contribute to the 3D scene without support from DES. Thus, the user can have combat features (such as missiles, explosions, and tracers) that originate from other federates besides DES. However, this also means that DES should be able to discover any such RTI objects created by other federates and use these objects appropriately. This includes mapping the external RTI objects to DES sites instead of creating duplicate RTI objects. This includes using the external object position instead of generating the positions from DES.
RTI Callbacks
An HLA communication process has three important elements:
- Processing time must be provided to the RTI to check for incoming messages. In the case of the MÄK or DMSO RTI, this means that the ‘tick()’ API must be invoked regularly.
- Time advances for time-constrained federates (typically the case for DES) are done by requesting a time advance and waiting for the grant.
- All input handling is done using callbacks provided by client code, but callbacks can NOT reinvoke the RTI.
3D Network Visualizer and High-Level Architecture Preferences
Riverbed analysis software uses the High-Level Architecture functionality for its communications with 3D Network Visualizer. This is independent of the High-Level Architecture functionality, which allows process models to generate HLA events and to react to incoming HLA events. Because of the common underlying HLA layers, however, name references and simulation behaviors depend on which modules are in use.
High-Level Architecture Configuration Preferences
Note: The GUI also uses HLA, but it uses a much smaller set of preferences because most of the HLA settings are hard-coded.
Table 1: High-Level Architecture Configuration Preferences
| Name | Type | Default | Purpose |
|---|---|---|---|
| HLA Callback Set | integer | 0x7FFFFFFF | Bit pattern indicating which RTI events are notified to the process model handling HLA esys events. See hla_cosim_events.h for details. |
| HLA Create Init Synchronization Point | toggle | FALSE | To block before generating RTI messages to wait for other federates. |
| HLA Fed File Name | string | “” | Name of .fed file used by the RTI. “” means same as federation. |
| HLA Federate Name | string | “” | Name of the application process |
| HLA Federation Name | string | “” | Shared by all federates. Ignored if 3dnv_stealth_hostname is defined. |
| HLA Init Synchronization Point | string | “” | To block before generating RTI messages to wait for other federates. |
| HLA Join Attempts | integer | 10 | Tries before giving up. |
| HLA Time Constrained | toggle | TRUE | If constrained, the application time cannot be ahead of global time. |
| HLA Time Lookahead | double | 1e-9 | Minimum delta between current time and time of scheduled events |
| HLA Time Regulating | toggle | TRUE | If regulating, global time can advance only when the application allows it. |
| HLA Verbose | toggle | FALSE | Generate additional messages |