Skip to content

Update um_ref to AM3-dev in spack.yaml - #74

Draft
Whyborn wants to merge 2 commits into
developmentfrom
reorder-cable-iterations-for-memory-efficiency
Draft

Whyborn wants to merge 2 commits into
developmentfrom
reorder-cable-iterations-for-memory-efficiency

Conversation

@Whyborn

@Whyborn Whyborn commented Oct 25, 2026 •

Copy link
Copy Markdown
Collaborator

Uses the reorder-cable-iteration-order branch of UM.


🚀 The latest prerelease access-am3/pr74-1 at 9d1478a is here: #74 (comment) 🚀

@Whyborn
Whyborn changed the base branch from main to development October 25, 2026 22:49
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-am3 Prerelease pr74-1 with commit 9d1478a

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.08.002 as a Release (when merged).
  • pr74-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr74-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/1.1/spack in the access-am3-pr74-1 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:

  • access-nri/spack on branch 1.1
  • ACCESS-NRI/upstream-spack-packages version access/v1.1
  • access-nri/access-spack-packages version 2026.09.001
  • access-nri/spack-config version 2026.10.003

If the above was not what was expected, commit changes to the manifest in this PR, or propose changes to build-cds config/settings.json.

This branch has not been deployed

No deployments
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