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
treat a predicted state too far as invalid in CosmicMuonSmoother (backport of #33168) #33214
treat a predicted state too far as invalid in CosmicMuonSmoother (backport of #33168) #33214
Conversation
A new Pull Request was created by @slava77 (Slava Krutelyov) for CMSSW_11_2_X. It involves the following packages: RecoMuon/CosmicMuonProducer @perrotta, @jpata, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
backport of #33168 |
@cmsbuild please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-0d4897/13600/summary.html Comparison SummarySummary:
|
This pull request is fully signed and it will be integrated in one of the next CMSSW_11_2_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_11_3_X is complete. This pull request will now be reviewed by the release team before it's merged. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
(copy-paste from the 11_3_X)
this is a follow-up to the origins of the issue reported in https://hypernews.cern.ch/HyperNews/CMS/get/recoDevelopment/1706.html
in processing of date in Run: 340323, which has a seg fault.
This is a case of runaway fit leading to running over numerical precision limits with a final result as NaN. Some later code using this can crash (fixed separately in #33157).
I propose to have this backport to avoid possible (rare) crashes in MWGR data (re)processing.
This PR is expected to affect/fix only cases that are going to lead to a crash or are very close to that state; this should be OK in the no-change policy.