Commit af050175 authored by Bernd Flemisch's avatar Bernd Flemisch
Browse files

updated INSTALL text file instructions

git-svn-id: svn://svn.iws.uni-stuttgart.de/DUMUX/dumux/trunk@5293 2fb0f335-1f38-0410-981e-8018bf24f1b0
parent d8614cc1
...@@ -17,36 +17,37 @@ Getting started ...@@ -17,36 +17,37 @@ Getting started
In order to compile DuMuX, you first have to download and extract the In order to compile DuMuX, you first have to download and extract the
following DUNE modules into your source directory: following DUNE modules into your source directory:
- DUNE-common from [1] - dune-common from [1]
- DUNE-grid from [1] - dune-grid from [1]
- DUNE-istl from [1] - dune-istl from [1]
- DUNE-localfuctions from [1] - dune-localfuctions from [1]
- DUNE-pdelab from [3] - dune-pdelab from [2]
Since many simulators of DuMuX use the UG grid manager, it is recommended Use the 2.0 release of the DUNE core modules and the 2.0 snapshot of
to install it first [4]. dune-pdelab.
Next, you need to decide whether you want to compile in debug or in Next, you need to decide whether you want to compile in debug or in
optimized mode and adapt the option file for the DUNE build system to optimized mode. Example files are located in $DUMUX_ROOT/optim.opts
the path where you installed UG. The files are located in and $DUMUX_ROOT/debug.opts respectively. ($DUMUX_ROOT is the
$DUMUX_ROOT/optim.opts and $DUMUX_ROOT/debug.opts directory where the unpacked files of the DuMuX distribution are
respectively. ($DUMUX_ROOT is the directory where the unpacked files located.)
of the DuMuX distribution are located.) Next, compile everything using
Next, compile everything with
./dune-common/bin/dunecontrol --opts=$(DUMUX_ROOT)/optim.opts --module=dumux all ./dune-common/bin/dunecontrol --opts=$(DUMUX_ROOT)/optim.opts --module=dumux all
Finally, install DUNE and DuMuX headers to your system using Finally, install DUNE and DuMuX headers to your system by
./dune-common/bin/dunecontrol --module=dumux make install ./dune-common/bin/dunecontrol --module=dumux make install
A more comprehensive introduction to the DUNE build system can be A more comprehensive introduction to the DUNE build system can be
found in [2]. found in [3].
Links Links
----- -----
0. http://www.dune-project.org/doc/installation-notes.html 0. http://www.dune-project.org/doc/installation-notes.html
1. http://www.dune-project.org/download.html 1. http://www.dune-project.org/download.html
2. http://www.dune-project.org/doc/buildsystem/buildsystem.pdf 2. http://www.dune-project.org/downloadext.html
3. http://www.dune-project.org/downloadext.html 3. http://www.dune-project.org/doc/buildsystem/buildsystem.pdf
4. http://www.dune-project.org/external_libraries/install_ug.html
Why CMake Why CMake
========= =========
We use CMake 2.6 or higher as alternative to the build system provided You can use CMake 2.6 or higher as alternative to the build system
by DUNE. CMake is included in most GNU/Linux distributions or can be provided by DUNE. CMake is included in most GNU/Linux distributions
downloaded at www.cmake.org. Using CMake has several advantages or can be downloaded at www.cmake.org. Using CMake has several
compared to autotools: advantages compared to autotools:
- Out-of-tree builds are the default way to build software: The - Out-of-tree builds are the default way to build software: The
directory where the source code resides won't get modified during directory where the source code resides won't get modified during
...@@ -74,3 +74,8 @@ cmake -DCMAKE_BUILD_TYPE=debug \ ...@@ -74,3 +74,8 @@ cmake -DCMAKE_BUILD_TYPE=debug \
-DALUGrid_DIR=/usr/local/alugrid \ -DALUGrid_DIR=/usr/local/alugrid \
-DMETIS_DIR=/usr/local/metis \ -DMETIS_DIR=/usr/local/metis \
path/to/DUMUX/source/directory path/to/DUMUX/source/directory
With gcc >= 4.5.0, compilation might fail due to an internal compiler
error. In this case, you might want to specify the compiler explicitly
by using the cmake options -DCMAKE_CXX_COMPILER and -DCMAKE_CC_COMPILER.
...@@ -393,7 +393,7 @@ protected: ...@@ -393,7 +393,7 @@ protected:
if (numDiffMethod <= 0) { if (numDiffMethod <= 0) {
// we are not using forward differences, i.e. we don't // we are not using forward differences, i.e. we
// need to calculate f(x - \epsilon) // need to calculate f(x - \epsilon)
// deflect the primary variables // deflect the primary variables
......
...@@ -122,7 +122,7 @@ public: ...@@ -122,7 +122,7 @@ public:
SET_BOOL_PROP(InjectionProblem2PNI, EnableGravity, true); SET_BOOL_PROP(InjectionProblem2PNI, EnableGravity, true);
// write convergence behaviour to disk? // write convergence behaviour to disk?
SET_BOOL_PROP(InjectionProblem2PNI, NewtonWriteConvergence, true); SET_BOOL_PROP(InjectionProblem2PNI, NewtonWriteConvergence, false);
} }
/*! /*!
......
...@@ -167,6 +167,8 @@ public: ...@@ -167,6 +167,8 @@ public:
void boundaryTypes(BoundaryTypes &BCtypes, const Vertex &vertex) const void boundaryTypes(BoundaryTypes &BCtypes, const Vertex &vertex) const
{ {
const GlobalPosition &pos = vertex.geometry().center(); const GlobalPosition &pos = vertex.geometry().center();
Scalar right = this->bboxMax()[0];
if (pos[0] < eps_) // Dirichlet conditions on left boundary if (pos[0] < eps_) // Dirichlet conditions on left boundary
BCtypes.setAllDirichlet(); BCtypes.setAllDirichlet();
else // neuman for the remaining boundaries else // neuman for the remaining boundaries
...@@ -179,6 +181,8 @@ public: ...@@ -179,6 +181,8 @@ public:
// primary variables. // primary variables.
void dirichlet(PrimaryVariables &values, const Vertex &vertex) const void dirichlet(PrimaryVariables &values, const Vertex &vertex) const
{ {
const GlobalPosition &pos = vertex.geometry().center();
values[Indices::pwIdx] = 200.0e3; // 200 kPa = 2 bar values[Indices::pwIdx] = 200.0e3; // 200 kPa = 2 bar
values[Indices::SnIdx] = 0.0; // 0 % oil saturation on left boundary values[Indices::SnIdx] = 0.0; // 0 % oil saturation on left boundary
} }
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment