add support for trigger matching for Run 3 data and MC #1638
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support of trigger matching for electron- and muon triggers for Run3 data and MC. As these have a new trigger navigation a dedicated matching tool has to be set up (following the R22TriggerAnalysis twiki). In contrast to "Run2 samples", no distinction seems to be required between PHYS and non-PHYS samples though.
As small additional adjustment was also required to
MuonEfficiencyCorrector.cxxin order to allow for a proper retrieval of muon trigger SFs for 2022.