Skip to content

2025.08.000 Release#138

Merged
anton-seaice merged 18 commits intomainfrom
dev
Sep 1, 2025
Merged

2025.08.000 Release#138
anton-seaice merged 18 commits intomainfrom
dev

Conversation

@anton-seaice
Copy link
Copy Markdown
Collaborator

@anton-seaice anton-seaice commented Aug 13, 2025 •
edited by github-actions bot
Loading

New release with updates to all upstream components - as noted in ACCESS-NRI/access-om3-configs#632

🚀 The latest prerelease access-om3/pr138-30 at 2807b30 is here: #138 (comment) 🚀

@anton-seaice anton-seaice marked this pull request as ready for review August 13, 2025 06:26
@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 13, 2025

🚀 Attempted to deploy access-om3 Prerelease pr138-11 with commit 6dada80

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Copy Markdown
Collaborator Author

anton-seaice commented Aug 13, 2025

!redeploy

@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 13, 2025

🚀 Attempted to deploy access-om3 Prerelease pr138-11 with commit 6dada80

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 13, 2025

🚀 Attempted to deploy access-om3 Prerelease pr138-13 with commit 6dada80

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Copy Markdown
Collaborator Author

anton-seaice commented Aug 13, 2025

@dougiesquire - did I use the wrong FMS /oneapi ?

[ 99%] Built target fms_r8_f
     905    make  -f CMakeFiles/fms_r8.dir/build.make CMakeFiles/fms_r8.dir/dep
            end
  >> 906    make[2]: *** internal error: invalid --jobserver-auth string 'fifo:
            /scratch/tm70/***/tmp/GMfifo2269347'.  Stop.
  >> 907    make[1]: *** [CMakeFiles/Makefile2:227: CMakeFiles/fms_r8.dir/all] 
            Error 2
     908    make[1]: *** Waiting for unfinished jobs....

?

@anton-seaice
Copy link
Copy Markdown
Collaborator Author

anton-seaice commented Aug 13, 2025

It concretised:

^[email protected]%[email protected]~deprecated_io~gfs_phys+internal_file_nml~ipo+large_file~openmp~pic~quad_precision~yaml build_system=cmake build_type=Release constants=GFDL generator=make precision=32,64 arch=linux-rocky8-x86_64_v4

Maybe the .01 is the issue ?

@dougiesquire
Copy link
Copy Markdown
Collaborator

dougiesquire commented Aug 13, 2025

I've never tried @2025.02.01. Could you try @2025.03?

anton-seaice
anton-seaice commented Aug 13, 2025
View reviewed changes
@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 13, 2025

🚀 Attempted to deploy access-om3 Prerelease pr138-14 with commit f78dabb

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.000 as a Release (when merged).
  • pr138-14 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr138-14

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-pr138-14 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.

@anton-seaice
Copy link
Copy Markdown
Collaborator Author

anton-seaice commented Aug 14, 2025

I ran this for a year using ACCESS-NRI/access-om3-configs@52bf0b6:

image

I forgot the sea ice initial condition had changed, I think that's enough to explain the differencce?:

image image

There are quite a lot of changes to MOM_parameter_doc.all , these ones might be related, although it looks to me like they won't change behaviour:

TFREEZE_S_IS_PRACS = False      !   [Boolean] default = False
                                ! When True, the model will check if the model internal salinity is practical
                                ! salinity.  If the model uses absolute salinity, a conversion will be applied.
TFREEZE_T_IS_POTT = False       !   [Boolean] default = False
                                ! When True, the model will check if the model internal temperature is potential
                                ! temperature.  If the model uses conservative temperature, a conversion will be
                                ! applied.

@anton-seaice anton-seaice mentioned this pull request Aug 14, 2025
Closed
@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 18, 2025

🚀 Attempted to deploy access-om3 Prerelease pr138-15 with commit bc4fb6a

🖥️ Gadi Deployment ✔️

Usage Instructions

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

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

@anton-seaice anton-seaice mentioned this pull request Aug 21, 2025
Closed
5 tasks
@anton-seaice anton-seaice marked this pull request as draft August 21, 2025 02:14
@anton-seaice
Copy link
Copy Markdown
Collaborator Author

anton-seaice commented Aug 21, 2025

See linked issue above and comms from Dougie on issue with obc and generic tracers

@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 29, 2025

