Skip to content

Conversation

@blimlim
Copy link
Collaborator

@blimlim blimlim commented Apr 22, 2025

The spinup run described here used UM executables built from a branch, making it difficult to know which commit of the code was used. Use this PR to try to figure this out.

Based on this commit


🚀 The latest prerelease access-esm1p6/pr81-1 at aeadfef is here: #81 (comment) 🚀

@blimlim
Copy link
Collaborator Author

blimlim commented Apr 22, 2025

!redeploy

@github-actions
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr81-1 with commit aeadfef

🖥️ Gadi Deployment ✔️

Usage Instructions

This access-esm1.6 model will be deployed to Gadi as:

  • dev_2024.12.0 as a Release (when merged).
  • pr81-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr81-1

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-esm1p6-pr81-1 environment.

Configuration Information

This Prerelease is deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2024.12.0
  • access-nri/spack-config version 2025.02.2

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

@blimlim
Copy link
Collaborator Author

blimlim commented Apr 22, 2025

Closing this PR. Tests with the executable confirm that PRs 27-5, 31-1, and 31-3 used in the spinup used the UM from 457d1da

@blimlim blimlim closed this Apr 23, 2025
@blimlim blimlim deleted the find-um-exe branch August 26, 2025 07:04
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