...
If the command fails for any reason (i.e. the module does not exist), it will return a non-zero exit code so you can trap it and deal with it appropriately. There is no need to check wether the module has been loaded or not. You may find that some scripts may fail early where they were not failing before because of this new behaviour
| Code Block |
|---|
|
noformat |
$ module load git; echo return_code=$?
return_code=0
$ module load foo; echo return_code=$?
Lmod has detected the following error: The following module(s) are unknown: "foo"
Please check the spelling or version number. Also try "module spider ..."
It is also possible your cache file is out-of-date; it may help to try:
$ module --ignore-cache load "foo"
Also make sure that all modulefiles written in TCL start with the string #%Module
return_code=1 |
...
Loading a module when there was another version of it loaded is no longer a problem. Lmod will swap them automatically.
| Code Block |
|---|
|
noformat |
$ module load git
$ module load git/new
The following have been reloaded with a version change:
1) git/2.20.1 => git/2.25.1 |
Loaded modules
You can see how many modules and which versions are loaded with "module list"
| Code Block |
|---|
|
$ module list
Currently Loaded Modules:
1) gcc/8.5.0 2) prgenv/gnu 3) git/2.30.1 |
Automatic version aliases
If you try to load a module with an incomplete version, it will try and find the best (latest) version that matches instead of failing.
| Code Block |
|---|
|
noformat |
$ module avail git
-------------------------------------------------------------------------------------- Global Aliases ---------------------------------------------------------------------------------------
pa -> prgenv/amd pe -> prgenv/expert pg -> prgenv/gnu pi -> prgenv/intel pp -> prgenv/pgi
--------------------------------------------------------------------------- /usr/local/apps/modulefiles/lmod/core ---------------------------------------------------------------------------
git/2.20.1 (D) git/2.25.1 (new)
Where:
Aliases: Aliases exist: foo/1.2.3 (1.2) means that "module load foo/1.2" will load foo/1.2.3
D: Default Module
Use "module spider" to find all possible modules and extensions.
Use "module keyword key1 key2 ..." to search for all possible modules matching any of the "keys".
$ module load git/2
$ module load git/2.25
The following have been reloaded with a version change:
1) git/2.20.1 => git/2.25.1 |
...
If two modules cannot be loaded at the same time due to a conflict, the old one will be swapped out and the new one will be loaded automatically.
| Code Block |
|---|
|
noformat |
$ module load proj4
$ module load proj
Lmod is automatically replacing "proj4/5.2.0" with "proj/6.1.1".
|
Native flavour support
You may feel that some packages or versions are missing when running the classic module avail. Lmod knows about those packages that are flavoured for different environments (compilers or MPI), and will only show as available to load those that have been installed for the currently loaded environment. This guarantees that when loading a module the right flavour of the tool or library will be used, avoiding incompatibilities.
...
The prgenv module addresses this problem. There is a prgenv for each compiler family, so it can guarantee a minimal compatibility between different packages.
| Code Block |
|---|
|
noformat |
$ module avail prgenv
-------------------------------------------------------------------------------------- Global Aliases ---------------------------------------------------------------------------------------
pa -> prgenv/amd pe -> prgenv/expert pg -> prgenv/gnu pi -> prgenv/intel pp -> prgenv/pgi
------------------------------------------------------------------------- /usr/local/apps/modulefiles/lmod/prgenvs --------------------------------------------------------------------------
prgenv/amd (a) prgenv/expert (E,e) prgenv/gnu (D:g) prgenv/intel (i) prgenv/pgi |
...