[blimlim]

This PR is to produce a "2026.09.29" prerelease build, from which development builds can be based on.

This uses:

• access3/access3-share: 793460415e411783798686b9e6fe42cd837e99a1 which includes some fixes since the version used in the 2026.08.(17/18) experiments. Swapped to ff5c4a3bf0ce3fc14a371f8501d6974170d8b6df as this seems to have replaced the old branch.
• UM: 0541c6519fa18ca399b5da563f3bb995c619a52e the current head of the vn13.8_nuopc branch.
• Versions for the UM dependencies (Jules etc.) are copied from the CM3 configs repo
• CICE: b983fe1db89d26f49044336ffeccee8ef451e6f6, the current head of the access-cm3-CICE6.6.1-0 branch. This contains the changes here compared to the version used in the 2026.08.(17/18) experiments

---

🚀 The latest prerelease access-esm3/pr16-3 at e3c3f67 is here: #16 (comment) 🚀

---

🚀 The latest prerelease access-esm3/pr16-10 at da82b4d is here: #16 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-esm3 Prerelease pr16-1 with commit 06713cc

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm3 Prerelease pr16-2 with commit 56ddd45

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm3 Prerelease pr16-2 with commit e3c3f67

🖥️ Gadi Deployment ❌

[blimlim]

!redeploy

[github-actions]

🚀 Attempted to deploy access-esm3 Prerelease pr16-3 with commit e3c3f67

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm3 Prerelease pr16-4 with commit 99a27d2

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm3, defined in spack.yaml, will be deployed to Gadi as:

• 2026.06.000 as a Release (when merged).
• pr16-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm3/pr16-4

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/1.1/spack in the access-esm3-pr16-4 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 1.1
• ACCESS-NRI/upstream-spack-packages version access/v1.1
• access-nri/access-spack-packages version 7a9acda3f9985d972f5e48b805f26313741cf64b
• access-nri/spack-config version 2026.08.001

If the above was not what was expected, commit changes to the manifest in this PR, or propose changes to build-cds config/settings.json.

[github-actions]

🚀 Attempted to deploy access-esm3 Prerelease pr16-5 with commit ba502b3

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm3, defined in spack.yaml, will be deployed to Gadi as:

• 2026.06.000 as a Release (when merged).
• pr16-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm3/pr16-5

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/1.1/spack in the access-esm3-pr16-5 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 1.1
• ACCESS-NRI/upstream-spack-packages version access/v1.1
• access-nri/access-spack-packages version dc2eb6e2bf91a25c3c8e49681daf44e002cc17cc
• access-nri/spack-config version 2026.08.001

If the above was not what was expected, commit changes to the manifest in this PR, or propose changes to build-cds config/settings.json.

[blimlim]

Sanity checking that we get the same answers compared to the suite build. When adding the march, mtune, and unroll flags to the suite build, we get identical results:

[github-actions]

🚀 Attempted to deploy access-esm3 Prerelease pr16-6 with commit 2f1cc5a

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm3 Prerelease pr16-7 with commit a73bcff

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm3 Prerelease pr16-8 with commit 3d4d2c4

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm3, defined in spack.yaml, will be deployed to Gadi as:

• 2026.06.000 as a Release (when merged).
• pr16-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm3/pr16-8

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/1.1/spack in the access-esm3-pr16-8 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 1.1
• ACCESS-NRI/upstream-spack-packages version access/v1.1
• access-nri/access-spack-packages version 2026.10.002
• access-nri/spack-config version 2026.10.000

If the above was not what was expected, commit changes to the manifest in this PR, or propose changes to build-cds config/settings.json.

[github-actions]

🚀 Attempted to deploy access-esm3 Prerelease pr16-9 with commit 9e8f3aa

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm3, defined in spack.yaml, will be deployed to Gadi as:

• 2026.06.000 as a Release (when merged).
• pr16-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm3/pr16-9

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/1.1/spack in the access-esm3-pr16-9 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 1.1
• ACCESS-NRI/upstream-spack-packages version access/v1.1
• access-nri/access-spack-packages version 2026.10.002
• access-nri/spack-config version 2026.10.000

If the above was not what was expected, commit changes to the manifest in this PR, or propose changes to build-cds config/settings.json.

[github-actions]

🚀 Attempted to deploy access-esm3 Prerelease pr16-10 with commit da82b4d

🖥️ Gadi Deployment ✔️

Usage Instructions

access-esm3, defined in spack.yaml, will be deployed to Gadi as:

• 2026.06.000 as a Release (when merged).
• pr16-10 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm3/pr16-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/1.1/spack in the access-esm3-pr16-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 1.1
• ACCESS-NRI/upstream-spack-packages version access/v1.1
• access-nri/access-spack-packages version 2026.10.006
• access-nri/spack-config version 2026.10.000

If the above was not what was expected, commit changes to the manifest in this PR, or propose changes to build-cds config/settings.json.