Skip to content

TrigEDMConfig: write HLT tau track impact parameters to AOD

Bertrand Martin Dit Latour requested to merge martindl/athena:R22_TrigTauTrackDecorEDM into master

Hello,

This MR is adding HLT tau track impact parameters and significances (4 new floats per track) to the Run3 trigger EDM file, for one container (HLT_tautrack_MVA), so that these variables are available in AOD. These variables are dynamic variables that will be needed to train RNN tau ID for Run3 tau triggers: d0TJVA, d0SigTJVA, z0sinthetaTJVA, z0sinthetaSigTJVA. The others in the list are static Aux variables that were already kept by default. The only Aux variable not appearing in the list is bdtScores, which is no longer used in R22 (neither offline nor online).

From 40 q221 events,

checkFile myAOD.pool.root | grep HLT_tautrack_MVA
       1.400 kb        0.311 kb        0.008 kb        0.000       40  (B) HLT_tautrack_MVA
      16.202 kb        1.406 kb        0.035 kb        0.000       40  (B) HLT_tautrack_MVAAuxDyn.viewIndex
       6.772 kb        3.437 kb        0.086 kb        0.000       40  (B) HLT_tautrack_MVAAuxDyn.d0TJVA
       6.826 kb        3.443 kb        0.086 kb        0.000       40  (B) HLT_tautrack_MVAAuxDyn.z0sinthetaSigTJVA
       6.812 kb        3.448 kb        0.086 kb        0.000       40  (B) HLT_tautrack_MVAAuxDyn.z0sinthetaTJVA
       6.787 kb        3.459 kb        0.086 kb        0.000       40  (B) HLT_tautrack_MVAAuxDyn.d0SigTJVA
      74.975 kb       12.182 kb        0.305 kb        0.000       40  (B) HLT_tautrack_MVAAux.

Hopefully the size increase is acceptable.

For completeness, I have updated the q221 digest reference file to reflect the new AOD content, although currently the CI test seems to ignore the L1 and HLT trigger content. I guess that's why people don't bother updating this file when the trigger content changes, and must explain why non-tau trigger changes are reported.

Tagging @ademaria , @iriu , @okuprash .

Cheers, Bertrand

Merge request reports