Running NorESM on Olivia - NorESMhub/noresm3_dev_simulations GitHub Wiki

Olivia is the latest HPC system provided by Sigma2. Most of the setup on Olivia is similar to Betzy, here we summarize some important differences.

Recommended modules on Olivia

Olivia provides different module stacks with software and libraries provided by NRIS, EESSI and Cray. Software and libraries from these stacks are not interchangeable. It is not recommended that users include module settings in their ~/.bashrc or ~/.profile files. Instead, we recommend to save and re-load a module collection list in the following way.

  • First time use:
module purge
module load NRIS/Login
module load Python/3.12.3-GCCcore-13.3.0
module save mod_noresm
  • Subsequent use
module r mod_noresm

The save name mod_noresm is a personal preference for the module collection list. This is a minimal requirement, users may want to add e.g. CDO or ncview as well. All named collection lists are listed by running

module savelist

To see what modules are included in a named collection, run

module describe <list name>

Load modules in run scripts

If you do setup/build/run for NorESM through a run script (highly recommended!) it is also an option to include the module loading as part of this script. Just copy the required module load <module_name> lines into your script.

No shared noresm directory

Currently we do not have access to a large shared storage space for noresm input data. The most important input data should be available from

/cluster/work/projects/nn9560k/inputdata/

Unfortunately, this is limited to users who have access to the nn9560k project space.

No common user work directory

On Betzy, all jobs run under a common user work directory

/cluster/work/users/<USERNAME>/

On Olivia, the work directory is connected to a specific project

/cluster/work/projects/<NN-PROJECT>/<USERNAME>/

Staging data on Olivia from Nird

Please refer to Sigma2 documentation pages for updated information:

⚠️ **GitHub.com Fallback** ⚠️