ACCESS-CM3 2026.07.000

[kieranricardo]

---

🚀 The latest prerelease access-om3/pr250-15 at e1fc2a8 is here: #250 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr250-1 with commit e6e2870

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr250-2 with commit 6a6ca74

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr250-3 with commit 3f3fca2

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr250-4 with commit 5959a65

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr250-5 with commit f1fc849

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.08.999 as a Release (when merged).
• pr250-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr250-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-om3-pr250-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 2026.06.000
• access-nri/spack-config version 2026.05.004

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

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr250-6 with commit 9ee7f1d

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr250-7 with commit 47dad5d

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.08.999 as a Release (when merged).
• pr250-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr250-7

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-om3-pr250-7 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.06.000
• access-nri/spack-config version 2026.05.004

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

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr250-8 with commit 6e15719

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.08.999 as a Release (when merged).
• pr250-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr250-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-om3-pr250-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.06.000
• access-nri/spack-config version 2026.05.004

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

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr250-9 with commit 9aa2046

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr250-10 with commit e23b1df

🖥️ Gadi Deployment ❌

[kieranricardo]

!redeploy

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr250-12 with commit 736824c

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr250-13 with commit 5501f35

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr250-14 with commit bd449cf

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr250-15 with commit e1fc2a8

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.08.999 as a Release (when merged).
• pr250-15 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

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