Update UM versions for runtime orbital parameters

[blimlim]

Closes #13.

This pr updates the UM to v 2024.10.17 which allows for orbital parameters to be read from a namelist at runtime.

Also includes updates to the versions.json file suggested by @CodeGat.

[github-actions]

🚀 Deploying access-esm1.5 2024.05.2 as prerelease pr14-1

Details and usage instructions

This access-esm1.5 model will be deployed as:

• 2024.05.2 as a Release (when merged).
• pr14-1 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p5/pr14-1

where the binaries shall be on your $PATH.
This Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p5- environment.

🛠️ Using: spack 0.22, spack-packages 2024.07.10, spack-config 2024.10.03

Details

It will be deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2024.07.10
• access-nri/spack-config version 2024.10.03

If this is not what was expected, commit changes to config/versions.json.

[github-actions]

🚀 Deploying access-esm1.5 2024.05.2 as prerelease pr14-2

Details and usage instructions

This access-esm1.5 model will be deployed as:

• 2024.05.2 as a Release (when merged).
• pr14-2 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p5/pr14-2

where the binaries shall be on your $PATH.
This Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p5- environment.

🛠️ Using: spack 0.22, spack-packages 2024.07.10, spack-config 2024.10.03

Details

It will be deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2024.07.10
• access-nri/spack-config version 2024.10.03

If this is not what was expected, commit changes to config/versions.json.

[github-actions]

🚀 Deploying access-esm1.5 2024.05.2 as prerelease pr14-3

Details and usage instructions

This access-esm1.5 model will be deployed as:

• 2024.05.2 as a Release (when merged).
• pr14-3 as a Prerelease (during this PR).

This Prerelease is accessible on Gadi using:

module use /g/data/vk83/prerelease/modules
module load access-esm1p5/pr14-3

where the binaries shall be on your $PATH.
This Prerelease is also accessible on Gadi via /g/data/vk83/prerelease/apps/spack/0.22/spack in the access-esm1p5- environment.

🛠️ Using: spack 0.22, spack-packages 2024.07.10, spack-config 2024.10.03

Details

It will be deployed using:

• access-nri/spack on branch 0.22
• access-nri/spack-packages version 2024.07.10
• access-nri/spack-config version 2024.10.03

If this is not what was expected, commit changes to config/versions.json.

[access-hive-bot]

This pull request has been mentioned on ACCESS Hive Community Forum. There might be relevant details there:

https://forum.access-hive.org.au/t/building-from-um7-repo/3815/29

[CodeGat]

Hey @blimlim, due to:

• The update to Prerelease versioning (in which we now use number of deployments rather than number of commits, which allows rebasing), and
• The update to Projections in the spack.yaml

Some of the spack environment names may clash for future deployments in this PR. If possible, can we move this to a new PR, and close this one? Happy to help out if needed.

There are conflicts currently on this branch due to the above, so you'll need to rebase onto main before opening the next PR - let me know if you need a hand!

[CodeGat]

NOTE: I know this one is going to be longer lived, so you don't nessecarily need to follow this, @blimlim ...

Hey, due to ACCESS-NRI/build-cd#173 we have had to update the infrastructure in this repository, as well - see #20.

We try and keep these kinds of updates to a minimum, and, starting from this one onwards, it will no longer be a hard requirement to update PR branches to incorporate infrastructure changes in order for the infrastructure to work - as you need to for this one.

To update this PR to the new origin/main, do the following:

git pull
git rebase origin/main
git push --force

to incorporate CI changes into the PR.

Your PR may redeploy, but that is okay - it should be identical to the last deployment. Let me know if you have any questions or issues.

[blimlim]

Will make a new PR incorporating the infrastructure updates!