\documentclass[onecolumn,letterpaper,11pt]{article}

%===================================================================
\input{common_latex/common_latex_packages}
\input{common_latex/common_latex_definitions}
\input{common_latex/common_latex_memo_format}
%===================================================================

\begin{document}

\begin{labcover}
\labtitle{Mission Structure, Launching and Automated Testing}
\vspace{0.1in}
\labdate{January 2025}
\vspace{0.1in}
\labauth{Michael Benjamin, mikerb@mit.edu}
\labauth{Department of Mechanical Engineering}
\labauth{MIT, Cambridge MA 02139}
%\labtoc{small}
\end{labcover}

\wikidoc{file=Memo.VVIntro}
\wikidoc{auth=mikerb@mit.edu}
\wikidoc{toc=false}

%==================================================================
\section{What is a Mission?}
%==================================================================

A mission, for one or more autonomous marine vehicles, is comprised of
a set of goals, constraints and contingencies to be carried out by the
vehicles to achieve one more more objectives. Traditional missions
include a simple mission such as transiting through a series of
waypoints to a destination, or searching a body of water with a
sensor-equipped vehicle to determine number and location of objects of
interest. Mission can also include a more non-deterministic structure
defined more by a set of vehicle modes and conditions for transitioning
between mode based on sensed events, or communications from other
vehicles or operators.

\vspace{0.1in}
\noindent
For the purposes of discussion here, the concern is more about the
mission configuration structure and launch mechanics. These aspects will
be relatively consistent across our missions, even if the goals and behaviors
of vehicles may vary widely as allude above.


\vspace{0.1in}
\noindent
One common notion is the {\em mission topology}. At a high level, a mission
is structured with the idea that there may be one or more vehicles, each in
communications with an operator with access to software for providing both
situational awareness, as well as some level of command authority over the
vehicles.


\vspace{0.1in}
\begin{figure}[ht]
  \centering 
  \includegraphics[width=0.4\textwidth]{figures/ufield.png}
  \caption{{\bf The SockNinja Utility}: Applications needing to
    interface over a socket can use the SockNinja to facilitate
    socket configuration and I/O over the connected socket.}
\label{fig_ufield}
\end{figure}



\end{document}



