Open makortel opened 6 years ago
A new Issue was created by @makortel Matti Kortelainen.
can you please review it and eventually sign/assign? Thanks.
cms-bot commands are listed here
yes, this is due to the difference between cpu and gpu clustering: on cpu the size of a cluster is limited while on gpu is not I investigated the origin and is understood
We discussed with @VinInn, and these are something to be checked after we have the full workflow (on GPU) working.
since it looks like the GPU algorithm behaves "better" than the CPU one, would it make sense to "improve" the latter in the same way ?
It will require a full involvement of Pixel DPG. I suggested to "go public" with them once Run2 is finished and we hope they will have more time to dedicate to software for Run3. (we can of course do it for the limited case of Phase1 pixel in run3 as a specific Raw2Cluster in a similar way I did it for Strip)
I noticed from the log of "ttbar testing 10824.8" with TTbar+PU for #62 as the input the following printouts from the rechits
Link to full log https://fwyzard.web.cern.ch/fwyzard/patatrack/pulls/f24fdf85aaaf7542195d985cacab4640b4ae5efb/RelValTTbar_13-CMSSW_10_2_0_pre3-PU25ns_101X_upgrade2018_realistic_v7-v1/testing-10824.8-step3.log
(the "development" log, i.e. without #62, shows the same printouts)
@VinInn Are the IMPOSSIBLE ones something that should be investigated at some point?