🚀 Attempted to deploy access-om3 Prerelease pr138-24 with commit 56cdc78

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Copy Markdown
Collaborator Author

anton-seaice commented Aug 29, 2025

!redeploy

@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 29, 2025

🚀 Attempted to deploy access-om3 Prerelease pr138-25 with commit 56cdc78

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 29, 2025

🚀 Attempted to deploy access-om3 Prerelease pr138-26 with commit c814236

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 29, 2025

🚀 Attempted to deploy access-om3 Prerelease pr138-26 with commit 6acdb62

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.08.000 as a Release (when merged).
  • pr138-26 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr138-26

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-pr138-26 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.

@anton-seaice
Copy link
Copy Markdown
Collaborator Author

anton-seaice commented Aug 29, 2025

Is there any reason not to hardcode a spack hash for esmf? @dougiesquire @aidanheerdegen - it avoids #12 , and makes future prerelease builds easier. The main downside is its a bit messy ?

I think we've concluded this won't work.

A spack hash is derived from a spec, but the relationship can't be untangled. e.g. you can't untangle the spec from the hash.

Specifying a hash only works where its already installed in an spack instance. e.g. if spack figured out once that was a hash to meet that spec, then you can request it gets re-used. but if spack doesn't know about the hash yet, it can't figure out what the spec should be to make that hash

(Sorry, gobbledygook ... its analog to saying you can't figure out a files' contents from a checksum)

@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 29, 2025

🚀 Attempted to deploy access-om3 Prerelease pr138-28 with commit 2807b30

🖥️ Gadi Deployment ❌

@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 29, 2025

🚀 Attempted to deploy access-om3 Prerelease pr138-27 with commit f7cd109

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Copy Markdown
Collaborator Author

anton-seaice commented Aug 29, 2025

!redeploy

@anton-seaice
Copy link
Copy Markdown
Collaborator Author

anton-seaice commented Aug 29, 2025

This should be ready to go no I think - see ACCESS-NRI/access-om3-configs#730 (comment) for some results

@github-actions
Copy link
Copy Markdown

github-actions bot commented Aug 29, 2025

🚀 Attempted to deploy access-om3 Prerelease pr138-29 with commit 2807b30

🖥️ Gadi Deployment ✔️

Usage Instructions

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

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

dougiesquire
dougiesquire approved these changes Aug 31, 2025
View reviewed changes
Copy link
Copy Markdown
Collaborator

@dougiesquire dougiesquire left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @anton-seaice - LGTM 🚀

@anton-seaice
Copy link
Copy Markdown
Collaborator Author

anton-seaice commented Sep 1, 2025 •
edited
Loading

This uses minor updates since the initial suggestion:

  • MOM6 -chosen to avoid open boundary conditions bug - see the release note in this link.
  • wombatlite - latest 2025.08.000

These two changes change answers

And from the initial suggestion:

The first four changes do not change answers, however updating the oneapi version does change answers. We didn't check if WW3 changes answers (i'd assume it does)

In an overall sense, this release changes answers, but global metrics looks unchanged, see ACCESS-NRI/access-om3-configs#730 (comment)

@anton-seaice anton-seaice marked this pull request as ready for review September 1, 2025 00:43
@anton-seaice
Copy link
Copy Markdown
Collaborator Author

anton-seaice commented Sep 1, 2025

@minghangli-uni - this should be ready to go. @dougiesquire and I are both happy - can you approve please?

minghangli-uni
minghangli-uni approved these changes Sep 1, 2025
View reviewed changes
Copy link
Copy Markdown
Collaborator

@minghangli-uni minghangli-uni left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM Thanks @anton-seaice

@anton-seaice anton-seaice merged commit cbe99b7 into main Sep 1, 2025
16 of 18 checks passed
@anton-seaice anton-seaice deleted the dev branch September 1, 2025 01:02
@github-actions
Copy link
Copy Markdown

github-actions bot commented Sep 1, 2025

🚀 Attempted to deploy access-om3 Prerelease pr138-30 with commit 2807b30

🖥️ Gadi Deployment ❌

@anton-seaice anton-seaice mentioned this pull request Sep 1, 2025
Closed
@chrisb13 chrisb13 mentioned this pull request Jan 7, 2026
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@minghangli-uni minghangli-uni minghangli-uni approved these changes

@dougiesquire dougiesquire dougiesquire approved these changes

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

@anton-seaice @dougiesquire @CodeGat @minghangli-uni