Many software and libraries are installed on the machines, but very few are directly accessible at the connection to avoid conflicts between different versions available.
The module command allows to load environments integrating the software, tool or library that interests you. It is generally available on all intensive computing centres.
Please note that the modules are no longer updated. The module command will be depreciated in the medium term to the more adapted tools as Nix, Guix or container systems.
To be able to use the applications, you have to load an environment :
source /applis/site/env.bash
You shouldn’t source this file from your .bashrc shell configuration
script or you may experiment conflicts with the system libraries. Only
source the ciment environment manually or at the beginning of your job
scripts.
Warning, the module command is not compatible with Nix, Guix environments. It is therefore necessary to NOT source the module initialization script at the same time than the Nix or Guix initialization script.
| Command | Result |
|---|---|
module avail | To see which modules are available |
module load nom_module | To load a module with all the environment variables |
module unload nom_modul | To remove all the environment created for the module |
module list | To see the loaded modules |
module purge | To purge all modules |
module whatis nom_modules | To have informations about a module |
For Dahu and Luke clusters The list of software and libraries available via the module command on the Dahu and Luke clusters is very limited. We strongly recommend that you to use the environments Nix or Guix on these machines.
For Froggy cluster
About programmation environment, if you need to access to intel and
gnu compilers, you have to use one of the following modules:
gnu-devel/4.4.6
intel-devel/13
intel-devel/14
intel-devel/2015