DIS Steering Committee, The DIS Vision, A Map to the Future of Distributed Simulation, Version 1, Institute for Simulation & Training, May 1994, Orlando, Florida, USA, IST-SP-94-01.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....Both types of simulations have their own background and standards in the military world. The US DoD developed the DIS (Distributed Interactive Simulation) protocol to enable the linking of real time training simulators and ALSP (Aggregate Level Simulation Protocol) for event driven simulations [1, 2]. In 1995 the US DoD initiated the development of a generic framework for distributed 16 XOOTIC MAGAZINE simulations, called the High Level Architecture. Distributed Interactive Simulation DIS (Distributed Interactive Simulation) is a standardised protocol for interconnecting large numbers of ....

DIS Steering Committee, The DIS Vision, A Map to the Future of Distributed Simulation, Version 1, Institute for Simulation & Training, May 1994, Orlando, Florida, USA, IST-SP-94-01.

....protocols constitute the low level basis for distributed simulation, a set of standards and tools at a higher abstraction level is required to enable the timely and effective development of applications. The underlying technical approach of the DIS protocols is based on the following principles [9]: object event architecture: all dynamic entities in the virtual environment inform all other entities of their status and actions through the transmission of standard information packets, so called Protocol Data Units (PDUs) autonomy of simulation nodes: all events caused by an individual ....

DIS Steering Committee: The DIS Vision, A Map to the Future of Distributed Simulation, Version 1, Institute for Simulation & Training, May 1994, Orlando, Florida, USA, IST-SP-94-01

....enables us to suggest reasonable policies for resolving the effects of concurrent interactions. 1. Introduction One of the most significant challenges facing the simulation community is Multi Representation Modeling (MRM) the joint execution of multiple models of the same object or process [8]. The crux of the challenge is resolving concurrent interactions on the representations in the different models [17] Many systems either serialize concurrent interactions or avoid them by restricting the interactions that can co occur. However, serialization and avoidance are insufficient for ....

DIS Steering Committee, The DIS Vision, A Map to the Future of Distributed Simulation, Comment Draft, October 1993.

....for a reconfiguration. These times are all very hardware dependent so we limit ourselves to an order of magnitude analysis. t event is the time the event occurs. t detect is when Bullpen detects that event. With heartbeats, this will average half the heartbeat expiration, measured in seconds. [5] t decide marks the completion of Bullpen s decision process. The elapsed time T decide is the only part that is attributable to Bullpen. Usual values are in hundredths of a second. t reconfig indicates the completion of the reconfiguration. In the best case where the simulation builders ....

DIS Steering Committee. The DIS Vision, A Map to the Future of Distributed Simulation, May 1994. Version 1.

....that are, unfortunately, incompatible with each other. ALSP [Weat93] presents a framework for linking unlike simulations. But a large number of simulations were intended to be stand alone and continue to be so. Increasingly, the view is that different simulations should be able to work together [DIS93]. There have been two initiatives towards this goal. One has been to make existing simulations legacy simulations work together. The second has been to devise standards for all future simulations, wherein interoperability is a requirement and not an afterthought [DoD94] Existing ....

DIS Steering Committee, The DIS Vision, A Map to the Future of Distributed Simulation, Comment Draft, October 1993.

....we briefly review key concepts in DIS and ALSP before describing the HLA. The primary mission of DIS is to define an infrastructure for linking simulations of various types at multiple locations to create realistic, complex, virtual worlds for the simulation of highly interactive activities [DIS94]. A DIS exercise can be viewed as a collection of autonomous simulations each maintaining a virtual environment representing the portions of the battlefield relevant to the entities it is modeling. An exercise may include (1) human in theloop elements such as tank or flight simulators, 2) ....

....in receive order (not time stamp order) to reduce communication latency, sometimes leading to anomalies. Some temporal errors are acceptable because they will not be noticed due to limitations in human perception. Unreliable communication services are often used, again to reduce latency. See [DIS94] for an introduction to DIS, and [Fuji95] for a discussion contrasting DIS and parallel simulation research. ALSP was designed to extend the DIS concept, and focused largely on combining separately developed wargame simulations into federations. Wargame simulations are often referred to as ....

"The DIS Vision, A Map to the Future of Distributed Simulation" Institute for Simulation & Training, Orlando FL, May 1994.

....Simulation Protocol) Weat93] presents a framework for linking simulations at different resolution levels. However, a large number of simulations were intended to be standalone and continue to be so. Increasingly, the view is that different simulations should be able to work together [DIS93]. There have been two initiatives towards this goal. One has been to make existing simulations legacy simulations work together. The second has been to devise standards for all future simulations, wherein interoperability is a requirement and not an afterthought [DoD94] Although the ....

