Diff for "Jureca/Software"

Differences between revisions 4 and 5

Software on JURECA

Access to installed software on JURECA is organized through a hierarchy of modules.

Show what modules are compatible available to load right now (given the toolchain modules you have already loaded):
```
module avail
```

Load a specific version of a module

module load <modulename>/<moduleversion>

List what modules are currently loaded
```
module list
```

Unload a module

module unload <modulename>/<moduleversion>

Unload all modules
```
module purge
```
Find the location of a module within the module hierarchy
```
module spider <modulename>
```
Show how to load NetCDF:
```
module -r spider '.*netCDF.*'
```

Module Stages

On JURECA there are major software updates every 6 month (in May and November).

These updates are called stages.

New stages require that user applications are recompiled.

To use "old" executables without recompiling or to create executables with older compiler versions, old stages can be loaded with:

module use /usr/local/software/jureca/OtherStages
module load Stages/xxx

e.g. : load old Intel compiler with parastation MPI and netCDF:

module purge       
module use /usr/local/software/jureca/OtherStages   
module avail
module load Stages/2018b
module load intel-para
module load netCDF-Fortran

Module Collections

Once users have the desired modules load they can save this to a named collection with:

```
module save <collection_name>
```
This creates a file called ~/.lmod.d/<collection_name> with the list of desired modules.

Once this is set-up a user can restore that named collection with:

```
module restore <collection_name>
```
and only the desired modules will be loaded.

Print the contents of a collection with:

```
module describe <collection_name>
```

List all collections:

```
module savelist
```

Disable a collection with:

```
module disable <collection_name>
```

-  ⇤ ← Revision 4 as of 2019-09-30 07:46:28 → 
  Size: 1476
  Editor: NicoleThomas
  Comment:
+   ← Revision 5 as of 2019-09-30 08:31:04 → ⇥
  Size: 2112
  Editor: NicoleThomas
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 44:
- On JURECA there are major software updates every 6 month (in May and November).<<BR>>
+On JURECA there are major software updates every 6 month (in May and November).<<BR>>
 Line 46:
- These updates are called stages.<<BR>>
+These updates are called stages.<<BR>>
 Line 48:
- New stages require that user applications are recompiled.<<BR>><<BR>>
+New stages require that user applications are recompiled.<<BR>><<BR>>
 Line 50:
- To use "old" executables without recompiling or to create executables with older compiler versions, old stages can be loaded with:
+To use "old" executables without recompiling or to create executables with older compiler versions, old stages can be loaded with:
 Line 56:
- e.g. : load old intel compiler with parastation MPI and netcdf:
+e.g. : load old Intel compiler with parastation MPI and netCDF:
 Line 65:
+==== Module Collections ====

Once users have the desired modules load they can save this to a named collection with:
 {{{
module save <collection_name>
}}}
 This creates a file called ''~/.lmod.d/<collection_name>'' with the list of desired modules.

Once this is set-up a user can restore that named collection with:
 {{{
module restore <collection_name>
}}}
 and only the desired modules will be loaded. 

Print the contents of a collection with:
 {{{
module describe <collection_name>
}}}

List all collections:
 {{{
module savelist
}}}

Disable a collection with:
 {{{
module disable <collection_name>
}}}