Use GitHub UKMO components

[Whyborn]

Now that the Met office has switched to Github, we can use Github repositories for the various components we used to pull from the MOSRS mirror. Uses GCOM, Socrates, UKCA, casim and shumlib from Github.

Confirmed that the release AM3 configuration gets bitwise identical results, for the first few months of NetCDF data.

---

🚀 The latest prerelease access-am3/pr25-3 at fc2db58 is here: #25 (comment) 🚀

---

🚀 The latest prerelease access-am3/pr25-7 at 6ea22a1 is here: #25 (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-am3 Prerelease pr25-1 with commit 0967772

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr25-1 with commit dd83468

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.03.000 as a Release (when merged).
• pr25-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/pr25-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-pr25-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 381aaf345f95e9ed712fc7a4f50d54f5e977c628
• 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 pr25-2 with commit 404688a

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr25-3 with commit fc2db58

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.02.001 as a Release (when merged).
• pr25-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/pr25-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-pr25-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 c0f985e01da7d9394020e3a8def8edd8aa270077
• 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.

[MartinDix]

Should this use the um13.1 tags for CASIM, shumlib and SOCRATES?

Should we put a tag on the UKCA branch?

[Whyborn]

@MartinDix hmm perhaps they should, and the fact that I naively used the head of these repos and it gives bitwise repro is suspicious. I will dig a bit to make sure it's not still getting them from MOSRS.

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr25-4 with commit 2afe7ef

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr25-5 with commit 2dc7c43

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr25-6 with commit 2f8ecc1

🖥️ Gadi Deployment ❌

[github-actions]

🚀 Attempted to deploy access-am3 Prerelease pr25-7 with commit 6ea22a1

🖥️ Gadi Deployment ✔️

Usage Instructions

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

• 2026.02.001 as a Release (when merged).
• pr25-7 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

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

[Whyborn]

@MartinDix I've updated the deployment to use um13.1 tags for all components except UKCA, which uses your branch. Results are still bitwise equivalent- I'm not sure if that means in the prior versions of spack-packages it was still pulling from the MOSRS mirror with the _rev_variants, or there just hadn't been any changes between um13.1 and the head commits.