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
Enable mkFit by default in 4+2 tracking iterations (initialStepPreSpl… #35660
Enable mkFit by default in 4+2 tracking iterations (initialStepPreSpl… #35660
Conversation
…itting, initialStep, highPtTripletStep, detachedQuadStep + detachedTripletStep, pixelLessStep)
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-35660/25930
|
A new Pull Request was created by @mmasciov (Mario Masciovecchio) for master. It involves the following packages:
@cmsbuild, @perrotta, @qliphy, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild, please test |
@cms-sw/reconstruction-l2 Should reco sign this? |
Also FYI @cms-sw/tracking-pog-l2 |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-90ee4c/19615/summary.html Comparison SummarySummary:
|
assign reconstruction |
Could you link a presentation in the description where the tracking performance (and if possible, also downstream performance) of just this PR is shown? The current link in the description is to the PPD news / plans, where the effect of just these two additional iterations is not clear to me. |
@jpata, the description of the PR has been updated as requested, with MTV results showing that tracking performance after this PR (together with PR #35652 and updated PR #35686) is largely improved. |
+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:
Following PR #35457, this PR enables mkFit for tracking in 4 (initialStepPreSplitting, initialStep, highPtTripletStep, detachedQuadStep) + 2 (detachedTripletStep, pixelLessStep) tracking iterations for the entire era of Phase-1 pixel detector (i.e. from 2017 to end of Run 3), except for HI eras (Run2_2017_pp_on_XeXe, Run2_2017_ppRef, Run2_2018_pp_on_AA, Run2_2018_pp_on_AA_noHCALmitigation, Run3_pp_on_PbPb) and 2017 special tracking eras (Run2_2017_trackingLowPU, Run2_2017_trackingRun2), following the plan presented in https://indico.cern.ch/event/1082441/#1-news
Note: the first 4 iterations were already enabled in PR #35457; this PR enables 2 additional iterations.
PR validation:
The performance of tracking after this PR, together with PR #35652 and PR #35686 (updated as suggested here) follows:
http://uaf-10.t2.ucsd.edu/~mmasciov/MkFit_devs/PRvalidation_Oct13/MTV_PR35660_mkFit-6iter_DNNfinalWP_afterPR35652/
Looking at out-of-the-box high-purity tracks (http://uaf-10.t2.ucsd.edu/~mmasciov/MkFit_devs/PRvalidation_Oct13/MTV_PR35660_mkFit-6iter_DNNfinalWP_afterPR35652/plots_highPurity/effandfakePtEtaPhi.pdf), efficiency is (much) improved (at low track pT), with overall lower fake+duplicate rate.