-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Remove unpackLayer1 option from L1REPACK:Full #43981
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43981/38894
|
A new Pull Request was created by @eyigitba for master. It involves the following packages:
@cmsbuild, @rappoccio, @davidlange6, @fabiocos, @antoniovilela can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
Please make a backport PR to 14_0. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-ed49cd/37500/summary.html Comparison SummarySummary:
|
@cms-sw/operations-l2 , this fix (esp. its backport, #43985) is needed for offline trigger studies. Could you please have a look ? Thanks ! |
+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. |
PR description:
This PR removes the
unpackLayer1
fromL1REPACK:Full
. This was brought into our attention by TSG colleagues and it was causing unrealistic rates when re-emulating data after 2023A.There might be an underlying reason to why this problem started happening, but for the time being we prefer to remove this option and use
unpackHcal
directly. This is more in line with how ECAL TPs are used. TheunpackLayer1
step was probably an artifact from Run 2, which is not needed anymore.PR validation:
Validated that the
L1REPACK:Full
workflows still work after the change and the rates obtained are as expected.FYI @missirol @savarghe @caruta @aloeliger @epalencia