automating choice of best chain for tag and probe for HLT muon efficiency monitoring
This MR addresses the issue reported in ATR-27787 (and visible for example in ATR-28255) by choosing automatically the best chain to be used as event and tag trigger in Z and ttbar tag-and-probe, for the monitoring of the HLT muon efficiency.
The trigger to request is chosen among the monitored triggers based on a preference (like "a chain with 24 GeV at HLT, possibly with isolation, and a 14 GeV L1 muon item"). This should allow a seamless running with the pp and HI menus. An info printout is also added to the logs to make it easy to spot future possible issues (e.g. broken naming convention of HLT chains).
I tested this change locally in 23.0 by checking the correct HLT chains are selected when processing the same raw file (using --triggerConfig "all=DB:TRIGGERDBREPR_RUN3:220,89,205,2" for pp and DB:TRIGGERDBREPR_RUN3:241,104,229,2 for HI); the resulting chosen chains are
$ grep TrigMuonEfficiencyMonConfig.py *log
athena_onlymuons_HI.log:RAWtoALL 16:15:58 Py:TrigMuonEfficiencyMonConfig.py INFO Using HLT_mu10_L1MU8F as tag and event trigger in ttbar tag&probe
athena_onlymuons_HI.log:RAWtoALL 16:16:11 Py:TrigMuonEfficiencyMonConfig.py INFO Using HLT_mu10_L1MU8F as tag and event trigger in Z tag&probe
athena_onlymuons_pp.log:RAWtoALL 16:17:47 Py:TrigMuonEfficiencyMonConfig.py INFO Using HLT_mu24_ivarmedium_L1MU14FCH as tag and event trigger in ttbar tag&probe
athena_onlymuons_pp.log:RAWtoALL 16:18:01 Py:TrigMuonEfficiencyMonConfig.py INFO Using HLT_mu24_ivarmedium_L1MU14FCH as tag and event trigger in Z tag&probeSince it addresses the fact HLT muon efficiency histograms would be missing when running on HI data, this MR targets 23.0.
P.s.: a small change in the description of the efficiency histograms in the webdisplay is also included, to avoid misleading the shifter (before, HLT_mu50 was mistakenly prepended to the chain name in the description of three histos)