opm-simulators/doc/handbook/install.tex

\section{Installation of \Dumux} \label{install}
\subsection{Preliminary remarks}

In this section about the installion of \Dumux it is assumed that you work on a UNIX compatible operating system and that you are a familiar with the use of a shell. Moreover, you should know,  if necessary, how to install
new software packages or you should have a person aside which can give you assistance with the shell and
the package installation. At the end of this chapter, we list some basic prerequesites for running \Dune and \Dumux. Please check this paragraph to evaluate whether it is possible for you to run \Dune and \Dumux.

In a technical sense \Dumux is a module of \Dune. The installation procedure of \Dumux is strongly related to 
that of \Dune.  Thus, for details of the installation please check also the {\Dune} website \cite{DUNE-HP}. If you are interested in more details of the build-system we refer to the {\Dune}-Build-System-Howto \cite{DUNE-HP}.

As in a \Dune installation, all \Dune modules including the modules for \Dumux as \texttt{dumux} should be extracted into a common directory named {\Dune}-ROOT. Each \Dune module is associated with a directory name in {\Dune}-ROOT. For convenience, this directory name is  also used as an alias for the module name, a practice we will follow here, too.
After installing source code for all requirered \Dune modules including the \Dumux parts
\Dune is being build by the shell-command \texttt{dunecontrol} which is part of {\Dune}-Build-System. The {\Dune}-Build-System is essentially a frontend of the gnu tool autoconf which was specialized for the \Dune project.

\paragraph{Basic prerequisites} \label{prerequisites}
The gnu toolchain of \texttt{g++}  and related gnu variants of developertools like \texttt{libtool}, \texttt{make} and
and \texttt{automake} must be available in a recent version.

\subsection{Obtaining \Dune and \Dumux}
Two possibilities exist to obtain \Dune and \Dumux. They can be obtained as so-called tarballs, i.e. \Dumux and \Dune code files of a certain version are packed into tar-archive files for download from the the respective {\Dune} and {\Dumux} website. The shell command \texttt{tar} can be used to extract them on your filesystem. This is explained in the next paragraph. 

\paragraph{Obtaining the software by installing tarballs}
Download the tarballs from the website. You can install the obtained tarballs as follows: Create a \Dune-Root-directory, which we call here DUMUX. For the installation in the shell, type the following commands: 
\begin{itemize}
\item \texttt{mkdir DUMUX}
\item \texttt{cd DUMUX}
\item \texttt{tar xzvf path\_to\_tarball\_of/pde-lab.tar.gz}
\item \texttt{tar xzvf path\_to\_tarball\_of/dumux.tar.gz}
\item \texttt{tar xzvf path\_to\_tarball\_of ...}
\item \texttt{...}
\end{itemize} 

\paragraph{Obtaining \Dune and \Dumux from the SVN repositories} 
The other possibility is to directly access the project archives of \Dune and \Dumux, the so-called software repositories. These are archives of a software version control system named apache subversion. From here on this is referred to as subversion.
You need a subversion client, with which you can access the repositories. This comes with a usual UNIX distribution or can be installed. Our description is limited to a standard subversion shell client realized by the shell command \texttt{svn}.

