Creating a cice5 with >= 20 cores

[manodeep]

Trying a new CICE5 exe with larger number of cores now that I can tune the exact placement with a rankfile.

---

🚀 The latest prerelease access-esm1p6/pr188-8 at b893303 is here: #188 (comment) 🚀

[github-actions]

The model version in the ./spack.yaml has not been updated.
You can update it manually.

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr188-1 with commit 73cbd4c

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr188-1 with commit 73cbd4c

🖥️ Gadi Deployment ❌

[manodeep]

!redeploy

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr188-2 with commit 73cbd4c

🖥️ Gadi Deployment ❌

[manodeep]

!redeploy

[manodeep]

(UM7 compile "terminated by kill signal)

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr188-4 with commit 285aa26

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr188-3 with commit 73cbd4c

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr188-5 with commit 408792a

🖥️ Gadi Deployment ❌

[anton-seaice]

It's also possible to make many builds (in pre-release only), the spack.yaml would be something like:

spack:
  specs:
    - access-esm1p6 cice=5 ^cice5 blckx=18 blcky=300 mxblcks=1
    - access-esm1p6 cice=5 ^cice5 blckx=30 blcky=150 mxblcks=2
  packages:
    # Coupler
    oasis3-mct:
      require:
        - '@5.2'
    # Major components
    cice5:
      require:
        - '@2026.01.000'
        - 'nxglob=360 nyglob=300'
...
  view: false
  concretizer:
    unify: false
  modules:
    default:
      tcl:
        projections:
          access-esm1p6: '{name}/{^cice5.variants.blckx.value}x{^cice5.variants.blcky.value}x{^cice5.variants.mxblcks.value}'
...

[manodeep]

@anton-seaice I was just about to ping you on Zulip with the question about multi-exes - many thanks 😄

[anton-seaice]

@CodeGat

We asked for this module name

access-esm1p6: '{name}/{^cice5.variants.blckx.value}x{^cice5.variants.blcky.value}'

but got

access-esm1p6: '{name}/pr188-6'

Thoughts?

From https://github.com/ACCESS-NRI/ACCESS-ESM1.6/actions/runs/21848909589/job/63051018462?pr=188#:~:text=The,hash%3A7%7D%27

The root spec 'access-esm1p6' does not have a git ref, so no changes are made.
Updating projection 'access-fms' from '{name}/mom5-2025.08.000-{hash:7}' to 'access-esm1p6/dependencies/pr188-6/{name}/mom5-2025.08.000-{hash:7}'
...

  modules:
    default:
      tcl:
        projections:
          access-esm1p6: '{name}/pr188-6'
          access-fms: 'access-esm1p6/dependencies/pr188-6/{name}/mom5-2025.08.000-{hash:7}'
          access-generic-tracers: 'access-esm1p6/dependencies/pr188-6/{name}/2025.09.000-{hash:7}'

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr188-6 with commit 464d858

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr188-7 with commit a2b836f

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• main as a Release (when merged).
• pr188-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/pr188-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-pr188-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:

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

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

[github-actions]

🚀 Attempted to deploy access-esm1p6 Prerelease pr188-8 with commit b893303

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• main as a Release (when merged).
• pr188-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/pr188-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-pr188-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 0.22
• access-nri/spack-packages version 2026.02.000
• access-nri/spack-config version 2026.02.000

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

[manodeep]

None of my attempts at custom-placing the ranks resulted in any any meaningful performance improvement :(