Wave-induced ice fracture development by NoahDay · Pull Request #211 · ACCESS-NRI/ACCESS-OM3

NoahDay · 2026-03-19T00:51:45Z

This is a draft PR to test new wave-induced ice fracture parameterisation in Icepack (CICE)

🚀 The latest prerelease access-om3/pr211-10 at 7bf4467 is here: #211 (comment) 🚀

github-actions · 2026-03-19T01:02:58Z

🚀 Attempted to deploy access-om3 Prerelease pr211-1 with commit 690b62d

🖥️ `Gadi` Deployment ❌

github-actions · 2026-03-19T01:16:39Z

🚀 Attempted to deploy access-om3 Prerelease pr211-2 with commit f06abce

🖥️ `Gadi` Deployment ❌

anton-seaice · 2026-03-19T01:52:00Z

Do you have write access to https://github.com/accESS-NRI/cice ?

anton-seaice · 2026-03-19T01:52:23Z

Youll need to make a branch with the changes at https://github.com/accESS-NRI/cice

NoahDay · 2026-03-19T02:06:11Z

Thanks @anton-seaice! To make changes in Icepack do I need to make a branch in https://github.com/ACCESS-NRI/Icepack too? Or can I .gitmodules the CICE branch to my version?

anton-seaice · 2026-03-19T04:45:36Z

Or can I .gitmodules the CICE branch to my version?

This should work fine

(it should be ok to point the icepack submodule to your fork)

github-actions · 2026-03-19T05:28:22Z

🚀 Attempted to deploy access-om3 Prerelease pr211-3 with commit e55540c

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2026.03.001 as a Release (when merged).
pr211-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr211-3

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-pr211-3 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
spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
access-nri/access-spack-packages version 2026.03.003
access-nri/spack-config version 2026.02.003

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.

NoahDay · 2026-03-25T05:10:42Z

!redeploy

anton-seaice · 2026-03-25T05:24:58Z

spack.yaml

-  definitions:
-  - _name: [access-om3]
-  - _version: [2026.03.000]
  specs:


Suggested change

specs:

# _name and _version are reserved definitions that inform deployments

definitions:

- _name: [access-om3]

- _version: [2025.08.001]

specs:

Between access-om3 2025.08.001 and 2026.03.000 we changed spack versions, and the new version requires this section

(Note the builds will be optimised slightly differently as well, we can fiddle with the target if you ened them identical to an old build)

anton-seaice · 2026-03-25T05:25:29Z

spack.yaml

+    gcc-runtime:
      require:
-      - 'intel-oneapi-compilers@2025.2.0'
-    cxx:
-      require:
-      - 'intel-oneapi-compilers@2025.2.0'
-    fortran:
-      require:
-      - 'intel-oneapi-compilers@2025.2.0'
-
+        - '%gcc'
    all:
-      prefer:
-      - 'target=x86_64_v4'
+      require:
+        - '%oneapi@2025.2.0'
+        - 'target=x86_64_v4'


Suggested change

gcc-runtime:

require:

- 'intel-oneapi-compilers@2025.2.0'

cxx:

require:

- 'intel-oneapi-compilers@2025.2.0'

fortran:

require:

- 'intel-oneapi-compilers@2025.2.0'

- '%gcc'

all:

prefer:

- 'target=x86_64_v4'

require:

- '%oneapi@2025.2.0'

- 'target=x86_64_v4'

# Compilers

c:

require:

- 'intel-oneapi-compilers@2025.2.0'

cxx:

require:

- 'intel-oneapi-compilers@2025.2.0'

fortran:

require:

- 'intel-oneapi-compilers@2025.2.0'

all:

prefer:

- 'target=x86_64_v4'

anton-seaice · 2026-03-25T05:26:35Z

Alternatively, starting from https://github.com/ACCESS-NRI/ACCESS-OM3/blob/2025.08.002/spack.yaml will be BFB with 2025.08.001 and setup for spack 1.1

NoahDay · 2026-03-25T05:30:16Z

Thanks @anton-seaice!

Alternatively, starting from https://github.com/ACCESS-NRI/ACCESS-OM3/blob/2025.08.002/spack.yaml will be BFB with 2025.08.001

I've fudged around to try and get spack.yaml compatible with the version, but starting over with this makes sense.

github-actions · 2026-03-25T05:44:44Z

🚀 Attempted to deploy access-om3 Prerelease pr211-5 with commit f20f392

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.08.002 as a Release (when merged).
pr211-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/pr211-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-pr211-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
spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
access-nri/access-spack-packages version 2026.03.003
access-nri/spack-config version 2026.02.003

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 · 2026-03-26T00:00:55Z

