Changeset 3244 for inundation/parallel

Timestamp:

Jun 27, 2006, 2:20:08 PM (18 years ago)

Author:

jack

Message:

Updated section re: running the code.

File:

• inundation/parallel/documentation/parallel.tex (modified) (3 diffs)

inundation/parallel/documentation/parallel.tex

@@ -144 +144 @@
 
 The first example in Section \ref{subsec:codeRPA} solves the advection equation on a
-rectangular mesh. A rectangular mesh is highly structured so a coordinate based decomposition can be use and the partitioning is simply done by calling the
+rectangular mesh. A rectangular mesh is highly structured so a coordinate based decomposition can be used and the partitioning is simply done by calling the
 routine \code{parallel_rectangle} as shown below. 
 \begin{verbatim}
@@ -252 +252 @@
 \section{Running the Code}
 \subsection{Compiling Pymetis and Metis}
-Currently, Metis and its Python wrapper Pymetis are not built by the
-\verb|compile_all.py| script. A makefile is provided to automate the build
-process. Change directory to the \verb|ga/inundation/pymetis/| directory and
-ensure that the subdirectory \verb|metis-4.0| exists and contains an
+Unlike the rest of ANUGA, Metis and its Python wrapper Pymetis are not built
+by the \verb|compile_all.py| script. A makefile is provided to automate the
+build process. Change directory to the \verb|ga/inundation/pymetis/| directory
+and ensure that the subdirectory \verb|metis-4.0| exists and contains an
 unmodified Metis 4.0 source tree. Under most varieties of Linux, build the
 module by running \verb|make|. Under x86\_64 versions of Linux, build the
@@ -262 +262 @@
 that the module works by running the supplied PyUnit test case with
 \verb|python test_metis.py|.
+\subsection{Running the Job}
+Communication between nodes running in parallel is performed by pypar, which
+requires the following:
+\begin{itemize}
+\item Python 2.0 or later
+\item Numeric Python (incling RandomArray) matching the Python installation
+\item Native MPI C library
+\item Native C compiler
+\end{itemize}
+Jobs are started by running appropriate commands for the local MPI
+installation. Due to variations in MPI environments, specific details
+regarding MPI commands are beyond the scope of this document. It is likely
+that parallel jobs will need to be scheduled through some kind of queuing
+system. Sample job scripts are available for adaptation in section
+\ref{sec:codeSJ}. They should be easily adaptable to any queuing system
+derived from PBS, such as TORQUE.