Occigen@CINES - feelpp/feelpp GitHub Wiki
The official FAQ is available at the following link.
You can display the quota available to your home directory with the command:
cat ~/.home_quota
If you are using a .bashrc file, it won't be read until you add those line in a .profile file in your home directory:
# if running bash
if [ -n "$BASH_VERSION" ]; then
# include .bashrc if it exists
if [ -f "$HOME/.bashrc" ]; then
. "$HOME/.bashrc"
fi
fi
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
PATH="$HOME/bin:$PATH"
fi
The custom installation are stored in the shared directory of the user aancel. The location is /panfs/panasas/cnt0026/ism7755/SHARED
. The layout is the following:
# The standard feelpp/config method of handling modules
config
software
# Directory here installation were performed
-- install
# Directory where the source and build files are located
-- src
All the installation follow the following path layout:
<software>/<version>/dependency1/dependency2/.../dependencyn
In each software directory of the src directory, there is an installation script called ìnstall.sh
that allows to reinstall the corresponding software. Note that you can't access external ressources on occigen (e.g. you cannot perform wget, curl ...)
Please add the following lines in your .bashrc to load the modules for Feel++:
cd /panfs/panasas/cnt0026/ism7755/SHARED/config/etc
source feelpprc.sh
cd -
module purge
module load /opt/modules/modulefiles/oscar-modules/1.0.3
module load intel
module load bullxmpi/1.2.8.4-mxm
module load cmake/3.5.2
module load hwloc/1.11.0
module load python/2.7.8
module load vtk/6.2.0
module load libs/gmp/6.1.1
module load libs/mpfr/3.1.4
module load libs/mpc/1.0.3
module load compilers/gcc/6.1.0
module load compilers/clang/4.0.0-svn_gcc610
module load libs/boost/1.61_gcc610_bullxmpi1284mxm
module load libs/petsc/3.7.3_gcc610_bullxmpi1284mxm
module load libs/slepc/3.7.2_gcc610_bullxmpi1284mxm
module load libs/hdf5/1.8.17_gcc610_bullxmpi1284mxm
module load science/gmsh/2.13.1_gcc610
Occigen seems to be using several access nodes to balance the load. You probably ended up on a different node from which you launched your previous screen.