-
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
add layer-TSOS compatibility check in LayerMeasurements
#42320
add layer-TSOS compatibility check in LayerMeasurements
#42320
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42320/36348
|
A new Pull Request was created by @missirol (Marino Missiroli) for master. It involves the following packages:
@cmsbuild, @mandrenguyen, @clacaputo can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
8fc4bef
to
d495adf
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42320/36349
|
Pull request #42320 was updated. @cmsbuild, @mandrenguyen, @clacaputo can you please check and sign again. |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c7ff3f/33805/summary.html Comparison SummarySummary:
|
+reconstruction |
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
Given the changes in data-taking schedule, I guess a backport to |
+1 I think it doesn't hurt to have the 13_0_X backport as well, unless there are some conflicts. |
PR description:
This PR includes a possibile solution for the issue discussed in #40174 (see that issue for details), thanks to suggestions from @cms-sw/tracking-pog-l2.
#42318 contains a different solution for the same issue. The two PRs are not mutually exclusive (in principle, both could be integrated).
In this PR, a check is added to
LayerMeasurements
in order to skipTrajectoryStateOnSurface
objects whose global position is well outside the detector volume. The rationale of this check was discussed in #40174 (comment).PR validation:
Manual checks with the reproducers in #40174 (comment) and #40174 (comment).
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:
TBD