-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
eg hlt filter threshold reduction to 15 \GeV from 20\GeV #40909
Conversation
Adding H to gg convener @lfinco here to keep track |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40909/34391
|
A new Pull Request was created by @Soumyatifr for master. It involves the following packages:
@cmsbuild, @swertz, @vlimant can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
enable nano |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-186f47/30965/summary.html Comparison SummarySummary:
NANO Comparison SummarySummary:
Nano size comparison Summary:
|
Hi @Soumyatifr , I'm surprised to not see any difference in the tests. Of course this might entirely be due to the samples we use for those tests (e.g. TTbar or Muon data), that wouldn't contain events triggered with low-pt photon paths... On the other hand, looking at the filters for which the objects are stored, I don't see any such low pt photons either. Are you sure you don't need to add some corresponding filters? A trigger object will only be saved if it passes at least one of the listed filters. |
in a previous PR (#40711), he added this filter -> it appears here:
It's a photon leg with 18 GeV Et cut |
Thanks @swagata87 , I'd overlooked that one - and indeed also in #40711 there were no events in the tests passing that filter, due to the choice of samples... All good then. |
+1 |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
is there a 13.0 back port expected for this ? |
Indeed, @Soumyatifr can you please take care? |
@Soumyatifr , kind ping for a backport to 13_0_X. |
Hi @Soumyatifr @swagata87 just a reminder that if you want this included for NanoAODv12 and 2023 data prompt NanoAOD, there should be a backport to 13_0_X. |
I was expecting that Soumya or someone from Higgs to gamma gamma would respond to this. They are the primary user of the HLT path/filter in question here. I will send an email to the Hgg convenors now. |
Yes, Soumya is going to take care of it, just pinged. |
PR description:
PR validation:
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
Before submitting your pull requests, make sure you followed this checklist: