2026.05.003 new build

[ezhilsabareesh8]

Fixes for the following:

MOM6:

• Add minimum thickness clamp in mixedlayer_restrat_Bodner (by @dougiesquire in Add minimum thickness clamp in mixedlayer_restrat_Bodner MOM6#61)
• Add FILE_DYE_TRACER_ACCUMULATE param to the file-based dye tracer (by @angus-g in Add FILE_DYE_TRACER_ACCUMULATE flag MOM6#67)
• Save correct thickness value for diagnostic vert_remap_h (by @jbisits in Save correct thickness value for id_vert_remap_h MOM6#66)
• Add a numerical mixing diagnostic (by @jbisits in Add a numerical mixing diagnostic to MOM6 MOM6#57)

CICE6:

• Fix ANGLE and tripole closure in MOM supergrid by @anton-seaice in Fix ANGLE and tripole closure in MOM supergrid CICE#50

WW3:

• Remove W3_IS2 compile guard from IC5 floe diameter update by @ezhilsabareesh8 in Remove W3_IS2 compile guard from IC5 floe diameter update in w3wavemd WW3#15
• Avoid ST6 IRANGE heap allocations in source loops by @ezhilsabareesh8 in Avoid ST6 IRANGE heap allocations in source loops WW3#16

---

🚀 The latest prerelease access-om3/pr260-5 at 40e8f5d is here: #260 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr260-1 with commit 8f538c6

🖥️ Gadi Deployment ❌

[dougiesquire]

You'll need to update the version of access-spack-packages in config/versions.json @ezhilsabareesh8

[ezhilsabareesh8]

!redeploy

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr260-2 with commit a21b825

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr260-2 with commit a21b825

🖥️ Gadi Deployment ❌

[dougiesquire]

The failures might be due to the fact that you triggered two builds of the same thing at the same time. Pushing a commit triggers the workflow - you don't need to also do !redeploy

[dougiesquire]

!redeploy

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr260-4 with commit a21b825

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.05.003 as a Release (when merged).
• pr260-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

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 pr260-5 with commit 40e8f5d

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.05.003 as a Release (when merged).
• pr260-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/pr260-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-pr260-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.08.005
• access-nri/spack-config version 2026.07.001

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.

[ezhilsabareesh8]

!update-configs

[github-actions]

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-om3-configs

Configurations Requested

Configurations requested from profile default:

• dev-MCW_100km_jra_iaf

• dev-MC_100km_jra_ryf

• dev-MC_100km_jra_ryf+wombatlite

• dev-MC_25km_jra_ryf

Pull Requests Opened/Updated

The following PRs were opened/updated:

• Auto update dev-MCW_100km_jra_iaf to use access-om3/pr260-5 access-om3-configs#1553

• Auto update dev-MC_100km_jra_ryf to use access-om3/pr260-5 access-om3-configs#1552

• Auto update dev-MC_100km_jra_ryf+wombatlite to use access-om3/pr260-5 access-om3-configs#1551

• Auto update dev-MC_25km_jra_ryf to use access-om3/pr260-5 access-om3-configs#1554

More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/31345367341

[anton-seaice]

Oh sorry - the CICE change is answer changing (ofcourse)

It looks like it runs ok in all the above PRs, and the determinism tests pass

[anton-seaice]

Please squash merge

[ezhilsabareesh8]

Thanks @anton-seaice and @dougiesquire