Skip to content

Conversation

blimlim
Copy link
Collaborator

@blimlim blimlim commented Aug 29, 2025

Seeing if I can get monthly mean river output.
See ACCESS-NRI/access-esm1.6-configs#172 for background


🚀 The latest prerelease access-esm1p6/pr132-42 at 4cff6a0 is here: #132 (comment) 🚀

Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-1 with commit 3323b40

🖥️ Gadi Deployment ❌

Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-2 with commit 465d21d

🖥️ Gadi Deployment ❌

@blimlim
Copy link
Collaborator Author

blimlim commented Aug 29, 2025

!redeploy

Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-3 with commit 465d21d

🖥️ Gadi Deployment ❌

Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-4 with commit 7e65471

🖥️ Gadi Deployment ❌

@blimlim
Copy link
Collaborator Author

blimlim commented Aug 29, 2025

!redeploy

Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-5 with commit 7e65471

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.07.000 as a Release (when merged).
  • pr132-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr132-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-esm1p6-pr132-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.

@blimlim blimlim temporarily deployed to Gadi Prerelease August 29, 2025 07:17 — with GitHub Actions Inactive
Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-6 with commit 342e2d3

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.07.000 as a Release (when merged).
  • pr132-6 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr132-6

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-pr132-6 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.

Copy link

github-actions bot commented Sep 1, 2025

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-7 with commit eadbfd4

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.07.000 as a Release (when merged).
  • pr132-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr132-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-esm1p6-pr132-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.

Copy link

github-actions bot commented Sep 1, 2025

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-8 with commit 0b803c7

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.07.000 as a Release (when merged).
  • pr132-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr132-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-esm1p6-pr132-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.

@blimlim blimlim force-pushed the um-river-diagnostics branch from 0b803c7 to a4ce3be Compare September 1, 2025 05:56
Copy link

github-actions bot commented Sep 1, 2025

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-9 with commit a4ce3be

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.07.000 as a Release (when merged).
  • pr132-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr132-9

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-pr132-9 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.

Copy link

github-actions bot commented Sep 2, 2025

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-10 with commit 7bb1c88

🖥️ Gadi Deployment ❌

Copy link

github-actions bot commented Sep 2, 2025

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-11 with commit 028b8b2

🖥️ Gadi Deployment ❌

Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-33 with commit 7eeae09

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.07.000 as a Release (when merged).
  • pr132-33 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr132-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-esm1p6-pr132-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.

Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-34 with commit c06605b

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.07.000 as a Release (when merged).
  • pr132-34 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr132-34

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-pr132-34 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.

Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-35 with commit 38b3783

🖥️ Gadi Deployment ❌

Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-36 with commit c839d1c

🖥️ Gadi Deployment ❌

Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-37 with commit 7bbce24

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.07.000 as a Release (when merged).
  • pr132-37 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr132-37

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-pr132-37 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.

Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-38 with commit 10e1bec

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.07.000 as a Release (when merged).
  • pr132-38 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr132-38

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-pr132-38 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.

Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-39 with commit 50e44e2

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.07.000 as a Release (when merged).
  • pr132-39 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr132-39

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-pr132-39 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.

Copy link

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-40 with commit d2d5359

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.07.000 as a Release (when merged).
  • pr132-40 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr132-40

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-pr132-40 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.

@blimlim
Copy link
Collaborator Author

blimlim commented Oct 2, 2025

!redeploy

Copy link

github-actions bot commented Oct 2, 2025

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-41 with commit 3d8683b

🖥️ Gadi Deployment ❌

@blimlim blimlim force-pushed the um-river-diagnostics branch from 3d8683b to 4cff6a0 Compare October 2, 2025 06:28
@blimlim
Copy link
Collaborator Author

blimlim commented Oct 2, 2025

!redeploy

Copy link

github-actions bot commented Oct 2, 2025

🚀 Attempted to deploy access-esm1p6 Prerelease pr132-42 with commit 4cff6a0

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.07.000 as a Release (when merged).
  • pr132-42 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p6/pr132-42

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-pr132-42 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.

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