Skip to content

[package list]

ecCodes

License information

The ecCodes software package license information is available on the "License" page of the ecCodes web site.

After installation and loading the module, a copy of the license is also available in the $EBROOTECDODES/share/licenses/eCCodes directory (from version 2.30.0 onwards).

User-installable modules (and EasyConfigs)

Install with the EasyBuild-user module: 

eb <easyconfig> -r
To access module help after installation and get reminded for which stacks and partitions the module is installed, use module spider ecCodes/<version>.

EasyConfig:

Technical documentation

EasyBuild

Version 2.23.0 in CPE 21.08

  • Started from the CSCS EasyConfig file but added JasPer as a dependency.

  • The Spack recipe seems to have options for various other packages also but the CMake process doesn't seem to look for those. We can't find a trace of those packages in the documentation, inCMakeLists.txt or in the CMake cache after the configure step.

  • Switched to installing libraries in lib rather than lib64 for consistency with most other installs in the LUMI software stack.

Version 2.25.0 for CPE 21.12

  • Trivial port from 2.23.0.

Version 2.26.0 for CPE 22.06 and 22.08

  • Trivial port from 2.25.0

  • Checked for additional sanity check commands but it looks like showing help also returns an error code in almost all commands.

  • Build without Python support as that is for Python2. Python3 support supposedly comes via the eccodes PyPi package but was not tested.

Version 2.30.0 for CPE 22.12 and 23.03

  • Trivial port from 2.26.0, with all remarks still valid.

Version 2.32.0 from CPE 23.09 on

  • Trivial port from 2.30.0, with all remarks still valid.

TODO: ecCodes comes with samples. Can we figure out how to use them and build some quick sanity checks with them?

Archived EasyConfigs

The EasyConfigs below are additonal easyconfigs that are not directly available on the system for installation. Users are advised to use the newer ones and these archived ones are unsupported. They are still provided as a source of information should you need this, e.g., to understand the configuration that was used for earlier work on the system.