Pre-deployment simulation notes: 2012_10_08_Daphne_Turbulence_09
================================================================

Primary Mission
---------------
The primary mission for this deployment is:

    Science/turbulence_daphne.xml

Jordan simulated the mission with `bin/LRAUV` built[^1] from svn 
repository revision 9940 on his workstation using the pre-deployment 
simulation script[^2] with the turbulence mission configuration file:

    cd Tools/pre-deployment-simulations  
    ./run-pre-deployment-simulations.py -i turbulence_missions.ini

![Figure 1: Simulation of Science/turbulence_daphne.xml]
(./201210100049_201212140050.sim.kmz.jpg)

Figure 1 shows the simulation result as viewed in Google Earth. 
There are no faults or failures in the simulation.
The full logs for this mission are in the project library:

    900739.LRAUV.Data/Testing/2012/2012_10_08_Daphne_Turbulence_09/sims

Additional Missions
-------------------
Jordan also simulated all Science and Transport missions, using:

    cd Tools/pre-deployment-simulations  
    ./run-pre-deployment-simulations.py -i standard_missions.ini

A few simulations produced notable results:


### `Science/drift.xml`
Produced one error:

    20121010T010909 [VerticalControl]:Can not stop descending, stopping 
    mission at depth excursion=10.098091, upwardsErrorDepth_=48.901367, 
    depthRate=0.008629


### `Science/track*.kml`
These missions probably failed because the pre-deployment script did not 
provide a target to track. (This is supported, but was not configured.)

* trackBox: The trajectory extends North, and looks like it is following 
  an isobath (maybe 50 meter?).

* trackBoxTransect: The trajectory just follows the transect.

* trackButterfly: There is no trajectory.

* trackCircle: The trajectory passes over dry land.

* trackCross: The trajectory doesn't really go anywhere.

* trackFigure4: The trajectory doesn't really go anywhere.

* trackPatch: This one actually seems to function without input.


### `Transport/*.kml`
These missions all simulate as expected.



-----------------------------------------------------------------------

[^1]: It is critical to make sure that the most recent revision is 
      checked out and the application is built using that revision 
      _before_ starting the pre-deployment simulations script.

[^2]: The pre-deployment simulation tools are in `branches/mjs_sandbox` 
      and will be merged back into the trunk at a later date.