-
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
Addition of Hgg trkSumPtHollowConeDR03 variable in NanoAOD #40583
Addition of Hgg trkSumPtHollowConeDR03 variable in NanoAOD #40583
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40583/33835
|
A new Pull Request was created by @VourMa (Manos Vourliotis) 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-415fa9/30113/summary.html Comparison SummarySummary:
NANO Comparison SummarySummary:
Nano size comparison Summary:
|
+1 New variable visible in DQM and looks reasonable. |
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 |
This PR is a follow-up to a couple of updates made to the NanoAOD content to accommodate variables that are needed for the preselection of H -> γγ analyses.
PRs #36037 and #36526 applied the changes advertized in an XPOG meeting presentation some time ago. The variable
trkSumPtHollowConeDR03
is mentioned in the slides but was included neither in the aforementioned PRs nor in a subsequent one. After a communication with the XPOG conveners, the Hgg conveners and the authors of the previous relevant PRs, this PR comes to include this variable.As a simple validation, a custom NanoAOD file was produced with the updated configuration and it included the new branch with reasonable values.