Skip to content

moving tracktwoEF chain run as BDT chain and not RNN chain

Antonio De Maria requested to merge tracktwoef_nonrnn_chain into master

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

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 misleading combination from LS2_V1 menu:

  • HLT_tau25_looseRNN_tracktwoEF_L1TAU12IM
  • HLT_tau25_mediumRNN_tracktwoEF_L1TAU12IM
  • HLT_tau25_tightRNN_tracktwoEF_L1TAU12IM
  • HLT_tau35_looseRNN_tracktwoEF_L1TAU12IM
  • HLT_tau35_mediumRNN_tracktwoEF_L1TAU12IM
  • HLT_tau35_tightRNN_tracktwoEF_L1TAU12IM
  • HLT_tau160_mediumRNN_tracktwoEF_L1TAU100
  • HLT_tau200_mediumRNN_tracktwoEF_L1TAU100

Merge request reports