Skip to content

installationHPC

Congjian Wang - INL edited this page Sep 27, 2021 · 31 revisions

INL HPC Systems

The High Performance Computing (HPC) machines at INL have similar RAVEN install procedures, outlined below. Note that AFTER loading modules, RAVEN libraries must be installed as per a normal Linux installation (link below).

The process for any INL HPC system is as follows:

  • Load modules
  • Clone RAVEN
  • Install libraries, giving the location of conda.

(Note, if you have not used the Linux command line before, it might be useful to read a tutorial on using it first: https://ubuntu.com/tutorials/command-line-for-beginners Learning about the ssh and the git commands will also be useful.)

Clone RAVEN

Regardless of the HPC environment in which you want to install RAVEN, it should be cloned.

NOTE that sometimes modules need to be loaded before cloning can occur (for example, git must be available). Also note that git can only be used on the login node (such as lemhi1 or falcon1), not on the cluster compute nodes (if you are using hpc ondemand, you may need to ssh to the login node to run git commands that access github.)

git clone https://github.com/idaholab/raven.git
cd raven

Install RAVEN Plugins (ONLY IF YOU HAVE ACCESS TO PLUGINS)

This step is optional, and you need to contact the raven developers to obtain the access first. Contact us. The installation instruction can be found: RAVEN Plugins

SAWTOOTH

Two tagged versions of RAVEN have been installed on sawtooth, i.e., raven and raven/2.0, the users can directly load these raven modules:

[~]> module load raven/2.0
[~]> raven_framework raven_input.xml

If you want to install the latest raven devel branch, try to load raven/2.0 first:

[~]> module load raven/2.0

Then try to set your own raven library name (FYI, you can not use "raven_libraries" as the library name since it is already used by module raven/2.0)

[~]> export RAVEN_LIBS_NAME=raven_libs

You can choose a different name to replace 'raven_libs', but you can not use 'raven_libraries' on sawtooth which is reserved for module raven/2.0. Now you can use establish_conda_env.sh script to install raven libraries, i.e.,

[~]> ./scripts/establish_conda_env.sh --install --conda-defs /apps/local/anaconda/3.7/etc/profile.d/conda.sh

When the libraries got installed, you can build raven:

[~]> ./build_raven

LEMHI

Lemhi does not yet have a raven-devel module, so the following should be loaded:

[~]> module load pbs python MVAPICH2

The module conda location (as an argument when installing RAVEN libraries)

./scripts/establish_conda_env.sh --install --conda-defs /apps/local/anaconda/anaconda3.7/etc/profile.d/conda.sh

FALCON

The following module needs to be loaded:

[~]> module load raven-devel

The module conda location (as an argument when installing RAVEN libraries)

./scripts/establish_conda_env.sh --install --conda-defs /apps/local/anaconda/Anaconda3-2019.10/etc/profile.d/conda.sh

Continuing Installation

After the appropriate modules are loaded, continue with normal Linux installation instructions:

Linux installation instructions.


General HPC

In general RAVEN needs:

  • a GCC compiler with C++11 standard (for example 4.9.2)
  • conda (local installation per user is fine)
  • MPI (if distributed simulations are desired)

Once these three are available, install RAVEN via the Linux installation instructions.

More Information

See also Advanced Installation