It would be good to have finer-grained control of what must be reproduced. The current --reproduce flag insists input and restart are reproduced, and optionally exe reproduce can be turned off, for the use case where the executable has changed for a good reason, or just due to time and code updates.
There could be sub-options to manifest to enforce reproduction (checksums matching) for each manifest separately.
The use case is for the COSIMA access-om2 model configs, where a configuration is updated and published, and then users clone and use that configuration. It would be advantageous to specify something like:
manifest:
exe: True
input: True
to make sure the executable and input files are checked and match those from the config. In this case it is not necessarily desirable to enforce restart reproduction.
It would be good to have finer-grained control of what must be reproduced. The current
--reproduceflag insistsinputandrestartare reproduced, and optionallyexereproduce can be turned off, for the use case where the executable has changed for a good reason, or just due to time and code updates.There could be sub-options to
manifestto enforce reproduction (checksums matching) for each manifest separately.The use case is for the COSIMA
access-om2model configs, where a configuration is updated and published, and then users clone and use that configuration. It would be advantageous to specify something like:to make sure the executable and input files are checked and match those from the config. In this case it is not necessarily desirable to enforce restart reproduction.