-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Store L1 prefiring weights in 2016 and 2017 MINIAOD #26654
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-26654/9615
|
A new Pull Request was created by @peruzzim for master. It involves the following packages: Configuration/Eras @perrotta, @cmsbuild, @franzoni, @slava77, @santocch, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
Comparison job queued. |
Comparison is ready Comparison Summary:
|
assign xpog for future reference |
@peruzzim you are filling the L1 prefiring weights in miniAOD also for real data, not only for MC. |
this was actually done on purpose, in order to allow for data/MC comparison of weight distributions e.g. in unprefireable events, or otherwise orthogonally selected samples |
+1
|
+xpog |
+1 |
+operations the update of Configuration is coherent with the purpose of this PR |
+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 be automatically merged. |
This PR adds L1 prefiring weights to MINIAOD event content for 2016 and 2017 datasets.
A new modifier
run2_L1prefiring
is defined to trigger this evaluation, and added to theRun2_2016
andRun2_2017
eras.Existing trigger modifiers are then used to customise its payload configuration, that is different for each year.