Page History

...

With modmap you can see if the desired module is available and which profile you have to load to use it.

>modmap -m <module name>

Spack

...

 Spack environment

In case you don't find a software you can choose to install it by yourself. 
In this case, on Marconi100 we also offer the possibility to use the “spack” environment by loading the corresponding module:

$ module load spack/<vers>

By loading this spack module, setup-env.sh file is sourced. Then $SPACK_ROOT is initialized to /cineca/prod/opt/tools/spack/<vers>/none, spack command is added to your PATH, and some nice command line integration tools too.

A folder is created into your default $WORK space ($USER/spack-<vers>) in order to contain some subfolders created and used by spack during the phase of a package installation:

- sources cache: $WORK/$USER/spack-<vers>/cache

- software installation root: $WORK/$USER/spack-<vers>/install

- module files location: $WORK/$USER/spack-<vers>/modulefiles

You can consult the spack guide in which you can find how to customize these paths.

The software we have installed through Spack is available as module by typing the following commands:

$ module load spack

$ module av

$ module av <module_name>

or as spack packages:

$ module load spack

$ spack find

$ spack find <pack_name>

You can show the dependencies, variants, and flags used for the installation of a specific package and the path where are located its binaries typing the following command:

$ spack find -ldvrp <name>

In order to find all the compilers available you can type the following command:

$ spack compiler list

In order to install software through this spack module you can 1) install the needed compilers and libraries on which it depends on spack too or 2) use the corresponding modules already available for the cluster users.

In the first case, after installing the needed compiler through spack, remember to load the corresponding module and add it to compilers.yaml file by typing the following commands:

$ module load <compiler>

$ spack compiler find

The file compilers.yaml is created by default into $HOME/.spack/<platform> path.

In the second case, you use the compiler module already installed on the cluster, you have to specify it simply:

#e.g. gcc 8.3.0:

$ spack install <pack> %gcc@8.3.

If you want to use a library already available on the cluster in order to install your application through spack module you have to specify it through ^ type:

#e.g. zlib@1.2.11

$ spack <pack> ^zlib@1.2.11

Production environment

Since M100 is a general purpose system and it is used by several users at the same time, long production jobs must be submitted using a queuing system. This guarantees that the access to the resources is as fair as possible.
Roughly speaking, there are two different modes to use an HPC system: Interactive and Batch. For a general discussion see the section Production Environment and Tools.

...