Attach central LHCb `Tell40Links` condition to appropriate dd4hep detector object
During 2022 Online started sending run by run a condition object that documents the links active in each run see
These conditions can in principle be used by the sub-system decoding to know what links to expect in each run, removing the need to 'hardcode' this in their own readout maps.
However, to access this it needs to be made available in dd4hep. I see two things
- Needs to be attached to some detector element, such that it can then be loaded as a condition by downstream detector code.
- As a nicety, it would be good to provide a central 'derived condition' object that provides a more sub-system oriented view of this data, to make it a bit more convenient for sub-system downstream to use. We don't really need or want each to have to reinvent their own parsing logic.
For 1. I guess the most obvious is to attach it some central entity, like LHCb or /world. I am not sure how to do this (I've only done this for spcific sub-systems before). @clemenci @bcouturi Can you please provide this part of the puzzle ?
@sgambett This is what we discussed this morning in the RICH ops meeting.