-
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
pick ecal fraction of 0 for a candidate with trackMomentum 0 #11302
pick ecal fraction of 0 for a candidate with trackMomentum 0 #11302
Conversation
A new Pull Request was created by @slava77 (Slava Krutelyov) for CMSSW_7_4_X. pick ecal fraction of 0 for a candidate with trackMomentum 0 It involves the following packages: RecoParticleFlow/PFProducer @cmsbuild, @cvuosalo, @slava77 can you please review it and eventually sign? Thanks. |
@cmsbuild please test |
The tests are being triggered in jenkins. |
@cmsbuild please test |
The tests are being triggered in jenkins. |
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_4_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_7_6_X is complete. This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @Degano, @smuzaffar |
…Algo-NaN-ecalE-postPhoton pick ecal fraction of 0 for a candidate with trackMomentum 0 (same as #11302)
+1 |
…postPhoton pick ecal fraction of 0 for a candidate with trackMomentum 0
This is a follow up to investigation of origins of the NaN PFCandidate that leads to a crash in
https://hypernews.cern.ch/HyperNews/CMS/get/recoDevelopment/1385.html
Here, the ecal raw energy was set to infinity, while the momentum is still OK.
Then later in the PFCandConnector, in the process of updating the momentum to account for nuclear interations, the candidate momentum is updated based on the calorimeter energy values. That's the point where the final candidate momentum turns to a NaN.
@bachtis please check if fraction=0 makes sense in this case.
If confirmed, I'd run more tests and propagate to 75X/76X.