-
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
[12.3.X] Fix Tracker Alignment Payload writing #37926
[12.3.X] Fix Tracker Alignment Payload writing #37926
Conversation
type bug-fix |
A new Pull Request was created by @mmusich (Marco Musich) for CMSSW_12_3_X. It involves the following packages:
@cmsbuild, @malbouis, @tvami, @yuanchao, @francescobrivio can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
type trk |
@cmsbuild, please test |
urgent
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-25e3a6/24666/summary.html Comparison SummarySummary:
|
+alca |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_3_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_12_4_X is complete. This pull request will now be reviewed by the release team before it's merged. @perrotta, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
backport of #37925
PR description:
The goal of this PR is to fix a bug inadvertently introduced at #36076 (aimed to migrate Alignment codes to new
PoolDBOutputService
methods).Moving to usage of instances instead of pointers led to the
GeometryAligner::removeGlobalTransform
call (to remove global roto-translations after computation of the alignment corrections) to be ineffective. This in turn lead to large spurious rotations and shifts of the alignment output geometry with respect to the input one.This is fixed here in commit eb88897.
PR validation:
Run a small alignment campaign (copied from
mp3495
) and compared the output payloads with respect to the input one. Results (obtained from the payload inspector) are collected:Here is a couple of plots selected from the folders above (notice the scale).
if this PR is a backport please specify the original PR and why you need to backport that PR:
partial backport of #37925