Skip to content

MOM6 symmetric with ice shelf debugging#142

Draft
claireyung wants to merge 50 commits intomainfrom
cy-pananopt-2.0
Draft

MOM6 symmetric with ice shelf debugging#142
claireyung wants to merge 50 commits intomainfrom
cy-pananopt-2.0

Conversation

@claireyung
Copy link
Collaborator

@claireyung claireyung commented Aug 27, 2025 •
edited by github-actions bot
Loading

do not merge!

This PR is to generate prereleases for MOM6 symmetric with ice shelves. Builds on #120 but rebased onto recent CD updates.

First commits get rid of debug mode from the above PR and then update the MOM6 to point to a version with small change to nuopc mom cap mom-ocean/MOM6@667aded

🚀 The latest prerelease access-om3/pr142-36 at f2a17e4 is here: #142 (comment) 🚀

Edward Yang and others added 23 commits August 27, 2025 15:40
@claireyung
+mom_symmetric
6e8e6e4
@claireyung
remove +mom_symmetric, +asymmetric_mem
b2fc7da
@claireyung
Change MOM6 commit reference in spack.yaml to add recent GFDL mom-oce…
219e7b6 
…an merge and small index bug
@claireyung
Attempt to fix notation according to https://github.com/ACCESS-NRI/mo…
d7a0e27 
…del-deployment-template/blob/main/spack.yaml
@claireyung
Update git version of MOM6 after Dougie rebased it
81fde52
@dougiesquire @claireyung
Update to %oneapi@2025.1.1
649a2c8
@dougiesquire @claireyung
Use %oneapi@2025.0.4 for FMS only
2262c26
@dougiesquire @claireyung
MOM6 with %oneapi@2025.1.1, everything else with %oneapi@2025.0.4
b0514fb
@dougiesquire @claireyung
Explicitly set compiler for each package
4750017
@dougiesquire @claireyung
This should work too?
f04ab9f
@claireyung
Revert "This should work too?"
581ac44 
This reverts commit 3528122.
@claireyung
Add MOM6 version with print statements in config_src/drivers/nuopc_ca…
2711750 
…p/mom_cap.F90
@claireyung
Update code trying to set dirs%input_filename in nuopc cap to get ice…
4189742 
… shelf to read it
@claireyung
Update git ref on MOM6 to no print statements
36320e5
@claireyung
Make a guess on how to make a debug executable cy-pananopt...om3-mom6…
061cbeb 
…-debug-example
@claireyung
Try again removing debug mode for some components
a7e794e
@claireyung
Try changes in https://github.com/ACCESS-NRI/ACCESS-OM3/pull/97/files
bf6c988 
ffflags instead of build_type=debug
@dougiesquire @claireyung
Use %oneapi@2025.2.0
ebbaee3 
Use spack-packages branch use-default-flag-handler
Update access-generic-tracers and access-mocsy
@anton-seaice @claireyung
Update cice to fix error found in debug build
9e8be86
@anton-seaice @claireyung
Update spack.yaml
976fc51
@anton-seaice @claireyung
Update spack.yaml
e7d376f
@claireyung
Remove debug mode ffflags from https://github.com/ACCESS-NRI/ACCESS-O…
33ca2e2 
…M3/tree/b751c08461cc95eb330b8b504aae0bd1f24a3c7e
@claireyung
Point MOM6 to https://github.com/mom-ocean/MOM6/tree/667aded12584a68c…
e2d2c1f 
…303cbec8441c0599f705fd09
@github-actions
Copy link

github-actions bot commented Aug 27, 2025

🚀 Attempted to deploy access-om3 Prerelease pr142-1 with commit e2d2c1f

🖥️ Gadi Deployment ❌

@github-actions
Copy link

github-actions bot commented Aug 27, 2025

🚀 Attempted to deploy access-om3 Prerelease pr142-2 with commit 579b4a1

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.05.001 as a Release (when merged).
  • pr142-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr142-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-om3-pr142-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:

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

@github-actions
Copy link

github-actions bot commented Dec 10, 2025

🚀 Attempted to deploy access-om3 Prerelease pr142-28 with commit b35296e

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.000/3jaaghfgv as a Release (when merged).
  • pr142-28 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr142-28

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-pr142-28 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.

@claireyung
Copy link
Collaborator Author

claireyung commented Dec 11, 2025

!redeploy

@github-actions
Copy link

github-actions bot commented Dec 11, 2025

🚀 Attempted to deploy access-om3 Prerelease pr142-29 with commit b35296e

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.000/3jaaghfgv as a Release (when merged).
  • pr142-29 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr142-29

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-pr142-29 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

github-actions bot commented Dec 11, 2025

🚀 Attempted to deploy access-om3 Prerelease pr142-30 with commit 61eafdc

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.001 as a Release (when merged).
  • pr142-30 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr142-30

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-pr142-30 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

github-actions bot commented Dec 17, 2025

🚀 Attempted to deploy access-om3 Prerelease pr142-31 with commit 0455a71

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.001 as a Release (when merged).
  • pr142-31 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr142-31

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-pr142-31 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

github-actions bot commented Dec 17, 2025

🚀 Attempted to deploy access-om3 Prerelease pr142-32 with commit 4cf65a8

🖥️ Gadi Deployment ❌

@claireyung
Copy link
Collaborator Author

claireyung commented Dec 17, 2025

!redeploy

@github-actions
Copy link

github-actions bot commented Dec 17, 2025

🚀 Attempted to deploy access-om3 Prerelease pr142-33 with commit 4cf65a8

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.001 as a Release (when merged).
  • pr142-33 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr142-33

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-pr142-33 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

github-actions bot commented Jan 8, 2026

🚀 Attempted to deploy access-om3 Prerelease pr142-34 with commit f2a17e4

🖥️ Gadi Deployment ❌

@claireyung
Copy link
Collaborator Author

claireyung commented Jan 8, 2026

!redeploy

1 similar comment
@claireyung
Copy link
Collaborator Author

claireyung commented Jan 9, 2026

!redeploy

@github-actions
Copy link

github-actions bot commented Jan 9, 2026

🚀 Attempted to deploy access-om3 Prerelease pr142-36 with commit f2a17e4

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.001 as a Release (when merged).
  • pr142-36 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr142-36

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-pr142-36 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.

@claireyung claireyung mentioned this pull request Jan 12, 2026
Draft
claireyung added a commit to claireyung/access-om3-configs that referenced this pull request Jan 14, 2026
@claireyung
Swap to non-debug exe ACCESS-NRI/ACCESS-OM3#142 (comment)
b3bbff0
dougiesquire added a commit that referenced this pull request Feb 17, 2026
@dougiesquire
MOM6 at latest on gfdl@ae752b6+access+isf
5623260 
Also updated compiler flags following #142

Also update to ESMF 8.8.1
@dougiesquire dougiesquire mentioned this pull request Feb 18, 2026
Draft
dougiesquire added a commit that referenced this pull request Feb 18, 2026
@dougiesquire
MOM6 at latest on dev/gfdl+access+isf
a3f667a 
Also updated compiler flags following #142

Also update to ESMF 8.8.1
@dougiesquire dougiesquire mentioned this pull request Feb 18, 2026
Open
dougiesquire added a commit that referenced this pull request Feb 19, 2026
@dougiesquire
Add lto flags for cice
e5a500e 
These were not included in #142 but are in #148
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@claireyung @dougiesquire @minghangli-uni @anton-seaice