Change to using ACCESS-NRI organisation OASIS3-mct code by aidanheerdegen · Pull Request #181 · ACCESS-NRI/ACCESS-ESM1.6

aidanheerdegen · 2026-01-26T22:40:32Z

This PR will close #179 by specifying a version of OASIS3-mct that uses code from the ACCESS-NRI organisation fork.

Will also close #117 (reorder packages) and hopefully close #180 (use all spack versions) at the same time.

🚀 The latest prerelease access-esm1p6/pr181-13 at 0693b5e is here: #181 (comment) 🚀

aidanheerdegen · 2026-01-26T22:57:18Z

CD was too smart and didn't fire with initial commit because there was no change to spack.yaml. Have done the rearrangement for #117 as it should be as close as possible to previous release.

github-actions · 2026-01-26T23:00:47Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr181-1 with commit 5fe3919

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.12.001 as a Release (when merged).
pr181-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/pr181-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-pr181-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 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.

aidanheerdegen · 2026-01-26T23:02:34Z

As a first step, @manodeep can you comment if you are happy with the rearrangement to fix your issue (#117)?

github-actions · 2026-01-26T23:08:45Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr181-2 with commit 341cae7

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.12.001 as a Release (when merged).
pr181-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/pr181-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-pr181-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 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.

aidanheerdegen · 2026-01-27T01:41:04Z

Testing in ACCESS-NRI/access-esm1.6-configs#403.

Up to this point is bitwise reproducible. 🥳

manodeep · 2026-01-27T01:54:56Z

As a first step, @manodeep can you comment if you are happy with the rearrangement to fix your issue (#117)?

@aidanheerdegen Thanks for reordering the packages - that looks good to me!

Since you are in the process of doing the update anyway, it might be worthwhile to upgrade to the latest v6 from upstream (assuming the results are bitwise identical)

aidanheerdegen · 2026-01-27T03:16:24Z

As a first step, @manodeep can you comment if you are happy with the rearrangement to fix your issue (#117)?

@aidanheerdegen Thanks for reordering the packages - that looks good to me!

👍

Since you are in the process of doing the update anyway, it might be worthwhile to upgrade to the latest v6 from upstream (assuming the results are bitwise identical)

Wouldn't that entail performance testing v6 as well? If so we'd want to make sure it was worth it.

The differences between v5 and v6 are detailed here:

https://gitlab.com/cerfacs/oasis3-mct/-/blob/release/v6/doc/UGA4_changes.tex?ref_type=heads#L23-48

github-actions · 2026-01-30T05:57:06Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr181-3 with commit 1080da5

🖥️ `Gadi` Deployment ❌

github-actions · 2026-01-30T06:25:23Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr181-4 with commit e611ed9

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.12.001 as a Release (when merged).
pr181-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr181-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-esm1p6-pr181-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 4814c0c1ec71cbd4c1bf437c697ee72cd2043332
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.

aidanheerdegen · 2026-01-30T07:11:04Z

Checked the build logs and they seem to have the most recent versions of the UM flags modified by @manodeep

mpif90 -o overlap_mix_maximum.o -I/scratch/tm70/tm70_ci/tmp/restricted/spack-stage/spack-stage-um7-git.2025.12.000_access-esm1.6-oz4papayiyljxealpwptlbgzzd56wdyp/spack-src/ummodel_hg3/inc -I/scratch/tm70/tm70_ci/tmp/restricted/spack-stage/spack-stage-um7-git.2025.12.000_access-esm1.6-oz4papayiyljxealpwptlbgzzd56wdyp/spack-src/umbase_hg3/inc -O2 -unroll  -g   -traceback   -i8 -r8      -fp-model precise -ftz -what -fno-alias -stack-temps -safe-cray-ptr -c /scratch/tm70/tm70_ci/tmp/restricted/spack-stage/spack-stage-um7-git.2025.12.000_access-esm1.6-oz4papayiyljxealpwptlbgzzd56wdyp/spack-src/ummodel_hg3/ppsrc/atmosphere/radiation_service/overlap_mix_maximum.f90

github-actions · 2026-01-30T07:24:21Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr181-5 with commit 5be6e92

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.12.001 as a Release (when merged).
pr181-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr181-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-esm1p6-pr181-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-01-30T07:24:23Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr181-6 with commit 8dac769

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.01.000 as a Release (when merged).
pr181-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/pr181-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-pr181-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.

github-actions · 2026-01-30T07:25:28Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr181-6 with commit 8dac769

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.01.000 as a Release (when merged).
pr181-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/pr181-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-pr181-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.

github-actions · 2026-01-30T07:36:54Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr181-8 with commit cb228e8

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.01.000 as a Release (when merged).
pr181-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr181-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-esm1p6-pr181-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.

aidanheerdegen · 2026-01-30T09:55:34Z

Confirmed bitwise identical for dev-historical+concentrations with access-esm1p6/pr181-8.

This is ready to merge subject to review.

github-actions · 2026-02-01T21:54:08Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr181-9 with commit b7dee39

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.01.000 as a Release (when merged).
pr181-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr181-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-esm1p6-pr181-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.

github-actions · 2026-02-01T22:37:03Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr181-10 with commit 5115e40

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.01.000 as a Release (when merged).
pr181-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/pr181-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-pr181-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 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-01T23:11:58Z

Updates pass repro still:

ACCESS-NRI/access-esm1.6-configs#403 (comment)

Shall we clean up the commit history ?

…e grid layout to user

github-actions · 2026-02-01T23:42:40Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr181-11 with commit 74412fc

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.01.000 as a Release (when merged).
pr181-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/pr181-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-pr181-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 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

THanks @aidanheerdegen -

Use access-spack-packages version with UM optimisation changes reverted.

github-actions · 2026-02-02T23:40:24Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr181-12 with commit 0693b5e

🖥️ `Gadi` Deployment ❌

aidanheerdegen · 2026-02-02T23:41:08Z

I have split out the UM optimisation changes. Hasn't deployed because Gadi is in maintenance mode. Will rerun deployment when it is back up.

anton-seaice · 2026-02-03T22:28:25Z

!redeploy

github-actions · 2026-02-03T22:48:11Z

🚀 Attempted to deploy access-esm1p6 Prerelease pr181-13 with commit 0693b5e

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.01.000 as a Release (when merged).
pr181-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/pr181-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-pr181-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 2026.02.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.

aidanheerdegen marked this pull request as draft January 26, 2026 22:40

aidanheerdegen temporarily deployed to Gadi Prerelease January 26, 2026 22:53 — with GitHub Actions Inactive

aidanheerdegen temporarily deployed to Gadi Prerelease January 26, 2026 23:01 — with GitHub Actions Inactive

aidanheerdegen had a problem deploying to Gadi Prerelease January 30, 2026 05:52 — with GitHub Actions Failure

aidanheerdegen temporarily deployed to Gadi Prerelease January 30, 2026 05:54 — with GitHub Actions Inactive

aidanheerdegen mentioned this pull request Jan 30, 2026

The compiler flags for an optimised UM7 build ACCESS-NRI/access-spack-packages#376

Merged

aidanheerdegen temporarily deployed to Gadi Prerelease January 30, 2026 07:16 — with GitHub Actions Inactive

aidanheerdegen marked this pull request as ready for review January 30, 2026 07:17

aidanheerdegen temporarily deployed to Gadi Prerelease January 30, 2026 07:17 — with GitHub Actions Inactive

aidanheerdegen temporarily deployed to Gadi Prerelease January 30, 2026 07:18 — with GitHub Actions Inactive

aidanheerdegen temporarily deployed to Gadi Prerelease January 30, 2026 07:22 — with GitHub Actions Inactive

aidanheerdegen requested review from anton-seaice, blimlim and dougiesquire January 30, 2026 09:55

anton-seaice temporarily deployed to Gadi Prerelease February 1, 2026 21:44 — with GitHub Actions Inactive

anton-seaice temporarily deployed to Gadi Prerelease February 1, 2026 22:28 — with GitHub Actions Inactive

aidanheerdegen added 4 commits February 2, 2026 10:29

Reorder packages to address #117

4ae28a8

Change to oasis3-mct@5.2, and access-spack-packages to 2026.01.001 tag

d6ef369

Update access-esm1p6 version to 2026.01.000

7fe846c

Update CICE5 version to 2026.01.000. Switch to Cmake for CICE5, expos…

74412fc

…e grid layout to user

aidanheerdegen force-pushed the 179-oasis3-org branch from 5115e40 to 74412fc Compare February 1, 2026 23:32

aidanheerdegen temporarily deployed to Gadi Prerelease February 1, 2026 23:33 — with GitHub Actions Inactive

anton-seaice previously approved these changes Feb 1, 2026

View reviewed changes

aidanheerdegen mentioned this pull request Feb 2, 2026

Revert "The compiler flags for an optimised UM7 build (#376)" ACCESS-NRI/access-spack-packages#378

Merged

Update spack-packages version to 2026.02.000

0693b5e

Use access-spack-packages version with UM optimisation changes reverted.

aidanheerdegen dismissed anton-seaice’s stale review via 0693b5e February 2, 2026 23:39

aidanheerdegen had a problem deploying to Gadi Prerelease February 2, 2026 23:40 — with GitHub Actions Error

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

aidanheerdegen requested a review from anton-seaice February 4, 2026 00:56

anton-seaice approved these changes Feb 4, 2026

View reviewed changes

blimlim approved these changes Feb 4, 2026

View reviewed changes

aidanheerdegen merged commit 0b85eff into main Feb 4, 2026
8 of 10 checks passed

aidanheerdegen temporarily deployed to Gadi Prerelease February 4, 2026 04:20 — with GitHub Actions Inactive

anton-seaice mentioned this pull request Feb 4, 2026

Use spack versions for all packages #180

Open

Conversation

aidanheerdegen commented Jan 26, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

aidanheerdegen commented Jan 26, 2026

Uh oh!

github-actions bot commented Jan 26, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

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

Uh oh!

Uh oh!

github-actions bot commented Jan 26, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

aidanheerdegen commented Jan 27, 2026

Uh oh!

manodeep commented Jan 27, 2026

Uh oh!

aidanheerdegen commented Jan 27, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Jan 30, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

aidanheerdegen commented Jan 30, 2026

Uh oh!

github-actions bot commented Jan 30, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Jan 30, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Jan 30, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Jan 30, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

aidanheerdegen commented Jan 30, 2026

Uh oh!

github-actions bot commented Feb 1, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Feb 1, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

anton-seaice commented Feb 1, 2026

Uh oh!

github-actions bot commented Feb 1, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

anton-seaice left a comment

Choose a reason for hiding this comment

Uh oh!

github-actions bot commented Feb 2, 2026

🖥️ Gadi Deployment ❌

Uh oh!

aidanheerdegen commented Feb 2, 2026

Uh oh!

anton-seaice commented Feb 3, 2026

Uh oh!

github-actions bot commented Feb 3, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

aidanheerdegen commented Jan 26, 2026 •

edited by github-actions bot

Loading

🖥️ `Gadi` Deployment ✔️

aidanheerdegen commented Jan 26, 2026 •

edited

Loading

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️