Chapter 13. Support for DIS Protocol

Table of Contents

13.1. Introduction
13.2. Configuring DIS
13.2.1. Network configuration
13.2.2. Configuring the launch of an external simulator
13.2.3. Giving Debrief an identity
13.2.4. Filtering DIS traffic
13.3. Monitoring a DIS simulation
13.3.1. Running a local simulator
13.3.2. Interacting with a DIS simulation
13.3.3. Other settings
13.3.4. Logging DIS messages
13.3.5. Performance graph
13.4. DIS Tips & Tricks
13.4.1. Specifying format parameters in advance
13.4.2. Running Debrief's DIS simulator
13.4.3. Track the simulator using the Console

13.1. Introduction

One group of users employ Debrief for the analysis of scenario results from a headless simulation engine. The simulation engine produces results data in a range of output formats. Historically the users had to convert an existing output format to Debrief .rep format, but in the late 2000s direct support for Debrief was added.

In 2015 this body of users recognised the utility of using Debrief as a live simulation monitor, to bring these benefits:

  • Verify scenario participants behave as predicted before committing to lengthy Monte Carlo block of simulation runs

  • Develop the behaviour of one or more scenario participants in a programming-like CODE-RUN-DEBUG cycle

The DIS standard was adopted for network communications between Debrief and the headless simulation engine: .

You can find System documentation for the DIS integration later in this document (Chapter 20, System Documentation for DIS integration)