Skip to content

Release 2025.05.001#106

Merged
dougiesquire merged 2 commits intomainfrom
release-2025.05.001
Jun 4, 2025
Merged

Release 2025.05.001#106
dougiesquire merged 2 commits intomainfrom
release-2025.05.001

Conversation

@dougiesquire
Copy link
Copy Markdown
Collaborator

@dougiesquire dougiesquire commented May 29, 2025

This PR includes changes for the ACCESS-OM3 2025.05.001 release:

  • spack-packages 2025.05.002
  • access3/access3-share 2025.03.1
    • Set earth radius consistent with UM
  • access-cice CICE6.6.0-3
    • Add ability to write grid history file
  • access-mom6 2025.02.001
    • Add gtracers library to CMake build
  • Add access-generic-tracers git.dev-2025.05.001 and access-mocsy git.2017.12.0
  • Use spack versions where sensible; explicity set spack version where gitref is necessary
  • Set compiler optimization flags for improved performance

🚀 The latest prerelease access-om3/pr106-3 at ed23475 is here: #106 (comment) 🚀

@dougiesquire
Copy link
Copy Markdown
Collaborator Author

@minghangli-uni can you please push the optimization flags to this branch?

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr106-1 with commit 592c6b2

🖥️ Gadi Deployment ✔️

Usage Instructions

This access-om3 model will be deployed to Gadi as:

  • 2025.05.001 as a Release (when merged).
  • pr106-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr106-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-om3-pr106-1 environment.

Configuration Information

This Prerelease is deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2025.05.002
  • 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.

@github-actions
Copy link
Copy Markdown

🚀 Attempted to deploy access-om3 Prerelease pr106-2 with commit 3fb7e58

🖥️ Gadi Deployment ✔️

Usage Instructions

This access-om3 model will be deployed to Gadi as:

  • 2025.05.001 as a Release (when merged).
  • pr106-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/pr106-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-pr106-2 environment.

Configuration Information

This Prerelease is deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2025.05.002
  • 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.

dougiesquire and others added 2 commits June 3, 2025 16:21
- spack-packages 2025.06.000
- access3/access3-share 2025.03.1
  - Set earth radius consistent with UM
- access-cice CICE6.6.0-3
  - Add ability to write grid history file
- access-mom6 2025.02.001
  - Add gtracers library to CMake build
- Add access-generic-tracers git.dev-2025.05.001 and access-mocsy git.2017.12.0
- Use spack versions where sensible; explicity set spack version where gitref is necessary
@dougiesquire
Copy link
Copy Markdown
Collaborator Author

dougiesquire commented Jun 3, 2025

@minghangli-uni I also added the optimisation flags to access3-share, access-generic-tracers and access-mocsy and (crudely) checked that performance was not negatively impacted. @minghangli-uni could you check you're happy with what I've done.

@anton-seaice would you be able to review?

@github-actions
Copy link
Copy Markdown

github-actions bot commented Jun 3, 2025

🚀 Attempted to deploy access-om3 Prerelease pr106-3 with commit ed23475

🖥️ Gadi Deployment ✔️

Usage Instructions

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

  • 2025.05.001 as a Release (when merged).
  • pr106-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/pr106-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-pr106-3 environment.

Configuration Information

This Prerelease is deployed using:

  • access-nri/spack on branch 0.22
  • access-nri/spack-packages version 2025.06.000
  • 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.

Copy link
Copy Markdown
Collaborator

@minghangli-uni minghangli-uni left a comment

Choose a reason for hiding this comment

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

Thanks @dougiesquire The flags look good to me.

I tested them on both the cascadelake (normal) and sapphirerapids (normalsr) queues and they work on both architectures. However on the CL queue, performance is ~5% lower because the flags are tuned for SR maximal throughput. Since in production, all configurations will ultimately run on SR for its lower communication overhead.

Some notes:

  1. fms: I didn’t add flags here because I found that it actually degrades runtime performance. This is still a WIP, and I may revisit the compiler flags for fms later in the beta release.

  2. ACCESS-WW3: I haven’t tested this yet, so no flags are being added at the moment.

  3. Other dependencies: boost wasn’t detected, so no flags were added for those components.

Copy link
Copy Markdown
Collaborator

@anton-seaice anton-seaice left a comment

Choose a reason for hiding this comment

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

@dougiesquire dougiesquire merged commit 220e1ef into main Jun 4, 2025
10 checks passed
@dougiesquire dougiesquire deleted the release-2025.05.001 branch June 4, 2025 00:05
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