--- manual/s_getstarted/text/getting_started.tex	2004/04/08 02:24:23	1.23
+++ manual/s_getstarted/text/getting_started.tex	2004/10/13 05:06:25	1.26
@@ -1,4 +1,4 @@
-% $Header: /home/ubuntu/mnt/e9_copy/manual/s_getstarted/text/getting_started.tex,v 1.23 2004/04/08 02:24:23 edhill Exp $
+% $Header: /home/ubuntu/mnt/e9_copy/manual/s_getstarted/text/getting_started.tex,v 1.26 2004/10/13 05:06:25 cnh Exp $
 % $Name:  $
 
 %\section{Getting started}
@@ -324,7 +324,7 @@
 
 \end{itemize}
 
-\section{Example experiments}
+\section[MITgcm Example Experiments]{Example experiments}
 \label{sect:modelExamples}
 
 %% a set of twenty-four pre-configured numerical experiments
@@ -484,7 +484,7 @@
 Once you have chosen the example you want to run, you are ready to
 compile the code.
 
-\section{Building the code}
+\section[Building MITgcm]{Building the code}
 \label{sect:buildingCode}
 
 To compile the code, we use the {\em make} program. This uses a file
@@ -666,17 +666,17 @@
 \end{verbatim}
 
 
-\subsection{Using \textit{genmake2}}
+\subsection{Using \texttt{genmake2}}
 \label{sect:genmake}
 
 To compile the code, first use the program \texttt{genmake2} (located
-in the \textit{tools} directory) to generate a Makefile.
+in the \texttt{tools} directory) to generate a Makefile.
 \texttt{genmake2} is a shell script written to work with all
 ``sh''--compatible shells including bash v1, bash v2, and Bourne.
 Internally, \texttt{genmake2} determines the locations of needed
 files, the compiler, compiler options, libraries, and Unix tools.  It
-relies upon a number of ``optfiles'' located in the {\em
-  tools/build\_options} directory.
+relies upon a number of ``optfiles'' located in the
+\texttt{tools/build\_options} directory.
 
 The purpose of the optfiles is to provide all the compilation options
 for particular ``platforms'' (where ``platform'' roughly means the
@@ -918,13 +918,39 @@
   Sightly more complicated scripts may be needed for many machines
   since execution of the code may be controlled by both the MPI
   library and a job scheduling and queueing system such as PBS,
-  LoadLeveller, Condor, or any of a number of similar tools.
+  LoadLeveller, Condor, or any of a number of similar tools.  A few
+  example scripts (those used for our \begin{rawhtml} <A
+    href="http://mitgcm.org/testing.html"> \end{rawhtml}regular
+  verification runs\begin{rawhtml} </A> \end{rawhtml}) are available
+  at:
+  \begin{rawhtml} <A
+    href="http://mitgcm.org/cgi-bin/viewcvs.cgi/MITgcm_contrib/test_scripts/">
+  \end{rawhtml}
+  {\footnotesize \tt
+    http://mitgcm.org/cgi-bin/viewcvs.cgi/MITgcm\_contrib/test\_scripts/ }
+  \begin{rawhtml} </A> \end{rawhtml}
 
 \end{enumerate}
 
+An example of the above process on the MITgcm cluster (``cg01'') using
+the GNU g77 compiler and the mpich MPI library is:
+
+{\footnotesize \begin{verbatim}
+  %  cd MITgcm/verification/exp5
+  %  mkdir build
+  %  cd build
+  %  ../../../tools/genmake2 -mpi -mods=../code \
+       -of=../../../tools/build_options/linux_ia32_g77+mpi_cg01
+  %  make depend
+  %  make
+  %  cd ../input
+  %  /usr/local/pkg/mpi/mpi-1.2.4..8a-gm-1.5/g77/bin/mpirun.ch_gm \
+       -machinefile mf --gm-kill 5 -v -np 2  ../build/mitgcmuv
+\end{verbatim} }
+
 
 
-\section{Running the model}
+\section[Running MITgcm]{Running the model in prognostic mode}
 \label{sect:runModel}
 
 If compilation finished succesfuully (section \ref{sect:buildingCode})
@@ -1033,7 +1059,7 @@
 >> for n=1:11; imagesc(eta(:,:,n)');axis ij;colorbar;pause(.5);end
 \end{verbatim}
 
-\section{Doing it yourself: customizing the code}
+\section[Customizing MITgcm]{Doing it yourself: customizing the code}
 
 When you are ready to run the model in the configuration you want, the
 easiest thing is to use and adapt the setup of the case studies