Release 2026.02.000 by dougiesquire · Pull Request #133 · ACCESS-NRI/ACCESS-OM2

dougiesquire · 2026-02-01T23:59:32Z

Next release of ACCESS-OM2:

Update access-generic-tracers
Update cice5 (and parallelio) closes CICE5 with updated ParallelIO #129 and CICE5 CMake Build #126

Will bump the access-om2 version once other changes have been made.

🚀 The latest prerelease access-om2/pr133-10 at cb206a7 is here: #133 (comment) 🚀

dougiesquire · 2026-02-01T23:59:50Z

@anton-seaice, could you please add CICE5 and PIO updates?

github-actions · 2026-02-02T00:28:23Z

🚀 Attempted to deploy access-om2 Prerelease pr133-2 with commit 9034c5b

🖥️ `Gadi` Deployment ❌

anton-seaice · 2026-02-02T00:39:05Z

[5](https://github.com/ACCESS-NRI/ACCESS-OM2/actions/runs/21573067764/job/62155349824#step:16:356)
  File "/g/data/vk83/prerelease/apps/spack/0.22/spack/lib/spack/spack/solver/asp.py", line 2683, in validate_and_define_versions_from_requirements
    f"Version requirement {versions} on {pkg_name} for {name} "
spack.config.ConfigError: Version requirement 2.6.8 on parallelio for parallelio cannot match any known version from package.py or externals

github-actions · 2026-02-02T01:01:54Z

🚀 Attempted to deploy access-om2 Prerelease pr133-1 with commit 714e94f

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.12.000 as a Release (when merged).
pr133-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr133-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-om2-pr133-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 2026.01.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.

anton-seaice · 2026-02-02T01:42:39Z

!redeploy

github-actions · 2026-02-02T01:48:17Z

🚀 Attempted to deploy access-om2 Prerelease pr133-3 with commit 9034c5b

🖥️ `Gadi` Deployment ❌

github-actions · 2026-02-02T02:02:02Z

🚀 Attempted to deploy access-om2 Prerelease pr133-4 with commit 809acb8

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.12.000 as a Release (when merged).
pr133-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr133-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/0.22/spack in the access-om2-pr133-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 0.22
access-nri/spack-packages version 2026.01.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.

dougiesquire · 2026-02-02T02:07:58Z

!update-configs

github-actions · 2026-02-02T02:08:58Z

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

Configurations Requested

Configurations requested from profile default:

dev-1deg_jra55_ryf

Pull Requests Opened

The following PRs were opened:

Auto update dev-1deg_jra55_ryf to use access-om2/pr133-4 access-om2-configs#250

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

anton-seaice · 2026-02-02T02:12:32Z

module load access-om2/pr133-4/2025.02.000-360x300

contains

cice_auscom_360x300_15x300.exe

access-om2/pr133-4/2025.02.000-1440x1080 : cice_auscom_1440x1080_30x27.exe

access-om2/pr133-4/2025.02.000-3600x2700 : cice_auscom_3600x2700_18x15.exe

spack.yaml

github-actions · 2026-02-02T02:25:24Z

🚀 Attempted to deploy access-om2 Prerelease pr133-5 with commit 2ac7efa

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.12.000 as a Release (when merged).
pr133-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr133-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/0.22/spack in the access-om2-pr133-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 0.22
access-nri/spack-packages version 2026.01.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.

github-actions · 2026-02-02T02:28:06Z

🚀 Attempted to deploy access-om2 Prerelease pr133-6 with commit 5308e1c

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.000 as a Release (when merged).
pr133-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr133-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-om2-pr133-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 2026.01.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.

dougiesquire · 2026-02-02T02:35:29Z

!update-configs

github-actions · 2026-02-02T02:37:02Z

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

Configurations Requested

Configurations requested from profile default:

dev-1deg_jra55_ryf

Pull Requests Opened

The following PRs were opened:

Auto update dev-1deg_jra55_ryf to use access-om2/pr133-6 access-om2-configs#251

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

spack.yaml

github-actions · 2026-02-02T04:25:56Z

🚀 Attempted to deploy access-om2 Prerelease pr133-7 with commit 3610070

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.000 as a Release (when merged).
pr133-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr133-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/0.22/spack in the access-om2-pr133-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 0.22
access-nri/spack-packages version 2026.01.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.

github-actions · 2026-02-02T04:44:44Z

🚀 Attempted to deploy access-om2 Prerelease pr133-8 with commit a929a9a

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.000 as a Release (when merged).
pr133-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr133-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/0.22/spack in the access-om2-pr133-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 0.22
access-nri/spack-packages version 2026.01.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.

github-actions · 2026-02-02T06:08:48Z

🚀 Attempted to deploy access-om2 Prerelease pr133-9 with commit cb206a7

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.02.000 as a Release (when merged).
pr133-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om2/pr133-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/0.22/spack in the access-om2-pr133-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 0.22
access-nri/spack-packages version 2026.01.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.

dougiesquire · 2026-02-02T06:30:59Z

Repro tests pass for :

github-actions · 2026-02-02T06:32:52Z

🚀 Attempted to deploy access-om2 Prerelease pr133-10 with commit cb206a7

🖥️ `Gadi` Deployment ❌

dougiesquire · 2026-02-02T06:35:29Z

CI doesn't like multiple specs I think...

anton-seaice · 2026-02-02T21:14:27Z

I thought only the version in the first line of the spec was important, we'll need to wait for Gadi

anton-seaice · 2026-02-02T21:16:58Z

spack.yaml

+    default:
+      tcl:
+        projections:
+          access-om2: '{name}/2026.02.000-{^cice5.variants.nxglob.value}x{^cice5.variants.nyglob.value}'


According to ACCESS-NRI/build-cd#350 we can remove the CalVer part from this string

anton-seaice · 2026-02-02T21:18:34Z

Looks like we might need Tommy: ACCESS-NRI/build-cd#344

anton-seaice · 2026-02-02T23:35:41Z

spack.yaml

+    - access-om2@git.2026.02.000 ^cice5 nxglob=360 nyglob=300 blckx=15 blcky=300 mxblcks=1
+    - access-om2 ^cice5 nxglob=1440 nyglob=1080 blckx=30 blcky=27 mxblcks=4
+    - access-om2 ^cice5 nxglob=3600 nyglob=2700 blckx=40 blcky=30 mxblcks=12


Suggested change

- access-om2@git.2026.02.000 ^cice5 nxglob=360 nyglob=300 blckx=15 blcky=300 mxblcks=1

- access-om2 ^cice5 nxglob=1440 nyglob=1080 blckx=30 blcky=27 mxblcks=4

- access-om2 ^cice5 nxglob=3600 nyglob=2700 blckx=40 blcky=30 mxblcks=12

- access-om2@git.2026.02.000 ^cice5 nxglob=360 nyglob=300 blckx=15 blcky=300 mxblcks=1

- access-om2@git.2026.02.000 ^cice5 nxglob=1440 nyglob=1080 blckx=30 blcky=27 mxblcks=4

- access-om2@git.2026.02.000 ^cice5 nxglob=3600 nyglob=2700 blckx=40 blcky=30 mxblcks=12

see #134

anton-seaice · 2026-02-02T23:35:53Z

spack.yaml

+    default:
+      tcl:
+        projections:
+          access-om2: '{name}/2026.02.000-{^cice5.variants.nxglob.value}x{^cice5.variants.nyglob.value}'


Suggested change

access-om2: '{name}/2026.02.000-{^cice5.variants.nxglob.value}x{^cice5.variants.nyglob.value}'

access-om2: '{name}/{^cice5.variants.nxglob.value}x{^cice5.variants.nyglob.value}'

anton-seaice · 2026-02-03T22:45:39Z

@aidanheerdegen -

We agreed at some point it was ok to have multiple specs where the different specs represent different processor layouts, but i can't remember if we resolved all the CI related things about it.

It's not currently possible:

If using:

    - access-om2@git.2026.02.000 ^cice5 nxglob=360 nyglob=300 blckx=15 blcky=300 mxblcks=1
    - access-om2 ^cice5 nxglob=1440 nyglob=1080 blckx=30 blcky=27 mxblcks=4
    - access-om2 ^cice5 nxglob=3600 nyglob=2700 blckx=40 blcky=30 mxblcks=12

then the 'Check Spack Manifest' step fails as the specs don't have versions

If using

    - access-om2@git.2026.02.000 ^cice5 nxglob=360 nyglob=300 blckx=15 blcky=300 mxblcks=1
    - access-om2@git.2026.02.000 ^cice5 nxglob=1440 nyglob=1080 blckx=30 blcky=27 mxblcks=4
    - access-om2@git.2026.02.000 ^cice5 nxglob=3600 nyglob=2700 blckx=40 blcky=30 mxblcks=12

then pre-release concretisation fails as git.2026.02.000 doesn't exist (yet) and only the version for the first line of the spec gets injected (repalced) by pre-release

aidanheerdegen · 2026-02-03T23:14:37Z

We agreed at some point it was ok to have multiple specs where the different specs represent different processor layouts, but i can't remember if we resolved all the CI related things about it.

I don't think I agreed that we would do releases like this: I am concerned about the provenance issues and potential confusion for users.

Why is it necessary to have a release with 3 different cice layouts?

Pre-release I'm ok with, but this may require v8 to be merged, which contains the update to do away with the clunky version approach and use reserved definitions instead.

Does it deploy to pre-release if it is a draft?

anton-seaice · 2026-02-18T22:03:24Z

We moved to spack v1.1 last week, so rather than rebase this PR - I've moved this to #135 and this can be kept for record / reference

Update access-generic-tracers to 2026.01.000

714e94f

dougiesquire temporarily deployed to Gadi Prerelease February 2, 2026 00:00 — with GitHub Actions Inactive

anton-seaice had a problem deploying to Gadi Prerelease February 2, 2026 00:20 — with GitHub Actions Failure

anton-seaice changed the title ~~Release 2026.01.000~~ Release 2026.02.000 Feb 2, 2026

anton-seaice force-pushed the rc-2026.01.000 branch from 9034c5b to 809acb8 Compare February 2, 2026 01:44

anton-seaice temporarily deployed to Gadi Prerelease February 2, 2026 01:45 — with GitHub Actions Inactive

access-bot mentioned this pull request Feb 2, 2026

Auto update dev-1deg_jra55_ryf to use access-om2/pr133-4 ACCESS-NRI/access-om2-configs#250

Closed

anton-seaice reviewed Feb 2, 2026

View reviewed changes

spack.yaml Outdated Show resolved Hide resolved

dougiesquire temporarily deployed to Gadi Prerelease February 2, 2026 02:16 — with GitHub Actions Inactive

dougiesquire temporarily deployed to Gadi Prerelease February 2, 2026 02:22 — with GitHub Actions Inactive

access-bot mentioned this pull request Feb 2, 2026

Auto update dev-1deg_jra55_ryf to use access-om2/pr133-6 ACCESS-NRI/access-om2-configs#251

Closed

This was referenced Feb 2, 2026

Repro testing ACCESS-OM2 2026.02.000: dev-025deg_jra55_ryf ACCESS-NRI/access-om2-configs#252

Closed

Repro testing ACCESS-OM2 2026.02.000: dev-01deg_jra55_ryf ACCESS-NRI/access-om2-configs#253

Closed

dougiesquire force-pushed the rc-2026.01.000 branch from 5308e1c to 3610070 Compare February 2, 2026 04:15

dougiesquire temporarily deployed to Gadi Prerelease February 2, 2026 04:16 — with GitHub Actions Inactive

anton-seaice reviewed Feb 2, 2026

View reviewed changes

spack.yaml Outdated Show resolved Hide resolved

dougiesquire temporarily deployed to Gadi Prerelease February 2, 2026 04:33 — with GitHub Actions Inactive

anton-seaice and others added 2 commits February 2, 2026 17:01

Use CICE5 2026.01.000 with CMake, and expose layout/io options to user

4caa5a7

Update access-om2 version to 2026.02.000

cb206a7

dougiesquire force-pushed the rc-2026.01.000 branch from a929a9a to cb206a7 Compare February 2, 2026 06:02

dougiesquire temporarily deployed to Gadi Prerelease February 2, 2026 06:02 — with GitHub Actions Inactive

dougiesquire marked this pull request as ready for review February 2, 2026 06:31

dougiesquire requested a review from anton-seaice February 2, 2026 06:32

anton-seaice reviewed Feb 2, 2026

View reviewed changes

anton-seaice mentioned this pull request Feb 2, 2026

Build a model for debugging section for CICE5 can be updated ACCESS-NRI/ACCESS-Hive-Docs#1137

Closed

anton-seaice marked this pull request as draft February 18, 2026 21:58

anton-seaice closed this Feb 18, 2026

anton-seaice deleted the rc-2026.01.000 branch February 18, 2026 22:03

anton-seaice mentioned this pull request Feb 18, 2026

CICE5 CMake Build #126

Closed

dougiesquire mentioned this pull request Feb 18, 2026

Release 2026.02.000 v2 #135

Merged

2 tasks

CodeGat mentioned this pull request Feb 19, 2026

Release 2026.02.000 v2 (Recreated) #137

Merged

2 tasks

	access-om2: '{name}/2026.02.000-{^cice5.variants.nxglob.value}x{^cice5.variants.nyglob.value}'
	access-om2: '{name}/{^cice5.variants.nxglob.value}x{^cice5.variants.nyglob.value}'

Conversation

dougiesquire commented Feb 1, 2026 • edited by anton-seaice Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dougiesquire commented Feb 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 2, 2026

🖥️ Gadi Deployment ❌

Uh oh!

anton-seaice commented Feb 2, 2026

Uh oh!

github-actions bot commented Feb 2, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

anton-seaice commented Feb 2, 2026

Uh oh!

github-actions bot commented Feb 2, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Feb 2, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

dougiesquire commented Feb 2, 2026

Uh oh!

github-actions bot commented Feb 2, 2026

Uh oh!

anton-seaice commented Feb 2, 2026

Uh oh!

Uh oh!

github-actions bot commented Feb 2, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Feb 2, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

dougiesquire commented Feb 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 2, 2026

Uh oh!

Uh oh!

github-actions bot commented Feb 2, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Feb 2, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Feb 2, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

dougiesquire commented Feb 2, 2026

Uh oh!

github-actions bot commented Feb 2, 2026

🖥️ Gadi Deployment ❌

Uh oh!

dougiesquire commented Feb 2, 2026

Uh oh!

anton-seaice commented Feb 2, 2026

Uh oh!

anton-seaice Feb 2, 2026

Choose a reason for hiding this comment

Uh oh!

anton-seaice commented Feb 2, 2026

Uh oh!

anton-seaice Feb 2, 2026

Choose a reason for hiding this comment

Uh oh!

anton-seaice Feb 2, 2026

Choose a reason for hiding this comment

Uh oh!

anton-seaice commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

aidanheerdegen commented Feb 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

anton-seaice commented Feb 18, 2026

Uh oh!

Reviewers

dougiesquire commented Feb 1, 2026 •

edited by anton-seaice

Loading

dougiesquire commented Feb 1, 2026 •

edited

Loading

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

dougiesquire commented Feb 2, 2026 •

edited

Loading

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ❌

anton-seaice commented Feb 3, 2026 •

edited

Loading

aidanheerdegen commented Feb 3, 2026 •

edited

Loading