Skip to content

Wave-induced ice fracture development#211

Draft
NoahDay wants to merge 17 commits intomainfrom
ice-fracture
Draft

Wave-induced ice fracture development#211
NoahDay wants to merge 17 commits intomainfrom
ice-fracture

Conversation

@NoahDay
Copy link
Copy Markdown
Collaborator

@NoahDay NoahDay commented Mar 19, 2026

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


🚀 The latest prerelease access-om3/pr211-18 at 60b2b77 is here: #211 (comment) 🚀

@github-actions
Copy link
Copy Markdown

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

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

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

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Copy Markdown
Collaborator

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

@anton-seaice
Copy link
Copy Markdown
Collaborator

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

@NoahDay
Copy link
Copy Markdown
Collaborator Author

NoahDay commented Mar 19, 2026

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
Copy link
Copy Markdown
Collaborator

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)

@NoahDay NoahDay temporarily deployed to Gadi Prerelease March 19, 2026 05:13 — with GitHub Actions Inactive
@github-actions
Copy link
Copy Markdown

🚀 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:

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
Copy link
Copy Markdown
Collaborator Author

NoahDay commented Mar 25, 2026

!redeploy

@anton-seaice
Copy link
Copy Markdown
Collaborator

anton-seaice commented Mar 25, 2026

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 NoahDay temporarily deployed to Gadi Prerelease March 25, 2026 05:27 — with GitHub Actions Inactive
@NoahDay
Copy link
Copy Markdown
Collaborator Author

NoahDay commented Mar 25, 2026

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
Copy link
Copy Markdown

🚀 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:

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 NoahDay temporarily deployed to Gadi Prerelease March 25, 2026 23:45 — with GitHub Actions Inactive
@github-actions
Copy link
Copy Markdown

🚀 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:

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
Copy link
Copy Markdown

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

🖥️ Gadi Deployment ❌

@NoahDay NoahDay temporarily deployed to Gadi Prerelease March 26, 2026 01:25 — with GitHub Actions Inactive
@github-actions
Copy link
Copy Markdown

🚀 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:

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 NoahDay temporarily deployed to Gadi Prerelease March 26, 2026 03:19 — with GitHub Actions Inactive
@github-actions
Copy link
Copy Markdown

🚀 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:

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 NoahDay temporarily deployed to Gadi Prerelease March 27, 2026 01:28 — with GitHub Actions Inactive
@github-actions
Copy link
Copy Markdown

🚀 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:

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
Copy link
Copy Markdown

github-actions bot commented Apr 2, 2026

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

🖥️ Gadi Deployment ❌

@NoahDay NoahDay temporarily deployed to Gadi Prerelease April 2, 2026 03:13 — with GitHub Actions Inactive
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 2, 2026

🚀 Attempted to deploy access-om3 Prerelease pr211-12 with commit 22fe1ca

🖥️ 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-12 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-12

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-12 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:

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
Copy link
Copy Markdown

github-actions bot commented Apr 2, 2026

🚀 Attempted to deploy access-om3 Prerelease pr211-13 with commit e82a18f

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 2, 2026

🚀 Attempted to deploy access-om3 Prerelease pr211-14 with commit f42dba2

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 2, 2026

🚀 Attempted to deploy access-om3 Prerelease pr211-15 with commit 42a5a6d

🖥️ Gadi Deployment ❌

@NoahDay NoahDay temporarily deployed to Gadi Prerelease April 2, 2026 05:16 — with GitHub Actions Inactive
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 2, 2026

🚀 Attempted to deploy access-om3 Prerelease pr211-16 with commit 6fc6795

🖥️ 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-16 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-16

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-16 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:

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 NoahDay temporarily deployed to Gadi Prerelease April 9, 2026 06:29 — with GitHub Actions Inactive
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 9, 2026

🚀 Attempted to deploy access-om3 Prerelease pr211-17 with commit 2212ec9

🖥️ 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-17 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-17

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-17 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:

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 NoahDay deployed to Gadi Prerelease April 9, 2026 07:22 — with GitHub Actions Active
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 9, 2026

🚀 Attempted to deploy access-om3 Prerelease pr211-18 with commit 60b2b77

🖥️ 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-18 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-18

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-18 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:

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants