Thanks to visit codestin.com
Credit goes to github.com

Skip to content

MOM6 symmetric with updated MOM6 version#120

Draft
claireyung wants to merge 22 commits into
mainfrom
cy-pananopt
Draft

MOM6 symmetric with updated MOM6 version#120
claireyung wants to merge 22 commits into
mainfrom
cy-pananopt

Conversation

@claireyung

@claireyung claireyung commented Jun 30, 2025

Copy link
Copy Markdown
Collaborator

do not merge!

Updated MOM6 version includes recent mom-ocean merge from GFDL and associated ice shelf pressure gradient fixes


🚀 The latest prerelease access-om3/pr120-19 at b751c08 is here: #120 (comment) 🚀

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-1 with commit f517777

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-2 with commit e6c881b

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jul 1, 2025

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-3 with commit 8f3d756

🖥️ Gadi Deployment ❌

@claireyung

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

github-actions Bot commented Jul 1, 2025

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-4 with commit 8f3d756

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jul 1, 2025

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-5 with commit a8a1390

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jul 1, 2025

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-6 with commit d7c4e58

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jul 1, 2025

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-7 with commit 122f32a

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jul 1, 2025

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-8 with commit dbac0ee

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jul 1, 2025

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-9 with commit 8a4755e

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.05.001 as a Release (when merged).
  • pr120-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/pr120-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-om3-pr120-9 environment.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@claireyung claireyung temporarily deployed to Gadi Prerelease July 2, 2025 23:27 — with GitHub Actions Inactive
@github-actions

github-actions Bot commented Jul 3, 2025

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-12 with commit 1129329

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.05.001 as a Release (when merged).
  • pr120-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/pr120-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/0.22/spack in the access-om3-pr120-12 environment.

Configuration Information

This Prerelease is deployed using:

If the above was not what was expected, commit changes to config/versions.json in this PR.

@github-actions

github-actions Bot commented Jul 6, 2025

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-13 with commit e70c883

🖥️ Gadi Deployment ❌

@github-actions

github-actions Bot commented Jul 6, 2025

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-14 with commit 2e32408

🖥️ Gadi Deployment ❌

@claireyung claireyung temporarily deployed to Gadi Prerelease July 7, 2025 01:16 — with GitHub Actions Inactive
@github-actions

github-actions Bot commented Jul 7, 2025

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-15 with commit 327f97c

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.05.001 as a Release (when merged).
  • pr120-15 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr120-15

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-om3-pr120-15 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.

Use spack-packages branch use-default-flag-handler
Update access-generic-tracers and access-mocsy
@github-actions

github-actions Bot commented Jul 8, 2025

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-16 with commit 949c849

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.05.001 as a Release (when merged).
  • pr120-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/pr120-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/0.22/spack in the access-om3-pr120-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.

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-17 with commit 124405b

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.05.001 as a Release (when merged).
  • pr120-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/pr120-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/0.22/spack in the access-om3-pr120-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.

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-18 with commit c4ad916

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.05.001 as a Release (when merged).
  • pr120-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/pr120-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/0.22/spack in the access-om3-pr120-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.

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr120-19 with commit b751c08

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.05.001 as a Release (when merged).
  • pr120-19 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr120-19

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-om3-pr120-19 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.

@access-hive-bot

Copy link
Copy Markdown

This pull request has been mentioned on ACCESS Hive Community Forum. There might be relevant details there:

https://forum.access-hive.org.au/t/setting-build-options-for-om3/4495/29

@access-hive-bot

Copy link
Copy Markdown

This pull request has been mentioned on ACCESS Hive Community Forum. There might be relevant details there:

https://forum.access-hive.org.au/t/the-road-to-regional-coupled-modelling-rcm3/4601/3

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.

4 participants