Add soil parameters through namelist

[Whyborn]

Second attempt at the changes @JhanSrbinovsky was trying in #43. The build was failing in unexpected ways- couldn't find external tools that should have already been built.

---

🚀 The latest prerelease access-am3/pr47-5 at 1df2c9a is here: #47 (comment) 🚀

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr47-1 with commit 7d8b607

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr47-2 with commit abbb430

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.06.000 as a Release (when merged).
• pr47-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/pr47-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/1.1/spack in the access-am3-pr47-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 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.

[Whyborn]

@JhanSrbinovsky associated deployment for the PFT params change. We can merge this in, and then update the configs PR to point to the new deployment (which will be 2026.06.001).

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr47-3 with commit 8e32ea9

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr47-4 with commit 2526909

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.06.001 as a Release (when merged).
• pr47-4 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr47-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/1.1/spack in the access-am3-pr47-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 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.

[JhanSrbinovsky]

no doubt effectively the same but do you guys have a requirement that a tagged ACCESS deployment should only require tagged child branches. i.e. JIULES required

[Whyborn]

Yep, I'll tag this JULES version

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr47-5 with commit 1df2c9a

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.06.001 as a Release (when merged).
• pr47-5 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-am3/pr47-5

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-pr47-5 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.