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
implement correct track breaking if propagation fails #8826
Conversation
A new Pull Request was created by @VinInn (Vincenzo Innocente) for CMSSW_7_5_X. implement proper track breaking if propagation fails It involves the following packages: RecoTracker/CkfPattern @cmsbuild, @cvuosalo, @nclopezo, @slava77 can you please review it and eventually sign? Thanks. |
if(failed) continue; | ||
|
||
|
||
/* previous code |
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.
please remove instead of keeping old development "for posterity"
The tests are being triggered in jenkins. |
} | ||
|
||
// Get inner state | ||
const bool doBackFit = (!doSeedingRegionRebuilding) & (!reverseTrajectories); |
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.
For clarity, & should be &&, otherwise someone might think bitwise AND is actually needed here instead of logical AND. But this issue doesn't justify changing the PR at this stage -- only fix it if making other changes, too.
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.
It s intetioanlly BITWISE, because is faster in this particular case.
This pull request is fully signed and it will be integrated in one of the next CMSSW_7_5_X IBs unless changes (tests are also fine). This pull request requires discussion in the ORP meeting before it's merged. @davidlange6, @nclopezo, @ktf, @smuzaffar |
+1 |
implement correct track breaking if propagation fails
There is a pretty visible effect from this change on muon standAloneSET reconstruction (the regular standalone muons are not affected) QCD dijet 3 TeV (mostly punch-through low-pt muons) @jhgoh @battibass @bellan @trocino please follow up. |
modifications suggested by Ferenc (@sikler) as very visible at low momentum in minimum bias events
The main issue is that previous code in Smoother was "breaking" the track on the "wrong" side
i.e. returning the far part, not the one closest to the vertex.
The new track-shortening algorithm tries to keep the longest possible track preserving the hits closest to the vertex.
Effect is tiny, still visible for 0.5<|eta|<1.2, where more longer tracks are reconstructed.
Small regression expected,
the other two modifications have negligible impact in standard condition.