VELO sensors out of range (sensor > 207)
As reported in !1338 (merged) and in this thread of LHCb!4227 (merged), VELO sensors with values greater than 207 are observed when running the VeloLumiCounters.cu algorithm. After some debugging running the command
MooreOnline/run Allen/Dumpers/BinaryDumpers/options/allen.py --monitoring-filename output.root -m 1000 -t 3 --events-per-slice 1000 --tags "detdesc:upgrade/dddb-20221004,upgrade/mu_VP_SciFi_macromicrosurvey_from20220923|dd4hep:trunk,master" --sequence Allen/build.x86_64_v2-el9-gcc12-opt/hlt1_PbPb_PbSMOG_no_ut.json --mep mdf:root://eoslhcb.cern.ch///eos/lhcb/wg/rta/samples/data/253895-LHCb-MEP/bu_253895_LHCb_ECEB02_BU_0.mep --output-file output.mdf --register-monitoring-counters 0we observed that all clusters out of DecodeRetinaClusters have sensor <= 207 and LHCbIDType = 0x2 (VELO) whereas, within VeloLumiCounters, some clusters have LHCbIDType != 0x2. Moreover each time sensor > 207 the LHCbIDType != 0x2. So it seems that VELO clusters are not read correctly within VeloLumiCounters.
To replicated this, add the following printout to L304 of DecodeRetinaClusters
if (raw_bank_sensor_index > 207){
std::cout << "decoder: ID = " << get_lhcb_id(cid) << " det type " << (get_lhcb_id(cid) >> 28) << " sensor " << raw_bank_sensor_index << std::endl;
}and the following printout to L157 of VeloLumiCounters
if (sensor_id > 207){
std::cout << "lumi: ID = " << velo_cluster_container.id(hit_index) << " det type " << (velo_cluster_container.id(hit_index) >> 28) << " sensor " << sensor_id <<std::endl;
}