Skip to content

Remove overlapping muons in muon triggers

Savanna Shaw requested to merge sshaw/athena:msonly-ovlprm into master

Adding a check on whether we're considering identical muons in the muon trigger:

  • Add a check in the hypo alg to flag if we add a muon to the hypo tool input if a muon with the same parameters already exists (runs only for RoI based chains, as full scan triggers should by definition not reconstruct the smae muon multiple times)
  • In the hypo tool flag the overlapping muons as not passing the trigger
    • Only do the removal for MS tracks for ms-only triggers (overlapping RoIs may produce the same MS tracks but different ID tracks, so we should keep the overlapping MS tracks until we do the combination)
    • Remove overlapping combined muons for all RoI based triggers

Should help with some of the high rates reported in ATR-23813.

Merge request reports