MUSIM Documented as Individual Processes and Libraries

MUSIM Core Processes

Flight Models

MUSIM currently supports two math models. A fixed wing flight   tfwsim   model and a rotorcraft model   simpleHeli  . Each math model spawns a process that controls one air vehicle. Multiple flight vehicles results in a separate process for each. Combinations of fixed wing, live (both air and ground have been integrated in the past) and rotorcraft vehicles are permissible and encouraged.



mapview

The   mapview   process opens a window on the desktop and displays a 2D map of a pre-defined gaming area.



Operator Input

The MUSIM operator uses a hand operated device to control the MUSIM sensor and the multi-function display. We are currently using a 3Dconnexion   SpaceExplorer   .  In the past, we have used 3Dconnexion   spaceball5000 and a BG Systems   Flybox , both of which are included here for the sake of completeness.



muChat

The   muChat   process was developed to mimic an IRC application, such as the open source xChat .   MuChat uses TCP comms to communicate with one or more chat clients.   There is no chat server   deamon   required, as there would be if using xChat or mIRC a commercial equivalent.



mfd

The   mfd   process opens a window on the desktop and displays a 2D multi-function display .   Several pages are selectable via the mouse, enabling the operator to manipulate the specific simulation and the components involved therein.



sensor

The   sensor process opens a window on the desktop and simulates a flying camera.



super

The   super process is the MUSIM executive. The super process performs network initialization, scenario initialization and real time control, data collection and process synchronization.





MUSIM Library Utilities






network

The   network library documentation has all the methods, classes and variable definitions required for any TCP or UDP messages using the MUSIM protocol.



metaFlight

The   metaflight library documentation has all the methods, classes and variable definitions required for parsing a meta flight file and loading the data base tiles as specified.



utility

The   utility library documentation has all the methods, classes and variable definitions required for functionality that is global in use or doesn't fit elsewhere.





External MUSIM Communications






AUSIM Server

The   AUSIM Server documentation has all the methods, classes and variable definitions required to support communications between MUSIM and the Ausim 3D Sound server.   The Ausim server provides an API and is linked to the calling application. MUSIM uses its' super process to compile and link the Ausim API calls. &nbs;The documentation is included here because the Ausim server is a third party app and is an optional feature for MUSIM that is enabled/disabled thru the use of software switches in the MUSIM super process.   It does not show up in the 3rd party Comms diagram above because it is not an independent process, but rather is linked to the calling app.



CDTI Server

The   CDTIServer process documentation has all the methods, classes and variable definitions required to support communications between MUSIM and the CDTI simulation.   The CDTI simulation is the desktop simulation developed by the folks here at NASA Ames in bldg. 262, that models an airspace control environment. CDTIServer sends data received from MUSIM to the CDTI simulation



clawComms

The   clawcomms process documentation has all the methods, classes and variable definitions required to support communications between MUSIM and the CLAW simulation of the Autonomous Rotorcraft Project (ARP)   RMAX.   This process was developed for the circa 2009 DELCON Demonstration.   ClawComms sends and receives data to/from the CLAW math model.



pspeakComms

The   pspeakcomms process documentation has all the methods, classes and variable definitions required to support communications between MUSIM and the pspeak voice recognition app developed by the folks at WPAFB .   This process was developed for the circa 2009 DELCON Demonstration.   pspeakComms sends and receives data to/from the pspeak process.



rtComms

The   rtComms process documentation has all the methods, classes and variable definitions required to support communications between MUSIM and the RIPTIDE   rotorcraft simulation developed by the folks at AFDD .   The rtComms process sends and receives data to/from the Riptide simulation.



VRLinkComms

The   VRLinkComms process documentation has all the methods, classes and variable definitions required to support communications between MUSIM and the VRLink   cots scenario generation tool.   VRLinkComms sends and receives data to/from the VRLink   simulation.

V1.0