-
Notifications
You must be signed in to change notification settings - Fork 4.6k
[NGT] Promote SimDoublets to full SimPixelTracks for better Patatrack pixel tracking performance analysis
#49194
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
base: master
Are you sure you want to change the base?
[NGT] Promote SimDoublets to full SimPixelTracks for better Patatrack pixel tracking performance analysis
#49194
Conversation
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-49194/46499
|
|
type ngt |
|
@cmsbuild, please test |
|
-1 Failed Tests: HeaderConsistency ClangBuild Clang BuildI found compilation warning while trying to compile with clang. Command used: See details on the summary page. |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-49194/46501
|
|
Pull request #49194 was updated. |
b1cfd88 to
b629d80
Compare
|
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-49194/47169
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
|
Milestone for this pull request has been moved to CMSSW_16_1_X. Please open a backport if it should also go in to CMSSW_16_0_X. |
PR description:
This PR upgrades the existing class of
SimDoubletsto a more extensive class ofSimPixelTracks. This allows for a more detailed analysis of the Patatrack pixel tracking performance by providing additional simulation truth for more intermediate objects in Patatrack. This includes triplets and N-tuplets and their respective cuts applied when built in reconstruction.This PR is currently a draft and not ready for review. More detailed information will follow...
PR validation:
To be added...
If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
This PR is not a backport and there is no backport planned.