This type of installation is not advised, some dependent libraries like MoAB or PETSc have very complex dependencies and success of installation depends on the state of your OS, i.e. versions of compilers, installed packages and location of libraries. Installation could be time-consuming. In order to avoid unnecessary effort, we recommend that you will follow installation with Spack.

If you have any problems, feedback or would like to suggest corrections, please email mofem-group@googlegroups.com.

Install packages

Following lines install minimum number of packages need to work with MoFEM:

apt-get update
apt-get install -y \
file \
zlib1g-dev \
openssh-server \
wget \
valgrind \
git \
g++ \
gfortran \
gdb \
m4 \
automake \
build-essential \
libtool \
libblas-dev \
liblapack-dev \
libsigsegv2 \
libjpeg-dev \
graphviz \
doxygen \
cmake \
gnuplot \
pstack \
ca-certificates \
python \
bison \
flex \
libx11-dev \
libboost-all-dev \
libopenmpi-dev \
openmpi-bin \
xauth \
xterm \
unzip \
tk8.6-dev \
libfreetype6-dev \
mesa-common-dev \
libglu1-mesa-dev \
libxmu-dev \
libxi-dev \
libssl-dev

Open a terminal

Create mofem install director:

export MOFEM_INSTALL_DIR=$HOME/mofem_installation

mkdir $MOFEM_INSTALL_DIR

Install PETSc and other libraries

# Change to your $MOFEM_INSTALL_DIR
cd $MOFEM_INSTALL_DIR
 
# Colone PETSc repository:
git clone https://bitbucket.org/petsc/petsc.git
cd $MOFEM_INSTALL_DIR/petsc
 
# Fix PETSc version
export PETSC_VERSION=3.11.3
git checkout tags/v$PETSC_VERSION
 
# Configure and compile petsc:
./configure --with-mpi=1 --with-debugging=0 \
--download-superlu_dist=1 --download-metis=1 --download-parmetis=1 --download-hypre=1 \
--download-mumps=1 --download-scalapack=1 --download-blacs=1 --download-moab=1 \
--download-ptscotch=1 --download-hdf5=1 --download-netcdf=1 \
--with-shared-libraries=1 && \
make PETSC_DIR=$PWD PETSC_ARCH=arch-linux2-c-opt all
 
# Add path to petsc binaries, you can add that line to .bashrc
export PATH=$MOFEM_INSTALL_DIR/petsc/arch-linux2-c-opt/bin:$PATH

Note: PETSc is compiled with debugging switch off for efficiency. If you develop code is recommended that you compile PETSc with debugging flag on in addition. You can have two versions of MoFEM compiled, for debugging and development and other version for larger calculations.

Clone source code and install core MoFEM library

# Change to your $MOFEM_INSTALL_DIR
cd $MOFEM_INSTALL_DIR
 
# Cloning MoFEM source code:
git clone --recurse-submodules https://bitbucket.org/likask/mofem-cephas.git mofem-cephas
 
# Make a build directory
mkdir $MOFEM_INSTALL_DIR/lib
cd $MOFEM_INSTALL_DIR/lib
 
# Configuring and compiling code:
cmake -DCMAKE_BUILD_TYPE=Release \
 -DPETSC_DIR=$MOFEM_INSTALL_DIR/petsc/ -DPETSC_ARCH=arch-linux2-c-opt \
 -DMOAB_DIR=$MOFEM_INSTALL_DIR/petsc/arch-linux2-c-opt/ \
 -DWITH_ADOL-C=1 -DWITH_TETGEN=1 -DWITH_MED=1 \
 -DCMAKE_INSTALL_PREFIX=$MOFEM_INSTALL_DIR/users_modules \
 $MOFEM_INSTALL_DIR/mofem-cephas/mofem
 
# Building code (assuming that you have computer with 4 cores):
make -j4 install
 
# Testing and publishing results on MoFEM CDashTesting WebPage:
ctest -D Experimental

Configuration, compilation and testing user modules

Before you start this version, change directory to install directory

cd $MOFEM_INSTALL_DIR/users_modules
# Configuration:
cmake -DCMAKE_BUILD_TYPE=Release users_modules
# Build:
make -j4

Testing

ctest -D Experimental

Note that results of the tests are publish on MoFEM CDashTesting web page. If you do not wish to publish results remove option -D Experimental

Adding users modules

MoFEM is extendable and you can upload additional users modules, see some of the here. You can upload them to the independent directory and provide a path by setting

-DEXTERNAL_MODULE_SOURCE_DIRS=$PATH_TO_MY_DIR

or upload them to $MOFEM_INSTALL_DIR/users_modules/users_modules. You have to re-run cmake, build and test code.

Table of Contents