-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[TkAl] Realign DQM and Offline analysis of μμ + vertex events #42971
[TkAl] Realign DQM and Offline analysis of μμ + vertex events #42971
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42971/37140
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
4839b20
to
3431a32
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42971/37141
|
A new Pull Request was created by @mmusich (Marco Musich) for master. It involves the following packages:
@nothingface0, @tjavaid, @rvenditti, @cmsbuild, @antoniovagnerini, @saumyaphor4252, @consuegs, @syuvivida, @perrotta can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
3431a32
to
d8087e7
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-42971/37145
|
Pull request #42971 was updated. @saumyaphor4252, @nothingface0, @syuvivida, @perrotta, @consuegs, @antoniovagnerini, @rvenditti, @cmsbuild, @tjavaid can you please check and sign again. |
@cmsbuild, please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-c4b5c5/35112/summary.html Comparison SummarySummary:
|
+alca |
+1 |
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. @rappoccio, @antoniovilela, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
Title says it all. After offline investigation (mainly from @vbotta) some discrepancy was found when comparing the results from the
DiMuonVertexValidation
module (in the packageAlignment/OfflineValidation
) andDiMuonVertexMonitor
(in the packageDQMOffline/Alignment
).These were traced back to the fact that the DQM module (by default) selects the primary vertex closest to the di-muon vertex, while the one in
Alignment/OfflineValidation
selects the first one (presumably the hardest in the event, but not guaranteed because there is no re-sorting post-refit). This is addressed in 2e70c3b by offering the user the possibility to use the closest (to X→μμ decay vertex) or the first primary vertex.The other two commits:
DiMuonVertexValidation
,DiMuonVertexMonitor
, that were useful during the debugging process.PR validation:
Run successfully:
scram b runtests_DiMuonVertex use-ibeos
scram b runtests_testDiMuonVertexMonitor use-ibeos
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:
N/A