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
Displace-tracking development in heavy ion tracking #21930
Displace-tracking development in heavy ion tracking #21930
Conversation
…with cms-merge-topic
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-21930/2998 |
A new Pull Request was created by @KongTu (KongTu) for master. It involves the following packages: RecoHI/HiTracking @perrotta, @cmsbuild, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
the plot has "blue" (this PR) both above and below the baseline. |
@cmsbuild please test |
The tests are being triggered in jenkins. |
Each point here represents the processing time of a single event, so I suspect the difference seen in the lower bins is just a fluctuation in the processing time. The code here does not 'remove' any features for central events to make them run faster; it only adds tracking iterations for more peripheral events. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
The code-checks are being triggered in jenkins. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-21930/3384 |
The tests are being triggered in jenkins. |
+1 The following merge commits were also included on top of IB + this PR after doing git cms-merge-topic: |
Comparison job queued. |
|
||
mixedTripletStepSeedLayersA.layerList = cms.vstring('BPix1+BPix2+BPix3', 'BPix1+BPix2+FPix1_pos', 'BPix1+BPix2+FPix1_neg', | ||
'BPix1+FPix1_pos+FPix2_pos', 'BPix1+FPix1_neg+FPix2_neg', | ||
'BPix2+FPix1_pos+FPix2_pos', 'BPix2+FPix1_neg+FPix2_neg') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the modifications made here actually propagate to hiRegitMuMixedTripletStepSeedLayersA.
I'm not sure that this is desired.
Based on the phase-0 configuration (wf 140.53) this is the only place with such dependency.
An easy fix is to set the layerList in hiRegitMuMixedTripletStepSeedLayersA explicitly.
OTOH, perhaps it's OK to have a more covering layer list for hiRegitMuMixedTripletStepSeedLayersA
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@slava77 I think having the extra layers in the list for the Regit step is fine; these steps tend to run quite quickly and produce a fairly small number of tracks. It is probably best for consistency to keep these two iterations using the same layer list.
Comparison is ready Comparison Summary:
|
Based on wf 150.0 I see that
Physics performance roughly looks as expected:
I'm ready to signoff pending the resolution of the hiRegitMuMixedTripletStepSeedLayersA configuration |
+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. @davidlange6, @slava77, @smuzaffar, @fabiocos (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
This displace-tracking development in heavy ion reconstruction is to find (like CMS standard pp tracking) the large impact parameter tracks for strange particles or heavy-flavor particles reconstruction.
This PR contains the following items:
Supporting presentations:
Performance plots on efficiency, fake rate, secondary rate (where it matters), https://indico.cern.ch/event/699094/contributions/2867255/attachments/1587914/2512006/Tracking_PR_preparation.pdf
Note that the comparison here is to compare "default" values from the standard pp tracking vs the modified values in the TrackingRegion parameters of the added iterations.
Study of V0s in terms of added 3 iterations:
https://indico.cern.ch/event/638128/contributions/2585615/attachments/1460150/2255756/Tracking_6_90X.pdf
https://indico.cern.ch/event/646309/contributions/2625076/attachments/1475706/2285788/Tracking_7_90X.pdf
Timing study as a function of Npix, https://indico.cern.ch/event/699094/contributions/2867255/attachments/1587914/2511992/Timing_displacedTracking_Jan24.pdf
@abaty @mandrenguyen