4.4 - Managing Local and Remote Simulation Objects

As described in 3.2.1 How the Object Manager Chooses an Object's Subcomponents, each VR-Forces application has its own Object Manager.

When the Object Manager creates a new simulation object (through the createAndInitVrfObject() function), it looks up the entry in the object parameter database for the object type to be created, and uses this data to direct the construction of the object.

For example, the following is an excerpt of the M1A2 entry from the object parameter database. It shows the local and remote objects lists.

(M1A2
   (parameter-type "ground-vehicle-param")
   ...
   (local-objects
      (state-repository  "ground-entity-state-repository")
      (state-repository-min-tick-period  -1.000000)
      (state-repository-min-tick-period-variance  -1.000000)
      (net-interface  "individual-local-entity-net-interface")
      (net-interface-min-tick-period  -1.000000)
      (net-interface-min-tick-period-variance  -1.000000)
      (task-manager  "local-task-manager")
      (component-manager  "component-manager")
      (plan-manager  "vrfobject-plan-manager")
   )
   (remote-objects 
      (state-repository  "vrf-moving-object-state-repository")
      (state-repository-min-tick-period  -1.000000)
      (state-repository-min-tick-period-variance  -1.000000)
      (net-interface  "vrf-individual-remote-entity-net-interface")
      (net-interface-min-tick-period  -1.000000)
      (net-interface-min-tick-period-variance  -1.000000)
      (task-manager  "")
      (component-manager  "")
      (plan-manager  "")
   )
)

Note

For remote objects simulated by non-VR-Forces applications, only the state repository and network interface subcomponents are created.

[<< Creating a Simulation Object] [Home] [Top of Page] [The Organization Manager >>]