The current Gadi setup instructions and helper scripts still load:
module load model-tools/babeltrace2/2.1.2
However the current ACCESS-NRI/model-tools deployment defines:
- _name: [babeltrace2]
- _version: [2.1.2-2]
# _spack-version informs the branch of spack to use
- _spack-version: ["1.1"]
# Release database provenance information - packages for inclusion into the database, and packages just for injection into the modules
- _provenance: []
- _injection: []
specs:
- babeltrace2@2.1.2
Here 2.1.2 is the upstream Babeltrace2 package version, while 2.1.2-2 is the ACCESS-NRI deployment/module version. The build-cd workflow injects _version into the module projection, so the current module should be loaded as:
module use /g/data/vk83/modules
module load model-tools/babeltrace2/2.1.2-2
The -2 deployment also reflects the updated build configuration, including the move to intel-oneapi-compilers@2025.2.0, target=x86_64_v3, and the updated Python module setup. See ACCESS-NRI/model-tools#24
The current Gadi setup instructions and helper scripts still load:
However the current ACCESS-NRI/model-tools deployment defines:
Here 2.1.2 is the upstream Babeltrace2 package version, while 2.1.2-2 is the ACCESS-NRI deployment/module version. The build-cd workflow injects _version into the module projection, so the current module should be loaded as:
The -2 deployment also reflects the updated build configuration, including the move to intel-oneapi-compilers@2025.2.0, target=x86_64_v3, and the updated Python module setup. See ACCESS-NRI/model-tools#24