Can pre-release infra be used to build MOM6 standalone

[chrisb13]

Attempting to run mom6 standalone, Harshula said we can use pre-release infra'!

---

🚀 The latest prerelease access-om3/pr151-4 at 279fb07 is here: #151 (comment) 🚀

[chrisb13]

ping @harshula as we've been chatting about it.

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr151-1 with commit 64e0c98

🖥️ Gadi Deployment ❌

[chrisb13]

Closing this as @dougiesquire has re-confirmed that it's not possible.

[dougiesquire]

It is possible, but what you tried here is not how to do it.

As we talked about yesterday, you can use the prerelease infrastructure to build whatever you like (within the confines of a few CI checks/requirements). E.g. in this PR I built FRE-NCtools. However, this is not something we should do routinely or probably at all.

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr151-3 with commit 64e0c98

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-om3 Prerelease pr151-4 with commit 279fb07

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2025.07.000 as a Release (when merged).
• pr151-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-om3/pr151-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/0.22/spack in the access-om3-pr151-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:

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

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

[chrisb13]

From @CodeGat the CD wizard:

Haha, the hack works, it's the comment that is wrong. You'd use the module access-mom6/pr151-4 instead. Undocumented, but hey, it's a hack 😉

[cyb561@gadi-login-04 ~]$ module purge
[cyb561@gadi-login-04 ~]$ module use /g/data/vk83/prerelease/modules
[cyb561@gadi-login-04 ~]$ module load access-mom6/pr151-4
Loading access-mom6/pr151-4
  Loading requirement: access-mom6/dependencies/pr151-4/access-mocsy/2025.07.002-ucihukj access-mom6/dependencies/pr151-4/access-generic-tracers/2025.08.000-lbeknxx
[cyb561@gadi-login-04 ~]$ which access-mom6
/usr/bin/which: no access-mom6 in (/g/data/vk83/prerelease/apps/spack/0.22/release/linux-rocky8-x86_64_v4/oneapi-2025.2.0/access-mom6-2025.07.000-ruhunvj5oyc2nidysvbmajb42ehtszzm/bin:/home/561/cyb561/.local/bin:/home/561/cyb561/bin:/opt/pbs/default/bin:/opt/nci/bin:/opt/bin:/opt/Modules/v4.3.0/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin)

[aidanheerdegen]

Using the wrong exe name

$ ls /g/data/vk83/prerelease/apps/spack/0.22/release/linux-rocky8-x86_64_v4/oneapi-2025.2.0/access-mom6-2025.07.000-ruhunvj5oyc2nidysvbmajb42ehtszzm/bin
mom6

[chrisb13]

Thanks @aidanheerdegen, I was hoping to have a hacked config.yaml with something like:

modules:
    use:
        - /g/data/vk83/prerelease/modules
    load:
        - access-mom6/pr151-4

model: access-mom6
exe: mom6
input: 
.
.

Would you expect this to work?

I suppose another option is:

model: mom6
exe: $ /g/data/vk83/prerelease/apps/spack/0.22/release/linux-rocky8-x86_64_v4/oneapi-2025.2.0/access-mom6-2025.07.000-ruhunvj5oyc2nidysvbmajb42ehtszzm/bin
mom6/mom6

Which I think should work for sure but is less preferred (by the release team I think)?

[dougiesquire]

Both the model and exe should be mom6

[chrisb13]

Thanks @dougiesquire, like this?

modules:
    use:
        - /g/data/vk83/prerelease/modules
    load:
        - access-mom6/pr151-4

model: mom6
exe: mom6

[dougiesquire]

Yup. The model field is the name of the Payu model driver to use. The exe field is the path to the executable (or just the executable name if it is already on your PATH)

[dougiesquire]

@chrisb13 I think this can be closed?