-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Bug Fix in Ecal/Hcal Digitizers for FASTPU aka Hybrid PU Mixing #49618
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
Bug Fix in Ecal/Hcal Digitizers for FASTPU aka Hybrid PU Mixing #49618
Conversation
…ags for Signal/PileUp SimHit collection
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-49618/47154 |
|
A new Pull Request was created by @subirsarkar for CMSSW_16_0_FASTPU_X. It involves the following packages:
@civanch, @cmsbuild, @kpedro88, @mdhildreth can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
test parameters: |
|
please test |
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-1b0895/49946/summary.html Comparison SummarySummary:
|
|
+simulation |
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_16_0_FASTPU_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_16_0_X is complete. This pull request will now be reviewed by the release team before it's merged. @mandrenguyen, @ftenchini, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 |
PR description:
A bug was found in Ecal and Hcal Digitizers where std::set was being used to hold the SimHit InputTag for signal and PU events. The order was found to be wrong. The std::set is now removed and the token for signal is directly created from the signal simHit InputTag.
PR validation:
Bug found during validation with officially produced data samples. Post bug-fix validation done with a small privately produced TTbar dataset
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:
@suchandradutta @kpedro88 @bsunanda