8.2 - The Human Entity Behavior Model

Table of Contents

• 8.2.1 Core Elements of Human Entities
• 8.2.2 Component Systems that Make Up a Human Entity
  • 8.2.2.1 A Specific Example: Friendly Dismounted Infantry
  • 8.2.2.2 Systems
  • 8.2.2.3 Other Simulation Components
    • Sensors:
    • Controllers
    • Actuators:

Humans are simulated as platform-level entities in VR-Forces. Examples include friendly and hostile dismounted infantry and civilians./p>

8.2.1 Core Elements of Human Entities

Humans in VR-Forces share certain common elements. A human entity in VR-Forces is always configured with the following:

• DtHumanStateRepository – Holds state information specific to humans
• DtSimIndividualLocalEntityNetInterface – Handles network publishing of individual (platform-level entities)

Because they are members of a military organization, dismounted infantry are also always configured with:

• DtVrfRadio – For enabling radio-like communication between entities in the same unit

8.2.2 Component Systems that Make Up a Human Entity

Humans share many of the same systems and simulation components (sensors, controllers, and actuators). To examine the systems typically configured on a human entity, we'll look at a specific instance of a human, the DI M4 entity. Differences arise between the various types of entities as a function of which particular sub-systems are configured, and the parameter values it is configured with.

For example, a civilian shares the same kinematics model as an Mideast combatant, but it does not include a weapon system.

8.2.2.1 A Specific Example: Friendly Dismounted Infantry

Defined in parameter files Human.ope and DI_M4.entity.

The figure below shows which systems and simulation components are configured as part of a friendly dismounted infantry entity. The boxes (nodes) represent either a system of components (DtComponentSystem) or indivdiual DtSimComponent classes. The edges connecting the boxes indicate port or port group connections between components. Information such as detected targets and control inputs are exchanged between components through ports.

8.2.2.2 Systems

Major sub-elements of an entity's capabilities are organized into systems.

• Lifeform Damage – Determine damage as a result of direct and indirect fire.
• Human Movement – Handle all types of movement behaviors, e.g. route following, turning, stopping, etc.
• Visual-Sensor – What can I see?
• Handheld M16 System – M16 rifle
• Spot-report Receiver – Listen for spot reports.
• Spot-report Generator – Generate spot reports based on what I see.

8.2.2.3 Other Simulation Components

Individual DtSimComponents (not organized as part of a system) that make up the rest of entity.

Sensors:

• DtUnderFireDeterminationSensor – Am I under fire?

Controllers

• DtScriptMultiTaskController – The controller for scripted tasks.
• DtScriptReactiveTaskController – The controller for reactive scripted tasks.
• DtOrganizationController – Maintain my position in the aggregate organizational hierarchy.
• DtLocalEntitySetController – Respond to a DtSetDataRequest, such as set location, set heading.
• DtDIGuyController – Support DI-Guy appearances and animations.
• DtEmbarkationController – Support entity's abiltiy to embark on other entities.
• DtContactFusionController – Fuse contact information from various sources into a single list.
• DtSendRadioMessageController – Send text or task messages through the radio.
• DtTargetSelectionController – Choose target for weapon system.

Actuators:

There are no actuators directly configured as part of this entity.

[<< The Ground Vehicle Entity Behavior Model] [Home] [Top of Page] [The Fixed-wing Entity Behavior Model >>]