QA: Test inputs are in approved locations

[aidanheerdegen]

Released configurations should only have paths in inputs (and restart) from two locations:

1. /g/data/vk83/configurations/inputs
2. Published data projects

This is because files in those locations are controlled and appropriately versioned. In the case of vk83 they are also backed up to tape.

We should have QA checks that enforce this.

Some example of published data locations:

• input4mips: /g/data/qv56/replicas
• ????

Note that it is permissible for prerelease dev configurations to have paths in /g/data/vk83/prerelease/configurations/inputs, but this is not permissible for released configurations, and so needs to be checked when transitioning from prerelease to release dev- to release- as it is an easy thing to overlook.

Edited based on correction from @ccarouge

[aidanheerdegen]

Damn. We should prioritise this. ACCESS-ESM1.6 configurations have been used to run experiments with inputs in the prerelease directory, which is not good.

[ccarouge]

For configurations, I think you mean dev- to release- instead of prerelease to release? Just trying to keep the vocabulary consistent.

[ccarouge]

@aidanheerdegen Can you add /g/data/jq44 in the list of published data locations? I'm jumping ahead here, but it will be used as the restart collection for ESM1.6 and later on for CM3 and ESM3.