Extend tau trigger single leg trigger matching list in DAOD PHYS (ATR-24269)

Issue : looking at two recent DAOD PHYS data/MC samples produced with 22.0.50:

• mc20_13TeV.361108.PowhegPythia8EvtGen_AZNLOCTEQ6L1_Ztautau.deriv.DAOD_PHYS.e3601_s3681_r13144_r13146_p4926
• data18_13TeV.00349481.physics_Main.deriv.DAOD_PHYS.r13286_p4910_p4926

The trigger matching information for single leg tau triggers are missing. The trigger matching info be used for trigger efficiency/scale factor measurement using R22 Run2 reprocessing.

The issue should be caused by different name convention between Run2 and Run3 triggers: Run2 triggers (our target) don't have L1 item in the trigger name, while the single leg tau trigger list used for matching is filled using Run3 trigger name convention (not useful in this context).

This MR is recovering the missing trigger matching information by extending the current single leg tau trigger list used for matching.

Tested using:

• test_data18PHYS_serial.sh
• test_mc16PHYS_serial.sh

Example of output added by this MR for 2018 data period:

 302.316 kb       20.893 kb        0.005 kb       14.470     4136  TrigMatch_HLT_tau25_medium1_tracktwoEF (DataVector<xAOD::TrigComposite_v1>) [Trig]
 302.316 kb       20.893 kb        0.005 kb       14.470     4136  TrigMatch_HLT_tau35_medium1_tracktwoEF (DataVector<xAOD::TrigComposite_v1>) [Trig]
 302.316 kb       20.893 kb        0.005 kb       14.470     4136  TrigMatch_HLT_tau60_medium1_tracktwoEF (DataVector<xAOD::TrigComposite_v1>) [Trig]

Tagging @tamartin, @aranzazu, @jburr, @iriu, @gipezzul, @martindl and @calpigia

PhysicsAnalysis/DerivationFramework/DerivationFrameworkPhys/data/run2ExtraMatchingTauTriggers.txt

@@ -7,30 +7,49 @@
 ################
 # Tau Triggers #
 ################
-
+HLT_tau25_medium1_tracktwoEF
 HLT_tau25_medium1_tracktwoEF_L1TAU12I
 HLT_tau25_medium1_tracktwoEF_L1TAU12IM
+HLT_tau25_medium1_tracktwo
 HLT_tau25_medium1_tracktwo_L1TAU12
 HLT_tau25_medium1_tracktwo_L1TAU12I
 HLT_tau25_medium1_tracktwo_L1TAU12IM
+HLT_tau25_mediumRNN_tracktwoMVA
 HLT_tau25_mediumRNN_tracktwoMVA_L1TAU12I
 HLT_tau25_mediumRNN_tracktwoMVA_L1TAU12IM
+HLT_tau35_medium1_tracktwoEF
+HLT_tau35_medium1_tracktwoEF_L1TAU12IM
 HLT_tau35_medium1_tracktwoEF_L1TAU20I
 HLT_tau35_medium1_tracktwoEF_L1TAU20IM
+HLT_tau35_medium1_tracktwo
+HLT_tau35_medium1_tracktwo_L1TAU12IM
 HLT_tau35_medium1_tracktwo_L1TAU20
 HLT_tau35_medium1_tracktwo_L1TAU20I
 HLT_tau35_medium1_tracktwo_L1TAU20IM
+HLT_tau35_mediumRNN_tracktwoMVA
+HLT_tau35_mediumRNN_tracktwoMVA_L1TAU12IM
 HLT_tau35_mediumRNN_tracktwoMVA_L1TAU20I
 HLT_tau35_mediumRNN_tracktwoMVA_L1TAU20IM
+HLT_tau40_medium1_tracktwoEF
 HLT_tau40_medium1_tracktwoEF_L1TAU25
 HLT_tau40_medium1_tracktwoEF_L1TAU25IM
+HLT_tau40_medium1_tracktwo
 HLT_tau40_medium1_tracktwo_L1TAU25
 HLT_tau40_medium1_tracktwo_L1TAU25IM
+HLT_tau40_mediumRNN_tracktwoMVA
 HLT_tau40_mediumRNN_tracktwoMVA_L1TAU25
 HLT_tau40_mediumRNN_tracktwoMVA_L1TAU25IM
+HLT_tau50_medium1_tracktwo
 HLT_tau50_medium1_tracktwo_L1TAU12
+HLT_tau60_medium1_tracktwoEF
 HLT_tau60_medium1_tracktwoEF_L1TAU40
+HLT_tau60_medium1_tracktwo
 HLT_tau60_medium1_tracktwo_L1TAU40
+HLT_tau60_mediumRNN_tracktwoMVA
 HLT_tau60_mediumRNN_tracktwoMVA_L1TAU40
+HLT_tau80_medium1_tracktwo
+HLT_tau80_medium1_tracktwo_L1TAU60
+HLT_tau80_medium1_tracktwoEF
 HLT_tau80_medium1_tracktwoEF_L1TAU60
-HLT_tau80_mediumRNN_tracktwoMVA_L1TAU60
\ No newline at end of file
+HLT_tau80_mediumRNN_tracktwoMVA
+HLT_tau80_mediumRNN_tracktwoMVA_L1TAU60