Add environment variables to modify the "Strictness" of the Tracker #86
Comments
|
One could do the same for git oriented fields. I.e., directly fail if the repository is not clean. And an upload is only accepted if the environment variable was present at the time of the experiments or if an experimenter describes why it was not present (e.g., "I had no time to get it to run on my system", "I did not have the system permissions", "I forgot to add the flag", "I only saw this after I did the experiments", etc.) I think this would be very cool, as it would be a good way to balance in the discussion that we had on how strict the tool should be (cc. @hscells). |
|
From the chat (Tim): |
|
Oh, and one could even add this environment variable to Docker images, so that it would work out of the box in dev-container-oriented setups. This would be really awesome. |
I would like that the tracker directly fails if some measurements can not be extracted, e.g., because the process has not the required permissions to access the corresponding system APIs.
Right now, the tracker does not fail if it can not record something, I would like to have a environment variable to control this behaviour.
E.g.,
that also is persisted into the metadata and would cause that the process directly terminates if it can not access something. Because this way, one could ensure that everything is properly recorded, and one could require that this flag is explicitly incorporated into ir-metadata to accept an run upload (or, to add a description why it was not possible to add this flag).
I think this would be very helpful and would not require to modify code.
The text was updated successfully, but these errors were encountered: