\section{Pre-deployment simulation notes: 2012\_10\_08\_Daphne\_Turbulence\_09}

\subsection{Primary Mission}

The primary mission for this deployment is:

\begin{verbatim}
Science/turbulence_daphne.xml
\end{verbatim}
Jordan simulated the mission with \verb!bin/LRAUV! built%
\footnote{It is critical to make sure that the most recent revision is
checked out and the application is built using that revision
\emph{before} starting the pre-deployment simulations script.}
from svn repository revision 9940 on his workstation using the
pre-deployment simulation script%
\footnote{The pre-deployment simulation tools are in
\verb!branches/mjs_sandbox! and will be merged back into the trunk
at a later date.}
with the turbulence mission configuration file:

\begin{verbatim}
cd Tools/pre-deployment-simulations  
./run-pre-deployment-simulations.py -i turbulence_missions.ini
\end{verbatim}
![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:

\begin{verbatim}
900739.LRAUV.Data/Testing/2012/2012_10_08_Daphne_Turbulence_09/sims
\end{verbatim}
\subsection{Additional Missions}

Jordan also simulated all Science and Transport missions, using:

\begin{verbatim}
cd Tools/pre-deployment-simulations  
./run-pre-deployment-simulations.py -i standard_missions.ini
\end{verbatim}
A few simulations produced notable results:

\subsubsection{\texttt{Science/drift.xml}}

Produced one error:

\begin{verbatim}
20121010T010909 [VerticalControl]:Can not stop descending, stopping 
mission at depth excursion=10.098091, upwardsErrorDepth_=48.901367, 
depthRate=0.008629
\end{verbatim}
\subsubsection{\texttt{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.)

\begin{itemize}
\item
  trackBox: The trajectory extends North, and looks like it is
  following an isobath (maybe 50 meter?).

\item
  trackBoxTransect: The trajectory just follows the transect.

\item
  trackButterfly: There is no trajectory.

\item
  trackCircle: The trajectory passes over dry land.

\item
  trackCross: The trajectory doesn't really go anywhere.

\item
  trackFigure4: The trajectory doesn't really go anywhere.

\item
  trackPatch: This one actually seems to function without input.

\end{itemize}
\subsubsection{\texttt{Transport/*.kml}}

These missions all simulate as expected.

\begin{center}\rule{3in}{0.4pt}\end{center}

