Skip to content

Regional update coupled names#208

Draft
ashjbarnes wants to merge 54 commits intomainfrom
regional-update-coupled-names
Draft

Regional update coupled names#208
ashjbarnes wants to merge 54 commits intomainfrom
regional-update-coupled-names

Conversation

@ashjbarnes
Copy link
Copy Markdown
Collaborator

@ashjbarnes ashjbarnes commented Mar 13, 2026

This builds on @kieranricardo 's recent branch (update-coupled-names). The only difference is that I've needed to

  1. turn of CICE
  2. alter the cmeps mediator file to remove the hardcoded ice fields in the mediator, so that when ice is turned off for a regional configuration, the mediator doesn't fail when it can't find ice fields

Eventually we want to set things up so that we can share the regional and global cm3 code, but for now I'm trying to keep the rcm3 exe as close as possible to cm3 with a few lines of commented out code sprinkled throughout:
CMEPS, UM and ACCESS-CM3-CONFIGS

See https://github.com/ACCESS-NRI/access-cm3-configs/issues/38

Thanks @anton-seaice for all his help!


🚀 The latest prerelease access-om3/pr208-11 at 43a3cbd is here: #208 (comment) 🚀

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr208-1 with commit 757a824

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr208-2 with commit 757a824

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Copy Markdown
Collaborator

!redeploy

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr208-3 with commit 757a824

🖥️ Gadi Deployment ❌

1 similar comment
@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr208-3 with commit 757a824

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr208-4 with commit 76497c5

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.999 as a Release (when merged).
  • pr208-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/pr208-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-pr208-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:

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 pr208-5 with commit c02c249

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr208-6 with commit 6f19e25

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr208-7 with commit a6a626a

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.999 as a Release (when merged).
  • pr208-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr208-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/1.1/spack in the access-om3-pr208-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:

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 pr208-7 with commit 5f691bc

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.999 as a Release (when merged).
  • pr208-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr208-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/1.1/spack in the access-om3-pr208-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:

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.

@ashjbarnes
Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr208-9 with commit c5eca93

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.999 as a Release (when merged).
  • pr208-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/pr208-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-pr208-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.

@ashjbarnes
Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr208-10 with commit 8e02d70

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.999 as a Release (when merged).
  • pr208-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/pr208-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-pr208-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.

@ashjbarnes
Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr208-11 with commit 43a3cbd

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.999 as a Release (when merged).
  • pr208-11 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr208-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/1.1/spack in the access-om3-pr208-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:

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.

3 participants