-
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
Implement second HF min-bias feature bit #24847
Implement second HF min-bias feature bit #24847
Conversation
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-24847/6808 |
A new Pull Request was created by @christopheralanwest for master. It involves the following packages: CalibCalorimetry/HcalTPGAlgos @cmsbuild, @tocheng, @nsmith-, @rekovic, @franzoni, @thomreis, @ggovi, @pohsun, @lpernie can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
The tests are being triggered in jenkins. |
-1 Tested at: 54853ef You can see the results of the tests here: I found follow errors while testing this PR Failed tests: Build ClangBuild
I found compilation warning when building: See details on the summary page.
I found compilation warning while trying to compile with clang: |
Comparison not run due to Build errors (RelVals and Igprof tests were also skipped) |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
The expected effect of this PR is seen in the HI workflow 158.0. hcalOccSentFb and hcalOccRecdFb now have entries, corresponding to the new feature bit, and hcalOccSentFb2 and hcalOccRecdFb2 have more entries, a consequence of the lowered threshold for this bit in HI workflows. I don't understand the changes in data/emulation comparisons for taus, which should be unaffected by any sort of change in HF. The backport of this PR (#24857) sees changes in electrons rather than taus, adding to the confusion. These changes seem unrelated to this PR. |
@christopheralanwest thank you for your feedback, I am afraid the issue with taus is the same that we have already seen in previous PRs, and related to a non reproducibility of part of the L1T emulator/DQM chain, that should be fixed asap |
+1 |
+1 |
+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 now be reviewed by the release team before it's merged. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
Only a single min-bias trigger has been used for 2018 pp running. For the upcoming 2018 HI run, two min-bias triggers that have different thresholds, but are otherwise identical, have been requested.
This PR implements two changes:
pp_on_AA_2018
era, the HF trigger primitive simulation has been modified to generate two min-bias feature bits with thresholds of >15 and >19 ADC counts for the existing and new ("second") feature bit. These thresholds are similar to those that are expected to be used during the 2018 HI run. No changes are expected for any other era.