Skip to content

Update muon trigger SF config to avoid MC20a warnings

Thomas Strebler requested to merge tstreble/athena:MuTrigSF_MC20a into main

For MC20a samples, combining 2015 and 2016 triggers, the MuonTriggerScaleFactors tool currently returns many warnings of the form

MuonTrigEfficiencyCorr...efficiencyScaleFactorToolWARNING Could not find what you are looking for in the efficiency map. The trigger you are looking for, year and mc are not consistent, or the trigger is unavailable in this data period. Returning efficiency = 0.

because of 2015 triggers checked with 2016 events and vice versa.

This MR configures the min/max run number for the CP algorithm to avoid using the tool for 2015 triggers on 2016 event and vice versa.

Merge request reports