Skip to content

Update CMEPS & Share only#196

Closed
anton-seaice wants to merge 9 commits intomainfrom
upstream-access3
Closed

Update CMEPS & Share only#196
anton-seaice wants to merge 9 commits intomainfrom
upstream-access3

Conversation

@anton-seaice
Copy link
Collaborator

@anton-seaice anton-seaice commented Feb 23, 2026


🚀 The latest prerelease access-om3/pr196-9 at ac9718a is here: #196 (comment) 🚀

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr196-1 with commit e99efb9

🖥️ Gadi Deployment ❌

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr196-2 with commit 8cbe351

🖥️ Gadi Deployment ✔️

Usage Instructions

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

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

@anton-seaice
Copy link
Collaborator Author

!update-configs

@github-actions
Copy link

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-om3-configs

Configurations Requested

Configurations requested from profile default:

  • dev-MC_100km_jra_ryf

  • dev-MC_100km_jra_ryf+wombatlite

  • dev-MC_25km_jra_ryf

Pull Requests Opened/Updated

The following PRs were opened/updated:

More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/22332268818

@anton-seaice
Copy link
Collaborator Author

Above repro tests show that this is not historically reproducable. (using https://github.com/ACCESS-NRI/access3-share/tree/9b418e8ff5dc5637f7da1cfc2ddc029f0f793cab with cesm_share 1.1.18 and cmeps 1.1.31

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr196-3 with commit d5a9be4

🖥️ Gadi Deployment ✔️

Usage Instructions

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

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

@anton-seaice
Copy link
Collaborator Author

!update-configs

@github-actions
Copy link

🔧 Opening/Updating Model Configuration PRs in ACCESS-NRI/access-om3-configs

Configurations Requested

Configurations requested from profile default:

  • dev-MC_100km_jra_ryf

  • dev-MC_100km_jra_ryf+wombatlite

  • dev-MC_25km_jra_ryf

Pull Requests Opened/Updated

The following PRs were opened/updated:

More details can be found in the workflow run: https://github.com/ACCESS-NRI/ACCESS-OM3/actions/runs/22334397837

@anton-seaice
Copy link
Collaborator Author

Above change has historical repro with cesm_share 1.1.18 only, so CMEPS seems to also be answer changing

@anton-seaice
Copy link
Collaborator Author

Running 196-2 shows large differences in the aoflux calculations, e.g.

image

@anton-seaice
Copy link
Collaborator Author

See ESCOMP/CMEPS#635

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr196-4 with commit 7706b38

🖥️ Gadi Deployment ❌

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr196-5 with commit c50bead

🖥️ Gadi Deployment ✔️

Usage Instructions

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

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

@anton-seaice
Copy link
Collaborator Author

anton-seaice commented Feb 25, 2026

Moving to CMEPS 1.0.35 resolved the problem (as it reverted a change so that aofluxes_use_shr_wv_sat defaults to .false. to maintain old behaviour in aoflux calculations)

https://github.com/ESCOMP/CMEPS/compare/cmeps1.1.31..cmeps1.1.35#diff-e705de7b456f1be0e1e2f8e675795a5d26b123c14ef2ef473eea4b0d378a454d

tests:

ACCESS-NRI/access-om3-configs#1151 (comment)

ACCESS-NRI/access-om3-configs#1149 (comment)

ACCESS-NRI/access-om3-configs#1150 (comment)

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr196-6 with commit 655858a

🖥️ Gadi Deployment ❌

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr196-7 with commit d8b9d32

🖥️ Gadi Deployment ✔️

Usage Instructions

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

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

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr196-8 with commit e52d3db

🖥️ Gadi Deployment ✔️

Usage Instructions

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

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

@github-actions
Copy link

🚀 Attempted to deploy access-om3 Prerelease pr196-9 with commit ac9718a

🖥️ Gadi Deployment ❌

@anton-seaice
Copy link
Collaborator Author

see #201

@anton-seaice anton-seaice deleted the upstream-access3 branch February 25, 2026 05:51
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.

1 participant