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
TTTrack bug fix for POCA #30663
TTTrack bug fix for POCA #30663
Conversation
@tomalin, CMSSW_11_2_X branch is closed for direct updates. cms-bot is going to move this PR to master branch. |
The code-checks are being triggered in jenkins. |
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30663/16946
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-30663/16947
|
A new Pull Request was created by @tomalin (Ian Tomalin) for master. It involves the following packages: DataFormats/L1TrackTrigger @cmsbuild, @rekovic, @benkrikler, @kpedro88 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@tomalin please make also the backport for 11_1_X |
I've added a second PR, #30666 , identical to this one, except that it (hopefully) backports this bug fix to 11_1_X. |
please test |
The tests are being triggered in jenkins.
|
+1 |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
merge |
+upgrade |
There was a bug in the variable "thePOCA", which represents the point of closest approach of the helix to the line x=y=0. This will affect anyone who uses the function TTTrack::POCA().
However, people using other TTTrack functions, such as those giving access to the helix parameters, will be unaffected.
I'd suggest back-porting this fix to CMSSW 11.1, if possible, as although I suspect few people use TTTrack::POCA(), the bug will confuse anyone who does.