-
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
SiStripClusterizer: veto zero-charge clusters #16572
SiStripClusterizer: veto zero-charge clusters #16572
Conversation
A new Pull Request was created by @pieterdavid (Pieter David) for CMSSW_8_1_X. It involves the following packages: HLTrigger/Configuration @perrotta, @cmsbuild, @silviodonato, @cvuosalo, @fwyzard, @Martin-Grunewald, @slava77, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here #13028 |
-1 |
@@ -1,7 +1,7 @@ | |||
import FWCore.ParameterSet.Config as cms | |||
|
|||
SiStripClusterChargeCutNone = cms.PSet( | |||
value = cms.double(-1.0) | |||
value = cms.double(0.0) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a comment explaining that the value must not be less than zero (and the reason for that)? Thanks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi all,
I have a very vague recollection of the problem, but in general I would not use side-effects (the CCC) to fix local-reco problems. If clusters with 0 charge are a problem, we should get rid of them explicitly in local-reco, not as a side-effect of CCC (like you seem to imply here, since -1 meant no cut, while your proposal means 0 is always a valid cut)
I'm sorry, I had not realised that SiStripClusterChargeCutNone is also used for other things than the CCC in the clusterizer, so just changing that may also introduce problems elsewhere. I will close this pull request and prepare a new one with a modification to the clusterizer itself, as Marco suggested. |
See the discussion in #13945 : zero-charge clusters get a NaN position error from the CPE, which leads to a segmentation fault in the reconstruction.
Fixed by changing the value of (HLT)SiStripClusterChargeCutNone from -1 to 0 (it is compared using ">" in https://github.com/cms-sw/cmssw/blob/CMSSW_8_1_X/RecoLocalTracker/SiStripClusterizer/src/ThreeThresholdAlgorithm.cc#L85)