DIS Steering Committee, The DIS Vision, A Map to the Future of Distributed Simulation, Comment Draft, October 1993.

....that also focuses on using a wide array of input data and hardware. AFM93] DoD s Distributed Interactive Simulation (DIS) defines a standard for how VEs interact, but not how to meet that standard. There are tools developed to help developers meet that standard, but not to retro fit existing VEs. Com94] BrickNet uses an interpreted language to facilitate sharing object behaviors between VEs. SSP 95] VRML is also an interpreted language that as of version 1.0 does not support connected VEs. There has been little research on how to retrofit legacy systems into distributed VEs. DPCS96] ....

DIS Steering Committee. The dis vision, a map to the future of distributed simulation, May 1994. Version 1.

....DIS and ALSP before describing the HLA. Distributed Interactive Simulation The primary mission of DIS is to define an infrastructure for linking simulations of various types at multiple locations to create realistic, complex, virtual worlds for the simulation of highly interactive activities [DIS94]. A DIS exercise may include (1) virtual human in theloop elements such as tank or flight simulators, 2) computation only elements such as wargame simulations, and (3) live elements such as instrumented tanks or aircraft. Each simulation advances in time according to a (local) hardware clock. ....

The DIS Vision, A Map to the Future of Distributed Simulation, Institute for Simulation & Training, Orlando FL, May 1994.

....largest implementation of CVEs is the Department of Defense (DoD) distributed simulation program. This program involves a number of architectures and an attempt to develop an architecture that meets all DoD requirements as well as serving other industries such as entertainment and education. 7][2] [12] Understanding these architectures and insuring that we can service them gives us a ready domain to prove our ideas and the opportunity to solve a practical problem. DOMAIN DRIVEN RECONFIGURATION REQUIREMENTS To make the concept of Domain Driven Reconfiguration more understandable we have ....

....application events. It must not only detect those events, but also gather all the preliminary information available. Ideally the Domain Driven Reconfiguration component can detect system events by listening to the application message traffic. This is low cost and unobtrusive. It is common [9] 8] [2] to require each component VE to update its state periodically, and failure to do so indicates a problem. A more expensive but faster technique is to query the VEs regularly. Another technique is to use either mobile or stationary agents that report information or events. This approach generates ....

[Article contains additional citation context not shown here]

DIS Steering Committee. The DIS Vision, A Map to the Future of Distributed Simulation, May 1994. Version 1.

....a wide variety of uses, architectures, and techniques. DoD uses distributed simulation for test and evaluation, analysis, and training. Each of these categories place different requirements on the distributed architecture. Currently DoD has simulations that use a totally distributed approach, [2] [14] but has mandated that all simulations use a middleware approach as defined by the high level architecture (HLA) 9] HLA is designed to support a family of simulations that include aggregate, disaggregate, and component levels of detail as well as discrete and continuous events. System ....

....for a reconfiguration. These times are all very hardware dependent so we limit ourselves to an order of magnitude analysis. t event is the time the event occurs. t detect is when Bullpen detects that event. With heartbeats, this will average half the heartbeat expiration, measured in seconds. [2] t decide marks the completion of Bullpen s decision process. The elapsed time T decide is the only part that is attributable to Bullpen. Usual values are in hundredths of a second. t reconfig indicates the completion of the reconfiguration. In the best case where the simulation builders dedicated ....

DIS Steering Committee. The DIS Vision, A Map to the Future of Distributed Simulation, May 1994. Version 1.

No context found.

DIS Steering Committee, The DIS Vision, A Map to the Future of Distributed Simulation, Version 1, Institute for Simulation & Training, May 1994, Orlando, Florida, USA, IST-SP-94-01.

No context found.

DIS Steering Committee, The DIS Vision, A Map to the Future of Distributed Simulation, Version 1, Institute for Simulation & Training, May 1994, Orlando, Florida, USA, IST-SP-94-01.

No context found.

DIS93 DIS Steering Committee, The DIS Vision, A Map to the Future of Distributed Simulation, Comment Draft, October 1993.

No context found.

DIS93 DIS Steering Committee, The DIS Vision, A Map to the Future of Distributed Simulation, Comment Draft, October 1993.

No context found.

DIS Steering Committee, The DIS Vision, A Map to the Future of Distributed Simulation, Comment Draft, October 1993.

No context found.

DIS Steering Committee, The DIS Vision, A Map to the Future of Distributed Simulation, Comment Draft, October 1993.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC