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
Update Phase-I mis-alignment scenario (MC2017 V1) #21347
Update Phase-I mis-alignment scenario (MC2017 V1) #21347
Conversation
please test |
+1 |
@ghellwig are you holding up a "sarcasm" sign? :) |
The code-checks are being triggered in jenkins. |
+code-checks |
The tests are being triggered in jenkins. |
A new Pull Request was created by @mschrode (Matthias Schroeder) for master. It involves the following packages: Alignment/TrackerAlignment @cmsbuild can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@mschrode well, it is the most up-to-date pseudo-asymptotic scenario, i.e. it is only a very small "sarcasm" sign ;) |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
Comparison is ready Comparison Summary:
|
+1 |
Mis-alignment scenario used in 92X MC production of 2017.
Derived from a "pseudo"-aligment procedure:
Corresponding objects in prod DB: