Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Check 2017 double muon triggers #373

Open
kmohrman opened this issue Aug 4, 2023 · 0 comments
Open

Check 2017 double muon triggers #373

kmohrman opened this issue Aug 4, 2023 · 0 comments

Comments

@kmohrman
Copy link
Contributor

kmohrman commented Aug 4, 2023

It seems the POG recommendation is Mu17_TrkIsoVVL_Mu8_TrkIsoVVL_DZ_Mass3p8 or Mu17_TrkIsoVVL_Mu8_TrkIsoVVL_DZ_Mass8 (it's not super clear if they're suggesting a logical or between the two triggers, or if they're just saying that either can be used). In TOP-22-006, we use just the Mass3p8 one alone. However, it seems that this Mass3p8one did not actually exist for all of 2017 (as shown here), while the Mass8 one did (as shown here). So the Mass3p8 one (that we use alone) seems to be missing about 5/fb of data.

The effect is probably small, but it may be worth trying to understand before the next iterations of the analyses.

It would probably make sense to use a logical or between these triggers, and/or to reach out to the POG to clarify the recommendation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant