Set UT post-MD noise, pedestal and readout sector conditions to emtpy
Alternative to !153 (closed)
Instead of completely removing the UT conditions that are relevant only for simulation, this MR sets them to empty, starting from run 304425 (Friday of august MD). This seems to solve the observed crashes that were seen with lhcb/Detector!578 (merged) and !153 (closed) and also enables backwards-compatibility of the conditions to releases prior to RTA/2024.08.22
The reason for not starting earlier is that for releases before RTA/2024.08.22, running with this MR produces some warnings of the type Unable to find UT noise conditio... ERROR UTCsideUTaXStave0Face0Module0Sector0 Unable to find UT noise conditio... ERROR UTCsideUTaXStave0Face0Module1Sector0 Unable to find UT noise conditio... ERROR UTCsideUTaXStave0Face0Module2Sector0 Unable to find UT noise conditio... ERROR UTCsideUTaXStave0Face0Module2Sector1 Unable to find UT noise conditio... ERROR UTCsideUTaXStave0Face0Module3Sector0 Unable to find UT noise conditio... ERROR UTCsideUTaXStave0Face0Module3Sector1 Unable to find UT noise conditio... ERROR UTCsideUTaXStave0Face0Module4Sector0 Unable to find UT noise conditio... ERROR UTCsideUTaXStave0Face0Module4Sector1 Unable to find UT noise conditio... ERROR UTCsideUTaXStave0Face0Module5Sector0 Unable to find UT noise conditio... ERROR UTCsideUTaXStave0Face0Module6Sector0 Unable to find UT noise conditio... ERROR UTCsideUTaXStave0Face0Module7Sector0 , which seem harmless, but annoying.
With RTA/2024.08.22 the warnings are not there (thanks to lhcb/Detector!578 (merged) probably). HLT1 runs fine, and the conditions loading time is reduced to a negligible value.
A better solution for the future would be to have a defined list of conditions to be loaded at START or CHANGE run.