Skip to content

Optimized petsc build for production release of access-issm#37

Merged
justinh2002 merged 10 commits into
mainfrom
justinh2002/170426_production_release
May 27, 2026
Merged

Optimized petsc build for production release of access-issm#37
justinh2002 merged 10 commits into
mainfrom
justinh2002/170426_production_release

Conversation

@justinh2002

@justinh2002 justinh2002 commented Apr 17, 2026

Copy link
Copy Markdown
Collaborator

🚀 The latest prerelease access-issm/pr37-9 at a764310 is here: #37 (comment) 🚀

justinh2002 and others added 6 commits March 7, 2025 15:46
* added python3.9.2 in package dependency tree

* added python dependency and installation for issm with wrapper spec

* Get into model deployment repo format

* add specific mpi version

* Update spack-packages version to 2025.04.000

* spack.yaml: Added newline at end of file

* Update issm tag, remove TODO

* changed from intel compiler to gcc

* change tag name
Comment thread spack.yaml Outdated
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr37-1 with commit f391325

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.05.0 as a Release (when merged).
  • pr37-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr37-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-issm-pr37-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:

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

@justinh2002

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr37-2 with commit f391325

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.05.0 as a Release (when merged).
  • pr37-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr37-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/1.1/spack in the access-issm-pr37-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, or propose changes to build-cds config/settings.json.

@justinh2002

Copy link
Copy Markdown
Collaborator Author

Pine Island Glacier testing with 4546 triangles.
hmax = 30000 hmin = 50 gradation = 1.7 err = 8

Total solution time of friction inversion

  1. old 2025.11.24 ISSM build took 121 seconds
  2. -02 ISSM build took 82 seconds
  3. -02 -DNDEBUG took 61 seconds

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr37-3 with commit 880e70f

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr37-4 with commit 428df88

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.05.0 as a Release (when merged).
  • pr37-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-issm/pr37-4

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-issm-pr37-4 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, or propose changes to build-cds config/settings.json.

@justinh2002 justinh2002 marked this pull request as draft May 26, 2026 05:32
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr37-5 with commit a764310

🖥️ Gadi Deployment ❌

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr37-5 with commit a764310

🖥️ Gadi Deployment ❌

@justinh2002

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr37-7 with commit a764310

🖥️ Gadi Deployment ❌

@justinh2002

Copy link
Copy Markdown
Collaborator Author

!redeploy

@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr37-8 with commit a764310

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.05.0 as a Release (when merged).
  • pr37-8 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

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

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

@justinh2002 justinh2002 requested a review from CodeGat May 27, 2026 03:58
@justinh2002 justinh2002 marked this pull request as ready for review May 27, 2026 03:58
@justinh2002 justinh2002 temporarily deployed to Gadi Prerelease May 27, 2026 04:00 — with GitHub Actions Inactive
@github-actions

Copy link
Copy Markdown

🚀 Attempted to deploy access-issm Prerelease pr37-9 with commit a764310

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2026.05.0 as a Release (when merged).
  • pr37-9 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

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

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

@CodeGat CodeGat left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks good to me. I'm a fan of the projection, actually - don't have to update it in two places 😆

Note to @aidanheerdegen - we might have to consider infrastructure that supports having multiple manifests in an MDR in cases like this in the future, maybe one with ad.spack.yaml and no-ad.spack.yaml or something, so one doesn't have to bounce between variants in the same file for releases on the main branch

@justinh2002 justinh2002 merged commit 9837340 into main May 27, 2026
26 of 29 checks passed
@justinh2002 justinh2002 temporarily deployed to Gadi Prerelease May 27, 2026 04:40 — with GitHub Actions Inactive
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