-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[14_0_X] Removal of ZDC Digitizer #46282
[14_0_X] Removal of ZDC Digitizer #46282
Conversation
A new Pull Request was created by @abdoulline for CMSSW_14_0_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 |
cms-bot internal usage |
please test |
urgent |
+1 Size: This PR adds an extra 20KB to repository Comparison SummarySummary:
|
+1 big difference in regresion connected with change of random number sequence |
This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_2_X is complete. This pull request will now be reviewed by the release team before it's merged. @mandrenguyen, @sextonkennedy, @rappoccio, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
Shall I backport #46286 to 14_0_X? If so, then please do not merge this PR. The backport and this PR will have conflicts |
Backport of #46286 allows ZDC digitization to be active while protects against bad ZDC DetIds |
I'm closing this PR then. |
In favor of Sunanda's more complete solution. |
silencing the digitizer all together in 14.0 is a much safer solution IMO, instead of backporting bugfixes to shady situations (how can a detid unkwon ... ) |
OK, let me reopen it "just in case"... |
hold |
Pull request has been put on hold by @mandrenguyen |
Hi all, one extra argument do not merge this PR but give a favor to #46300 : if we have the same approch to handle ZDC 14_0, 14_1, 14_2 it will give chance fully understand the problem in future and provide full fix without spliting branches for different fixes. The idea of this fix to add a filter, which exclude bad ZDC IDs seems to be safe, at least, to me. |
ZdcTopology object needs to be created by ESProducer in solutions of 14_1_X and 14_2_X. So the solution to HcalDigitizer is somewhat different in the 3 versions. All future versions will make use the solution in 14_1_X and 14_2_X. Since 14_0_X is a closed release and there is some doubt if the backport of #46246 will be accepted, this is shorter solution to fix the issue. If the backport #46246 is still alive we need to change this fix and also modify #46246 |
then this PR should be unhold and #46300 should be closed. |
unhold |
This pull request is fully signed and it will be integrated in one of the next CMSSW_14_0_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_14_2_X is complete. This pull request will now be reviewed by the release team before it's merged. @rappoccio, @antoniovilela, @mandrenguyen, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This is 14_0_X-specific "quick and dirty" patch in view of the 2024 MC production issues, discussed in #43582
PR validation:
One of the problematic wfs (crashing on ev.33) 180.1 ran OK over 1000 ev
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:
It's not intended for 14_1_X/14_2_X