-
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
Filter tracks extrapolated to the muon system #41323
Filter tracks extrapolated to the muon system #41323
Conversation
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41323/35143
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-41323/35145
|
A new Pull Request was created by @CeliaFernandez (Celia Fernández Madrazo) 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 |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-41323/35150
|
Pull request #41323 was updated. @cmsbuild, @mandrenguyen, @clacaputo can you please check and sign again. |
enable profiling |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-619298/31955/summary.html Comparison SummarySummary:
|
Looks like this PR is causing genuine changes: https://cmssdt.cern.ch/SDT/jenkins-artifacts/baseLineComparisons/CMSSW_13_1_X_2023-04-12-1100+619298/56509/validateJR.html |
Thanks @mmusich , I did not observe these changes before... Indeed the proposed changes are not fully transparent and this effects need to be understood.
And at the same time, the number of chambers seems to be "switching" some of the values to zero: I suspect that the muons suffering these changes are those whose tracks are successfully extrapolated to chambers but none of the extrapolated chambers have segments. These were counted before when all the extrapolations were done. However here, where the extrapolations are done only if at least one of the chambers have segments, these are not counted. Since tracker muons have at least one segment (the implementation was done taking this into account) I suspect that the affected muons are global/standalone muons which do not make it to tracker muons. I will do more studies to check is this is the case and try to fully understand what is happening... |
@CeliaFernandez Any update here? Would you say these differences are now expected? |
Hi @mandrenguyen, sorry for the late reply. It took me more time to check than I thought... After doing so, the hypothesis presented here is confirmed:
Whenever there are no segments/hits, the track extrapolation is aborted and numberOfChambers() is set to zero. This leads to changes in this variable for muons that are not reconstructed as TrackerMuons i.e. Standalone muons (which could be Global o not). |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-619298/33094/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) |
type performance-improvements |
type muon |
+1 |
PR description:
This PR modifies the track extrapolation to the muon chambers to reduce the time taken in muons1stStep sequence. In the current setup all tracks (passing soft pt and eta requirements) are extrapolated to all chambers that are geometrically compatible with the track parameters. The proposed changes allow to check if there are segments/hits in these chambers before initiating any extrapolation. If there are segments/hits, the track is extrapolated to the compatible chambers, if not, extrapolation is aborted.
Implementation was built on top of 13_0_0_pre3.
The time taken by muon1stStep was reduced from 4.5% to 3.8%, which translates into a reduction of total RecoMuon time from 7.0% to 6.1%. This measurement was done in lxplus with low precision, so checks are required.
No changes are expected in any collection as this PR is not intended to modify any physics behavior but reduce the time taken by muon reconstruction.
More info in this presentation: https://indico.cern.ch/event/1257332/
Some notes:
fillDescriptions
toAlignment/OfflineValidation
plugins #40698), although the proposed changes should give an equivalent outcome. How can I proceed here?PR validation:
This PR was tested with standard 11834.21 workflow. It passes the runTheMatrix tests with the exception of 2 where the connection of the input samples couldn't be readed.
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:
This PR is not a backport.