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
small improvements to HLTSumJetTag
#36981
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36981/28357
|
A new Pull Request was created by @missirol (Marino Missiroli) for master. It involves the following packages:
@cmsbuild, @missirol, @Martin-Grunewald can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b27ec4/22466/summary.html Comparison Summary@slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
|
+hlt
|
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, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR provides small improvements to the HLT filters introduced in #36862 (cc: @rgerosa), including a follow-up to the review comments in #36862 (review).
One change is not merely technical; it concerns the case where
MatchByDeltaR == true
. In the original implementation, every jet is assigned a "jetTag" value, and, when there is no valid Delta-R match with a jet in the JetTag map, then the tagValue is set to an arbitrary -1000. In this PR, jets without a valid DR-match are instead skipped; for realistic cuts on "JetSumTag", the two approaches should be equivalent from a practical point of view, and I would suggest to use the one in this PR.Since the relevant plugins are not run in any central wf, the PR tests are not expected to be sensitive to this PR.
PR validation:
I manually checked with the recipe provided in cms-data/RecoBTag-Combined#47 (comment) (plus some edits to the config file, using one instance of the plugin with
MatchByDeltaR=false
and one withMatchByDeltaR=true
) that the results of the HLT filters, and corresponding trigger objects, are exactly the same for 100 MC events.If this PR is a backport, please specify the original PR and why you need to backport that PR:
N/A