Follow-up from "[master] Follow Run 3 conditions database changes in checkRun3CondDB"
The following discussion from !1462 (merged) should be addressed:
-
@clemenci started a discussion: (+4 comments) The batching of runs in group of 1000s is a bit arbitrary, but a safe assumption for the moment.
Instead of
git ls-tree --name-only master Conditions/LHCb/Online/Tell40Links.yml/...
I would use the equivalent of (pseudo code):git rev-parse {tag}:Conditions/LHCb/Online/Tell40Links.yml/{runID // 1000}000/{runID} || git rev-parse {tag}:Conditions/LHCb/Online/Tell40Links.yml/{runID}
I would also use a different YAML path as the choice of Tell40Links seems arbitrary. For example
Conditions/LHCb/Online/LHC.yml
sounds better, but I'll have to check with @clara what is best or if to add a "run stamp" artificial condition for readability.As I mentioned in lhcb-conddb/lhcb-conditions-database#12 (comment 7278076) I can prepare a Python module that uses the same library used by LHCb applications, but this is a good temporary patch.