Add payu setup check?

[aidanheerdegen]

We could add payu setup check to the QA workflow.

This would be relatively quick to run and would be a sanity check for correct paths on deployment targets (gadi).

[jo-basevi]

Once payu setup is run, it can be used to check the manifests are unchanged (e.g. manifests/input.yaml, manifests/restart.yaml and manifests/exe.yaml).

The QA checks currently just run on Github Runners, while this sort of these would require a logging in to the deployment target. Should there be two different types of QA checks for local and remote? It could almost go under the reproducibility tests that log onto Github runners?

[anton-seaice]

to check the manifests are unchanged

I would find this useful.

I agree, it makes sense to write into the repro test rather than the QA check.

[aidanheerdegen]

The QA checks currently just run on Github Runners, while this sort of these would require a logging in to the deployment target.

Now that we have the model-config-inputs repo which should have an up-to-date manifest of all the model inputs, we should be able to this check on a GitHub runner.

Should there be two different types of QA checks for local and remote? It could almost go under the reproducibility tests that log onto Github runners?

See above, but that also doesn't mean we could do a payu setup sanity check as part of the repro checks to make sure they're consistent. There may well be other QA checks we can't do on a runner.

[aidanheerdegen]

Example where I did the exe check by hand, but it would be good to automate this, which is fairly straightforward with the model release DB:

ACCESS-NRI/access-esm1.6-configs#429 (review)