Investigate namelist differences

[Whyborn]

Jhan is currently trying to implement reading of a namelist for major configuration options. Found some very strange behaviour- seems that cable_user%l_revise_coupling is not what it's expected to be on a single step on a single processor? See JULES thread. Doing some digging to see if I can work out what's going on, and some tracking of what we've tested.

---

🚀 The latest prerelease access-am3/pr28-3 at fbb486c is here: #28 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr28-1 with commit 87c94f1

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.03.000 as a Release (when merged).
• pr28-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.09.004
• 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-am3 Prerelease pr28-2 with commit 6eeb42e

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.03.000 as a Release (when merged).
• pr28-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2025.09.004
• 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-am3 Prerelease pr28-3 with commit fbb486c

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.03.000 as a Release (when merged).
• pr28-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr28-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-am3-pr28-3 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.09.004
• 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.