<html><head><meta name="color-scheme" content="light dark"></head><body><pre style="word-wrap: break-word; white-space: pre-wrap;">%===================================================================
\subsection{The Helm Behavior Directory Path is Important in this Lab!}
\label{sec_bhv_dir}

This missions in this lab involve a new behavior, \var{BHV\_Scout}. Initially
this behavior will be the straw-man version we provide. Then you will provide
your own. The IvP Helm behavior directory path is important not to overlook
in this lab!

\vspace{0.1in}
\noindent
The straw-man version of this behavior resides in the
\var{moos-ivp-2680} tree. As part of this lab you will make a copy of
this behavior in your \var{moos-ivp-extend} tree.

\vspace{0.1in}
\noindent
So - You will need to augment your \var{.bashrc} file to augment the
\var{IVP\_BEHAVIOR\_DIRS} to the following:

\vspace{0.1in}
\begin{fileverb}
IVP_BEHAVIOR_DIRS=:~/moos-ivp-pavlab/lib
IVP_BEHAVIOR_DIRS+=:~/moos-ivp-2680/lib       (comment this out when you have your own)
IVP_BEHAVIOR_DIRS+=:~/moos-ivp-extend/lib

export IVP_BEHAVIOR_DIRS
\end{fileverb}

\vspace{0.1in}
\noindent
Note: you do not need to include the \var{lib/} folder from the \var{moos-ivp}
tree. Behaviors in MOOS-IvP are compiled to be part of the \app{pHelmIvP} app.
Behavior not distributed with MOOS-IvP, such as in this class, are compiled to
be dynamic libraries (MacOS term), a.k.a., shared libraries (Linux term). They
are linked (loaded) at run time to be part of the helm.

\vspace{0.1in}
\noindent
Note: The helm will not complete its startup process if it detects a
behavior of the same name in two locations in the
\var{IVP\_BEHAVIOR\_DIRS}. That may happen in this lab since the
\var{BHV\_Scout} behavior exists in the \var{moos-ivp-2680} tree, and
then you will make your version in your \var{moos-ivp-extend}
tree. Using the same name has its benefits since it allows us to have
a common mission \var{meta\_vehicle.bhv} file.


</pre></body></html>