This page describes the organization of the new missions directory located in ivp-extend/missions and how the files there should be used when creating your own mission. The new arrangement should make it easier for all missions to share some common plugs and configuration parameters, reducing the need to update multiple missions when serial ports change, etc.
trunk
This is the main missions directory, where the standard missions, plugs, and configurations are stored.
plugs
Default plugs for shore, vehicle, and simulation are located in this directory. Meta files should include plugs from this directory to easily inherit any changes.
config
There are just two files in this directory, "hard_config" and "soft_config". These are not MOOS files, but standard bash files that should be sourced by the launch script. hard_config includes definitions for IP addresses, port number, serial ports, and other 'hard' configuration parameters. All missions should use this file.
soft_config includes 'soft' configuration parameters such as return locations, rudder offsets, and cruise speeds. These are parameters you may want to change in your own missions, in which case you should either rewrite these parameters in your own launch script or include your own copy of this file.
baseline folders
These are the standard mission configurations. Each includes scripts for launching the mission and the meta files for simulation, shoreside, icarus, and vehicles.
baseline_uFld - the standard mission, using uFld to configure variable sharing between communities.
baseline_pShare - currently preferred, uses single variable pShare configuration to avoid the communications overhead imposed by uFld.
baseline_pShare_wild - similar to baseline_pShare, but uses wildcard shares to simplify the sharing configuration. Should not be used until a newer version of MOOS with updated wildcard handling makes its way to the kayaks.