-
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
Correct GEM edge calculation for TrackerMuons #40554
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40554/33786
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40554/33787
|
A new Pull Request was created by @jo100sun (Jo100) 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 |
please test |
-1 Failed Tests: Build BuildI found compilation warning when building: See details on the summary page. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-40554/33791
|
Pull request #40554 was updated. @cmsbuild, @mandrenguyen, @clacaputo can you please check and sign again. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-46aad4/30076/summary.html Comparison SummarySummary:
|
type -tracking a case of false-positive in cms-sw/cms-bot#1916 |
I think the differences that are seen in the matches match what we expect: correcting the edge calculation will reject some GEM matches that were previously accepted (inside the rectangular boundary, but not in the trapezoidal boundary). This decrease can be seen in the recoMuons_displacedMuons__RECO_obj_muMatches__detector plots. Then with fewer chamber matches, the corresponding chamber match plots will all have fewer entries. |
+reconstruction |
+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 be automatically merged. |
PR description:
When filling chambermatches to TrackerMuon, it calculates edge distance of a muon track on the detector surface from the detector edge.
It is assuming the rectangular shape, but GEM detector is trapezoid.
So we fixed wrong edge distance calculation.
@watson-ij @jshlee
PR validation:
We ran a runThematrix test in run3 and phase2 Zmumu setup. We saw that edge is now calculating correctly in TrackerMuon. We reported this fixes in the muon dpgo meeting https://indico.cern.ch/event/1232229/contributions/5186787/attachments/2568843/4429266/20221216-muon-dpgo.pdf
and the GEM DPG meeting https://indico.cern.ch/event/1241721/contributions/5219032/attachments/2576699/4444051/Low%20efficiency%20at%20GE2_1%20in%20phase%202%20condition%20(5).pdf
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:
Before submitting your pull requests, make sure you followed this checklist: