Change the cable_surface_types_mod for CABLE library

[Whyborn]

The current setup of cable_surface_types_mod is not compatible with a library. This brings in the changes from this JULES PR, which no longer sets the CABLE surface type indices from namelist, as this is not yet supported by CABLE.

---

🚀 The latest prerelease access-am3/pr40-14 at c7be9c8 is here: #40 (comment) 🚀

[github-actions]

The model version in the spack.yaml has not been updated.
You can update it manually.
Alternatively, comment the following to have it updated and committed automatically:

• !bump major for feature releases
• !bump minor for bugfixes

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr40-1 with commit c8eb698

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr40-1 with commit d5da62d

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr40-2 with commit 941fca9

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr40-3 with commit 26e639e

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr40-4 with commit 69ff876

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr40-5 with commit 1d0517c

🖥️ Gadi Deployment ❌

[Whyborn]

!redeploy

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr40-6 with commit 1d0517c

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr40-7 with commit 42bd9b7

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr40-8 with commit 487eb71

🖥️ Gadi Deployment ❌

[github-actions]

The model version in the spack.yaml has not been updated.
You can update it manually.
Alternatively, comment the following to have it updated and committed automatically:

• !bump major for feature releases
• !bump minor for bugfixes

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr40-9 with commit 34afb54

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr40-9 with commit 92206ca

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr40-10 with commit 8680260

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr40-11 with commit 5a3f836

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr40-12 with commit 96f1235

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.06.001 as a Release (when merged).
• pr40-12 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr40-12

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-am3-pr40-12 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.005
• 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.

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr40-13 with commit f43446e

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.06.002 as a Release (when merged).
• pr40-13 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr40-13

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-am3-pr40-13 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.005
• 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.

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr40-14 with commit c7be9c8

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.06.002 as a Release (when merged).
• pr40-14 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr40-14

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-am3-pr40-14 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.005
• 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.