-
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
Update trigger filters for jets stored in Nano for Run3 menu #39818
Update trigger filters for jets stored in Nano for Run3 menu #39818
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39818/32686
|
A new Pull Request was created by @johnalison (John Alison) 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 |
Hi @johnalison , for my information, I suppose this change is not compatible with Run2 samples/triggers? We are planning to change the way trigger object info is stored in nano, but for now we have decided that we would allow changes to the trigger object filter names necessary for Run3 so that prompt nano can pick those up, even if it breaks compatibility with Run2 or existing V10 samples. Can you please apply the same changes to the "frozen" V10 config, so that V10 stay in sync between 124X and 126X? https://github.com/cms-sw/cmssw/blob/master/PhysicsTools/NanoAOD/python/V10/triggerObjects_cff.py |
@swertz correct. I have removed the filters that are not Run 3 and added filters that are not in Run-2. |
@swertz changes now in V10 config |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39818/32820
|
enable nano |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-dce978/28660/summary.html Comparison SummarySummary:
NANO Comparison Summary@slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
Nano size comparison Summary:
|
+1 Only differences are seen in jet trigger objects. |
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
|
PR description:
Updating the Jet Trigger objects stored in Nano with the filters from the Run3 menu
Expect the trigObj content of the Nano to change.
PR validation:
Tested producing new NanoAOD in 12_4_8
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:
Would be good to have this in 12_4_X for Run3 Nano production.