🚀 Attempted to deploy access-om3 Prerelease pr211-6 with commit 02c630d

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.08.002 as a Release (when merged).
pr211-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr211-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/1.1/spack in the access-om3-pr211-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 1.1
spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
access-nri/access-spack-packages version 2026.03.003
access-nri/spack-config version 2026.02.003

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 · 2026-03-26T01:01:43Z

🚀 Attempted to deploy access-om3 Prerelease pr211-7 with commit 72f013c

🖥️ `Gadi` Deployment ❌

github-actions · 2026-03-26T01:49:01Z

🚀 Attempted to deploy access-om3 Prerelease pr211-8 with commit 2f11748

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.08.002 as a Release (when merged).
pr211-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/pr211-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-pr211-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
spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
access-nri/access-spack-packages version 2026.03.003
access-nri/spack-config version 2026.02.003

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 · 2026-03-26T03:30:14Z

🚀 Attempted to deploy access-om3 Prerelease pr211-9 with commit 3fc39bb

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.08.002 as a Release (when merged).
pr211-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr211-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-om3-pr211-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
spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
access-nri/access-spack-packages version 2026.03.003
access-nri/spack-config version 2026.02.003

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 · 2026-03-27T01:41:32Z

🚀 Attempted to deploy access-om3 Prerelease pr211-10 with commit 7bf4467

🖥️ `Gadi` Deployment ✔️

Usage Instructions

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

2025.08.002 as a Release (when merged).
pr211-10 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr211-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-om3-pr211-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
spack/spack-packages version 383e969358c951abe17623696083e6f862c4488e
access-nri/access-spack-packages version 2026.03.003
access-nri/spack-config version 2026.02.003

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.

Pointing to my CICE and icepack fork

690b62d

NoahDay had a problem deploying to Gadi Prerelease March 19, 2026 00:55 — with GitHub Actions Failure

Pointing to my fork

f06abce

NoahDay had a problem deploying to Gadi Prerelease March 19, 2026 01:09 — with GitHub Actions Failure

Pointing to ACCESS-NRI/CICE branch

e55540c

NoahDay temporarily deployed to Gadi Prerelease March 19, 2026 05:13 — with GitHub Actions Inactive

Copying ERA5-forcing

f20f392

anton-seaice reviewed Mar 25, 2026

View reviewed changes

NoahDay force-pushed the ice-fracture branch from 4437753 to f20f392 Compare March 25, 2026 05:25

NoahDay temporarily deployed to Gadi Prerelease March 25, 2026 05:27 — with GitHub Actions Inactive

Checkout from 2025.08.002

02c630d

NoahDay temporarily deployed to Gadi Prerelease March 25, 2026 23:45 — with GitHub Actions Inactive

Pointing to WW3 IC4 Numerics

72f013c

NoahDay had a problem deploying to Gadi Prerelease March 26, 2026 00:34 — with GitHub Actions Failure

access3-share from ERA5-forcing

2f11748

NoahDay temporarily deployed to Gadi Prerelease March 26, 2026 01:25 — with GitHub Actions Inactive

Reverting back to 2025.08.002 but now pointing to CICE branch

3fc39bb

NoahDay temporarily deployed to Gadi Prerelease March 26, 2026 03:19 — with GitHub Actions Inactive

Updating WW3 to 2026.03.000

7bf4467

NoahDay temporarily deployed to Gadi Prerelease March 27, 2026 01:28 — with GitHub Actions Inactive

Conversation

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

Uh oh!

Uh oh!

github-actions bot commented Mar 19, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Mar 19, 2026

🖥️ Gadi Deployment ❌

Uh oh!

anton-seaice commented Mar 19, 2026

Uh oh!

anton-seaice commented Mar 19, 2026

Uh oh!

NoahDay commented Mar 19, 2026

Uh oh!

anton-seaice commented Mar 19, 2026

Uh oh!

github-actions bot commented Mar 19, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

NoahDay commented Mar 25, 2026

Uh oh!

anton-seaice Mar 25, 2026

Choose a reason for hiding this comment

Uh oh!

anton-seaice Mar 25, 2026

Choose a reason for hiding this comment

Uh oh!

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

Uh oh!

Uh oh!

NoahDay commented Mar 25, 2026

Uh oh!

github-actions bot commented Mar 25, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Mar 26, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Mar 26, 2026

🖥️ Gadi Deployment ❌

Uh oh!

github-actions bot commented Mar 26, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Mar 26, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

github-actions bot commented Mar 27, 2026

🖥️ Gadi Deployment ✔️

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

NoahDay commented Mar 19, 2026 •

edited by github-actions bot

Loading

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

anton-seaice commented Mar 25, 2026 •

edited

Loading

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ❌

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️

🖥️ `Gadi` Deployment ✔️