From ALICE Documentation
Message Passing Interface (MPI)
The Message Passing Interface (MPI) is a library specification that allows HPC to pass information between its various nodes and clusters. ALICE uses OpenMPI, an open-source, portable implementation of the MPI standard. OpenMPI contains a complete implementation of version 1.2 of the MPI standard and also MPI-2.
OpenMPI is both runtime and compile-time environment for MPI-compliant code.
OpenMPI supports several different compiler sets, but the user must specify which they wish to use for each job.
OpenMPI supports C, C++, F77, and F90. However, not all compiler sets support all languages. Portland Group’s CDK and Intel support all four languages. KCC supports only C++. Absoft supports F77 and F90. GNU supports C, C++, and F77. OpenMPI is tightly integrated with the operating system and the compiler set being used.
Setting up your job
With so many devices and compiler combinations, setting up your environment can seem complicated. ALICE has defined preferred bindings to simplify your environment initialization. The preferred bindings work well on the Linux cluster; however, you are free to choose the best setup for your needs. For most software packages, it is recommended that you use the default link, which points to the default version of the software. For OpenMPI, this is not recommended. Since changing the default link after installing a newer version of OpenMPI will always break currently running or waiting jobs, it is recommended that you always use the path that is associated with that version.
Compiling Your Job
OpenMPI includes wrapper scripts designed to hide the details of compiling with any particular build or compiler. Simply source an OpenMPI build into your shell environment and use mpicc, mpicxx, or mpifort to compile your code. The arguments to the script are passed to the compiler and interpreted normally. The wrapper script will link in the correct libraries and add rpaths as necessary.
Running Your Job
OpenMPI includes a wrapper script called mpirun(1) to hide the details of getting your program to run. To use mpirun, it is critical that the exact same OpenMPI build that was used to build the program is also used to run it (see the mpiexec note below to get around this restriction). After sourcing the correct OpenMPI build, mpirun requires a few arguments to tell it which nodes to run on. The two most common options are -machinefile and -np. Under Slurm, simply pass $SLURM_NTASKS to -np.
Additional information about MPI can be found on the Official Message Passing Interface (MPI) website. To get help with using MPI on ALICE, send an email to email@example.com