Group: Mission Control

Total Lines of Code: 19,458

Total Files of Code: 123

Total Work Years: 4.01

Group Description: (16 modules)

The Mission Control modules are run-time modules for either direct monitoring and control of the mission (e.g., pMarineViewer), or for passively scoping the mission (e.g., uXMS, uMS, uHelmScope, uQueryDB, uFunctionVis, uMAC, uMACView, uLoadWatch, uProcessWatch), or for injecting messages to one or more vehicles, (e.g., uPokeDB, uTermCommand). The common theme is that they are run-time modules for either scoping or injecting changes in the missions, or both.

Documentation:

Distribution:

  • moos-ivp.org

Modules:

  • MOOSMobile: Cross-platform mobile app for communication with MOOS.
  • iSay: Invokes system text to voice upon postings to the MOOSDB.
  • pMarineViewer: Mission control GUI for monitoring, deploying and commanding vehicles.
  • pRealm: Shadow the local MOOSDB and support RealmCasting requests.
  • uFunctionVis: A GUI based MOOS App for monitoring IvP Helm objective functions.
  • uHelmScope: A terminal based MOOS App for monitoring the state of IvP Helm.
  • uLoadWatch: A utility for monitoring the load of MOOS Apps.
  • uMAC: A terminal based MOOS app for monitoring appcasts.
  • uMACView: A GUI based MOOS app for visually monitoring appcasts.
  • uMemWatch: A MOOS app for monitoring the memory usage of other apps.
  • uProcessWatch: A MOOS app for monitoring the presence of other MOOS apps.
  • uQueryDB: A command line app, connect to MOOSDB, check condition, then exit.
  • uTermCommand: A terminal MOOS app for poking the MOOSDB with pre-configured pokes.
  • uXMS: A command line app for scoping the MOOSDB.
  • lib_ipfview: A library with classes to support the rendering of IvP Functions.
  • lib_ucommand: A library for supporting CommandFolios - mission control pre-defined sets of commands.