2025.11.000 Release

[Whyborn]

Involves changes to UM7, inclusion of CABLE in specs and changes to the UM7 and CABLe spack packages. Checking for bitwise compatibility against the release version.

---

🚀 The latest prerelease access-esm1p6/pr156-15 at 3827bb8 is here: #156 (comment) 🚀

[github-actions]

The model version in the ./spack.yaml has not been updated.
You can update it manually.

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-1 with commit 81d9496

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-1 with commit 4cf9363

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-1 with commit 509799d

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-1 with commit df09412

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

• 2025.10.001 as a Release (when merged).
• pr156-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr156-1

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr156-1 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version c15cfff914a16c6c492c36eab9c540525e5b4735
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-2 with commit eaaaaea

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

• 2025.10.001 as a Release (when merged).
• pr156-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr156-2

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr156-2 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version c15cfff914a16c6c492c36eab9c540525e5b4735
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[Whyborn]

@ccarouge @JhanSrbinovsky The library and non-library builds show bitwise equivalence after a year of run time. The CABLE library is taken from the HEAD of main. I have opened a PR in UM7 here that removes the CABLE code.

access-esm1.6/config.yaml

...
modules:
  use:
      - /g/data/vk83/modules
  load:
      - access-esm1p6/2025.10.000
...

access-esm1.6-CABLE-as-library/config.yaml

...
modules:
  use:
      - /g/data/vk83/prerelease/modules
  load:
      - access-esm1p6/pr156-2
...

Running nccmp:

[lw5085@gadi-login-03 access-esm1.6]$ nccmp -d access-esm1.6/archive/output000/atmosphere/netCDF/aiihca.pa-219812_mon.nc access-esm1.6-CABLE-as-library/archive/output000/atmosphere/netCDF/aiihca.pa-219812_mon.nc
[lw5085@gadi-login-03 access-esm1.6]$

[Whyborn]

Forgot to include the spack-packages PR: ACCESS-NRI/access-spack-packages#340

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-3 with commit f7b4810

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-4 with commit cce2870

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-5 with commit f58d8c8

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-5 with commit 497f417

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-6 with commit 0b1c0df

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

• 2025.10.001 as a Release (when merged).
• pr156-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr156-6

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr156-6 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version a611a4d07c45cc32f25a273198943ec097dee3b8
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-10 with commit 24b81a2

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

• 2025.11.000 as a Release (when merged).
• pr156-10 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr156-10

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr156-10 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.11.000
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[Whyborn]

!redeploy

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-11 with commit 24b81a2

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

• 2025.11.000 as a Release (when merged).
• pr156-11 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr156-11

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr156-11 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.11.000
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-12 with commit 0237086

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-12 with commit 0da4f3b

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-13 with commit eb05af6

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

• 2025.11.000 as a Release (when merged).
• pr156-13 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr156-13

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr156-13 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version f7ff18261e8026015d200549dd7c0c2472dbd8e9
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-14 with commit ec879bd

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr156-15 with commit 3827bb8

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm1.6, defined in ./spack.yaml, will be deployed to Gadi as:

• 2025.11.000 as a Release (when merged).
• pr156-15 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr156-15

When using the above modules, the binaries shall be on your $PATH.

For advanced users, this Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p6-pr156-15 environment.
Due to inode-saving measures, one will have to manually untar the environment metadata before environment activation with tar -xf .spack-env .spack-env.tar. It will require one to have write privileges.

Configuration Information

This Prerelease is deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.11.001
• access-nri/spack-config version 2025.08.000

If the above was not what was expected, commit changes to config/versions.json in this PR.

[ccarouge]

From the little I know, it seems ok to me. I've checked that the UM tag points to the latest commit on UM7.

For CABLE, there are 2 changes for compatibility with gcc which aren't included here. But since GCOM4 does not compile with gcc, it doesn't matter. The tag points to the commit in CABLE for the latest UM7 changes.