\paragraph{Checkout of the core modules}
From version 2.0 of \Dune on, it was decided to stick to stable \Dune releases, comprising the core modules 
\texttt{dune-common}, \texttt{dune-grid}, \texttt{dune-istl}, \texttt{dune-localfunctions} and the external \texttt{dune-pdelab}.  
First, create a directory (here, we call it DUMUX) where all the \Dune and \Dumux modules will be stored in. Then, enter the previously created folder and checkout the modules. Checkout means that you get a working copy of the code from the software repository. 
The checkout has to be performed as described on the \Dune webpage, \cite{DUNE-HP}. For the installation in the shell, type the following commands:
\begin{itemize}
\item \texttt{mkdir DUMUX}
\item \texttt{cd DUMUX}
\item \texttt{svn checkout https://svn.dune-project.org/svn/dune-common/releases/2.0 dune-common}
\item \texttt{svn checkout https://svn.dune-project.org/svn/dune-grid/releases/2.0 dune-grid}
\item \texttt{svn checkout https://svn.dune-project.org/svn/dune-istl/releases/2.0 dune-istl}
\item \texttt{svn checkout https://svn.dune-project.org/svn/dune-localfunctions/releases/2.0 dune-localfunctions}
\item \texttt{svn checkout https://svn.dune-project.org/svn/dune-pdelab/branches/2.0snapshot dune-pdelab}
\end{itemize} 

Additionally, it is highly recommended that you also checkout the \texttt{dune-grid} HOWTO by 
\begin{itemize}
\item \texttt{svn checkout https://svn.dune-project.org/svn/dune-grid-howto/releases/2.0 dune-grid-howto}
\end{itemize}
and work yourself through that tutorial in order to get an understanding of the Dune grid interface. 

\paragraph{Checkout of \Dumux}

In order to access an anonymous read-only copy of the stable part of \Dumux from the reposoitory, the most simple way is to type
\begin{itemize}
\item \texttt{svn checkout --username=anonymous --password='' \\ 
svn://svn.iws.uni-stuttgart.de/DUMUX/dumux/trunk dumux}
\end{itemize}
% On the subversion repository, the \Dumux project is divided into a stable and a developers part, which should stay in separate folders

If you also want to commit new developments to the repositories, you can ask the \Dumux project leader to get developers access fully or in some certain parts. The developer part is only available to people which belong to the \Dumux developer group and have non-anonymous access. If you have developer rights the checkout looks as follows: 
\begin{itemize}
 \item \texttt{svn checkout --username=yourusername \\ 
      \hspace{4cm} svn://svn.iws.uni-stuttgart.de/DUMUX/dumux/trunk dumux}
 \item \texttt{svn checkout --username=yourusername \\
      \hspace{4cm} svn://svn.iws.uni-stuttgart.de/DUMUX/dune-mux/trunk dumux-devel}
\end{itemize} 
The two parts should be stored in separate folders. You can ommit the username option, if the username for the repository access is identical to the one for your system account. Please choose either not to store the password that way or store it by subversion in a secure way, check documentation of subversion for that. A leaked out password can be used by evil persons to vandalize a software repository.
% If you also want to commit new developments or changes to the repositories, you can ask one of the LH$^2$ administrators to add you to the svn group ( \texttt{svndune}).

When using subversion, it is possible, provided that to you are granted developer, i.e. write permissions to repositories, to feed back
your own code or code changes to software repositories. With direct access to software repositories it is also easier for you to keep up with code changes as for important bug fixes or to keep up with general developments of code.


\paragraph{External modules}
Among others, the following modules provide additional functionality, but are not required to run \Dumux:
\begin{itemize}
 \item grids: Alberta, AluGrid, UG
 \item solvers: Pardiso, SuperLU
 \item BLAS and METIS library 
\end{itemize}
These can be downloaded from the respective websites.

If you are working on a LH$^2$ computer, you can checkout a set of external modules via \\
\texttt{svn checkout svn+ssh://luftig/home/svn/DUMUX/external/trunk external}. \\
To install them all, execute the install script in the folder \texttt{external}:
\begin{center}
\texttt{./installExternal.sh all}
\end{center}
If you like to install only some of the external software, you can choose one of the 
corresponding options instead of \texttt{all}: \texttt{alberta, alu, blas, metis, ug}.
Please also refer to the \Dune webpage for additional details, \cite{DUNE-HP}. 


\paragraph{Installation on a non-IWS PC}
If \Dumux is not to be used on a PC maintained by LH$^2$ it is probable that one needs to install additional software. 
Here is a (hopefully complete) list of packages that needed to  be installed on a fresh ubuntu 10.04 in order to get \verb+dunecontrol+ running.
\begin{itemize}
  \item build-essential
  \item openmpi-common / openmpi-bin ...
  \item gfortran
  \item libtool
  \item libboost-all-dev
  \item bison
  \item flex
  \item gcc-4.3 (hard coded into installExternal.sh)
  \item blas ???
  \item pardiso
\end{itemize}


\paragraph{Build the external modules} 
If you obtained a \Dumux tarball, you can skip this part. 

\begin{turn}{45}\textbf{Attenschion}\end{turn}
\begin{turn}{45}\textbf{Attenschion}\end{turn}
\begin{turn}{45}\textbf{Attenschion}\end{turn}
\begin{turn}{45}\textbf{Attenschion}\end{turn}
\begin{turn}{45}\textbf{Attenschion}\end{turn}

{\it

  This  part needs to be extended in order to show which package is necessary for what purpose, 
  so the user can decide whether getting all the grmblDamnItDamnbndfjk 
  moduls working is worth it! \\

  So could somebody please write something about the respective external modules!\\ 

Also, the gcc version 4.3 is hard coded into the skript. }

\begin{turn}{45}\textbf{Attenschion}\end{turn}
\begin{turn}{45}\textbf{Attenschion}\end{turn}
\begin{turn}{45}\textbf{Attenschion}\end{turn}
\begin{turn}{45}\textbf{Attenschion}\end{turn}
\begin{turn}{45}\textbf{Attenschion}\end{turn}

\paragraph{Pardiso} 
In order to get the pardiso solver running one needs to install gfortran-4.3 (this very version) and use the provided option files that end on ``suse11.2'' for dunecontrol. 


\textbf{What needs to be done in order to make pardiso use multiple cores?}

The external modules have to be built first. They consist of Alberta, ALUGrid, UG, and METIS.

\paragraph{Build \Dune and \Dumux}
\label{buildIt}
If you want to compile in the debugging mode, type in the folder \texttt{DUMUX}: 
\begin{center}
\texttt{./dune-common/bin/dunecontrol --opts=\$DUMUX\_ROOT/debug.opts all}
\end{center}

Otherwise you can type
\begin{center}
\texttt{./dune-common/bin/dunecontrol --opts=\$DUMUX\_ROOT/optim.opts all}
\end{center}
in order to get an optimized compilation (better performance, but no possibility to use a debugger).

This uses the \Dune buildsystem. If it does not work, please have a look at the file \texttt{INSTALL} in the \Dumux root directory (if you use SVN, this \texttt{\$DUMUX\_ROOT} is usually \texttt{dumux}, if you use a released version it is usually \texttt{dumux-VERSION}). You can also find more information in the \Dune Buildsystem HOWTO located at the \Dune webpage, \cite{DUNE-HP}.  Alternatively, the tool CMake can be used to build \Dumux. Please check the file \texttt{INSTALL.cmake} for details.