HLT GNTau implementation
It's finally here! This MR addresses the implementation of the GNTau algorithm and duplication of tau chains in the dev Menu (ATR-30086). The following changes are included:
- Included the
HLTGNTau_v1p0
model inference in thetracktwoMVA
sequence. - Set the
tracktwoMVA
sequence as the default for all tau chains.- The new GNTau-based chains don't include the
tracktwoMVA
param in the leg names. This allows to simplify tau legs, which will soon also start to include preselection and alt. reco specs. - Added a bypass to the default parameter check in
DictFromChainName.py
, to avoid unnecessary warnings until we fully decommission the RNN-based chains following the previous naming scheme during 2025.
- The new GNTau-based chains don't include the
- Added an option for alternative TauID score discriminants, required by the
HLTGNTau_v1p0
model. We will test other discriminants in the future, so it's better to add this generalization now instead of hard-coding PTau in the configs. - Added monitoring of the GNTau score in the
TrigTauMonitoring
package. - Duplicated all Physics and Dev menu chains including tau legs to use the new GNTau ID.
- All new chains have been placed in the Dev Menu.
- The new Physics chains will be moved to the Physics menu after the central reprocessing validations.
Tagging all other HLT GNTau team members, Tau Trigger experts and coordinators. Congratulations to all for the very hard work!
@asudhaka, @slai, @smwang, @mashamim, @htsoi, @cschiavi, @lderin, @fparodi, @abetti, @ademaria, @martindl
Edited by Jean Yves Beaucamp