Muon trigger: clean-up and simplification of the muFast step (ATR-26968)
It is an attempt to eliminate the using of the chainName for the TrigMufastHypoTool configuration, see TrigMuonHypoConfig.py
All parts of the configuration are now put in one place, namely to the TrigMufastHypoToolConfig class which performs initialization of the HypoTool using the chainPart dictionary. It seems we can remove muFastOvlpRmSequence and use the only muFastSequence
The affected chains are:
- HLT_mu11_mu6_bBmumux_Bidperf_L1MU8VF_2MU5VF (expected, now mu11 is configured as l2io leg, not as idperf)
- HLT_mu14_mu14_idperf_50invmAB130_L12MU8F (leg000 is now configured as pure mu14, not mu14_idperf, bugfix to confirmed)
- HLT_mu14_mu14_idtp_idZmumu_L12MU8F (leg000 is now configured as pure mu14, not mu14_idtp, bugfix to confirmed)
The changes from confTool.py
confTool.py --diff new.pkl ../test02/default.pkl
Step 1: reference file #components: 27453
Step 2: file to check #components: 27453
Legend:
Differences in components Settings in 1st file Settings in 2nd file
Component PerfMonMTSvc may differ
wallTimeOffset = 1677250000000.0 vs 1677160000000.0 <<
but all are suppressed by renaming/known differences/...
Component TrigL2MufastHypoAlg.leg000_HLT_mu11_mu6_bBmumux_Bidperf_L1MU8VF_2MU5VF may differ
PtThresholdForECWeakBRegionA = [3910.0] vs [6190.0] <<
PtThresholdForECWeakBRegionB = [2220.0] vs [4370.0] <<
PtThresholds = [[5170.0, 3250.0, 4690.0, 5140.0]] vs [[8990.0, 6620.0, 7400.0, 9320.0]] <<
but all are suppressed by renaming/known differences/...
Component TrigL2MufastHypoAlg.leg000_HLT_mu14_mu14_idperf_50invmAB130_L12MU8F may differ
PtThresholdForECWeakBRegionA = [3910.0] vs [6780.0] <<
PtThresholdForECWeakBRegionB = [2220.0] vs [5030.0] <<
PtThresholds = [[5170.0, 3250.0, 4690.0, 5140.0]] vs [[11150.0, 7580.0, 8430.0, 11610.0]] <<
but all are suppressed by renaming/known differences/...
Component TrigL2MufastHypoAlg.leg000_HLT_mu14_mu14_idtp_idZmumu_L12MU8F may differ
PtThresholdForECWeakBRegionA = [3910.0] vs [6780.0] <<
PtThresholdForECWeakBRegionB = [2220.0] vs [5030.0] <<
PtThresholds = [[5170.0, 3250.0, 4690.0, 5140.0]] vs [[11150.0, 7580.0, 8430.0, 11610.0]] <<
but all are suppressed by renaming/known differences/...If you like these changes we can go ahead. If you find them too violent we can close this MR
PS As a bonus there is no need to implement muFastOvlpRmSequence in CA. I've checked the counts for HLT 2mu4 for newJO are the same as for nonCA (default scheme).