Don't contact myMdC to get run creation time
Description
The code to get the creation time of a run preferred getting it from myMdC if possible, with a fallback to looking at the files. Talking to an external service is a problem for reproducibility - when you re-run it, the response from the external service might be different, the API you're using might have changed, or you might be running it without the credentials (configured per user) to access myMdC. The fallback mitigates this, but might give a different answer from myMdC.
It's also easier for people to try running the calibration code if there's no need to configure an Oauth token for myMdC.
Files from 2020 onwards appear to have the INDEX/timestamp dataset; Luis has told me that the start time in myMdC is taken from the timestamp of the first train, so this should reliably give us the same answer. For older files, it falls back to finding the earliest modification time of the .h5 files in the directory.
How Has This Been Tested?
The functions this uses were already used as fallbacks, and are covered by tests.
Types of changes
- New feature (non-breaking change which adds functionality)
Checklist:
- My code follows the code style of this project.