-
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
Phase II Patatrack Pixel Local Reco #36235
Phase II Patatrack Pixel Local Reco #36235
Conversation
Validation plots/RelValTTbar_14TeV/CMSSW_12_1_0_pre5-PU_121X_mcRun3_2021_realistic_v15-v2/GEN-SIM-DIGI-RAW
/RelValZMM_14/CMSSW_12_1_0_pre5-PU_121X_mcRun3_2021_realistic_v15-v1/GEN-SIM-DIGI-RAW
Validation plots (CPU vs GPU)/RelValTTbar_14TeV/CMSSW_12_1_0_pre5-PU_121X_mcRun3_2021_realistic_v15-v2/GEN-SIM-DIGI-RAW
/RelValZMM_14/CMSSW_12_1_0_pre5-PU_121X_mcRun3_2021_realistic_v15-v1/GEN-SIM-DIGI-RAW
Throughput plots/EphemeralHLTPhysics1/Run2018D-v1/RAW run=323775 lumi=53logs and
|
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36235/26865
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
@emiglior FYI |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-36235/26866
|
A new Pull Request was created by @AdrianoDee for master. It involves the following packages:
@malbouis, @civanch, @yuanchao, @makortel, @cvuosalo, @fwyzard, @ianna, @mdhildreth, @cmsbuild, @Dr15Jones, @slava77, @jpata, @tvami, @francescobrivio can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@srimanob FYI. Would be eventually nice to have some wf to test phase-2 GPU reconstruction. |
@cmsbuild please test |
@AdrianoDee shouldnt |
@cmsbuild please abort |
enable gpu |
@cmsbuild please test |
+Upgrade |
+1 |
|
||
auto const& input = iEvent.get(pixelDigiToken_); | ||
|
||
const TrackerGeometry* geom_ = &iSetup.getData(geomToken_); |
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 esConsumes()
is missing for geomToken_
and that is causing workflow 39434.502 step 3 to fail on a machine with a GPU (see #36604).
+1 |
-1 Failed Tests: RelVals RelValsValueError: Undefined workflows: 39434.5, 39434.501, 39434.502 GPU Comparison SummarySummary:
|
+heterogeneous |
This pull request is fully signed and it will be integrated in one of the next master IBs (but tests are reportedly failing). |
cms-bot internal usage |
PR description:
Allowing Patatrack tracker local reco to run on Phase2 tracker. A summary:
maxNumModules
to 4000 to allow for Phase2 tracker geometry to be accommodated;maxNumDigis
(set based on ttbar events @ =200);28
forTrackingRecHit2DSOAView:: PhiBinner
. This in principle could be templated but seems to me it would mess up with too many specialized definitions.m_nMaxModules
(and it's getternMaxModules()
forTrackingRecHit2DSOAView
andTrackingRecHit2DHeterogeneous
to determine hits module structures sizes; added in the constructor forTrackingRecHit2DHeterogeneous
.phase1PixelTopology
topixelTopology
and separating the two topologies in two namespaces (namelyphase1PixelTopology
andphase2PixelTopology
);SiPixelRawToClusterCUDA
in two branches to account for digis already being there for Phase2;gpuCalibPixel
pixelCPEforGPU::CommonParams
to includemaxModuleStride
andnumberOfLaddersInBarrel
to have them propagated around being different for Phase1 and Phase2;pixelCPEforGPU::DetParams
to includenRowsRoc
,nColsRoc
,nRows
,nCols
andnumPixsInModule
being not constant among modules for Phase2;isUpgrade_
flag or template all around;PR validation:
Attaching in the first comment a validation run via cms-patatrack/patatrack-validation on a P100 at T2@Bari.
Local tracker validation for Run3 samples (comparison
12_2_0_pre2
vs this PR for CPU/GPU):Local tracker validation for Phase2 samples (comparison legacy reco from
12_2_0_pre2
vs this PR for CPU/GPU):A simple customization function to run the new local reco on top of a generic wf here. This may be tested, e.g., on top of
38634.1
workflow (onstep3
).This will conflict with #36215 and #36176. As soon as those are merged a fix will be committed here. In a following PR the modifications to Pixel Tracks reco will be addressed.
cc: @mtosi @vmariani @mmusich @VinInn
(probably you will be notified anyway)