-
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
L1T o2o: fix int/2 bug #43510
L1T o2o: fix int/2 bug #43510
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-43510/38090
|
A new Pull Request was created by @bundocka for master. It involves the following packages:
@aloeliger, @cmsbuild, @epalencia 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-b4338f/36358/summary.html Comparison SummarySummary:
|
+l1 |
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. @rappoccio, @antoniovilela, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
This PR fixes a bug in the L1T o2o where an integer type is being divided by 2 and producing truncated float output.
During the 2023 HI run, the jet seed threshold was set to 5, thus the GT was populated with the incorrect value of 2 instead of 2.5. HI have requested this be fixed retrospectively in the GT (to be followed up with AlCa).
With this fix, future L1TCalo o2o'd payloads will contain the correct values for parameters divided by 2 that take odd numbers in the HW key.
No backport required.