Move tracktwoEF to be BDT TauID trigger
According to https://twiki.cern.ch/twiki/bin/view/Atlas/LowestUnprescaled#Taus, the tracktwoEF chain should be paired with BDT and not RNN TauID such as:
- HLT_tau200_medium1_tracktwoEF_L1TAU100
- HLT_tau35_medium1_tracktwoEF_tau25_medium1_tracktwoEF_L1DR-TAU20ITAU12I-J25
This MR is changing the tracktwoEF chain behaviour:
- moving from RNN to BDT (
TrigTauRecMerged_TauPrecisionMVA
->TrigTauRecMerged_TauPrecision
) - output will be written on
HLT_TrigTauRecMerged_Precision
container and not in "HLT_TrigTauRecMerged_PrecisionMVA
(change on Run3 EDM)
Removing also misleading combination from LS2_V1 menu since RNN should run only on tracktwoMVA/tracktwoMVABDT chains:
- HLT_tau160_mediumRNN_track_L1TAU100
- HLT_tau160_mediumRNN_tracktwoEF_L1TAU100
- HLT_tau160_mediumRNN_tracktwo_L1TAU100
- HLT_tau200_mediumRNN_track_L1TAU100
- HLT_tau200_mediumRNN_tracktwoEF_L1TAU100
- HLT_tau200_mediumRNN_tracktwo_L1TAU100
- HLT_tau25_looseRNN_track_L1TAU12IM
- HLT_tau25_looseRNN_tracktwoEF_L1TAU12IM
- HLT_tau25_looseRNN_tracktwo_L1TAU12IM
- HLT_tau25_mediumRNN_track_L1TAU12IM
- HLT_tau25_mediumRNN_tracktwoEF_L1TAU12IM
- HLT_tau25_mediumRNN_tracktwo_L1TAU12IM
- HLT_tau25_tightRNN_track_L1TAU12IM
- HLT_tau25_tightRNN_tracktwoEF_L1TAU12IM
- HLT_tau25_tightRNN_tracktwo_L1TAU12IM
- HLT_tau35_looseRNN_track_L1TAU12IM
- HLT_tau35_looseRNN_tracktwoEF_L1TAU12IM
- HLT_tau35_looseRNN_tracktwo_L1TAU12IM
- HLT_tau35_mediumRNN_track_L1TAU12IM
- HLT_tau35_mediumRNN_tracktwoEF_L1TAU12IM
- HLT_tau35_mediumRNN_tracktwo_L1TAU12IM
- HLT_tau35_tightRNN_track_L1TAU12IM
- HLT_tau35_tightRNN_tracktwoEF_L1TAU12IM
- HLT_tau35_tightRNN_tracktwo_L1TAU12IM
tagging @carquin, @malconad and @martindl, please have a look and let me know if I missed something ...
Edited by Antonio De Maria