Slava Krutelyov

> 60% of the tracks used for BPH analysis have this problem. simple rounding will likely have a smaller impact than what's done in miniAOD with the cov parameterization

About the number of bit for px,py,pz, if I take a naive linear propagation of the relative uncertainty, for the W mass we'll need 1e-6 precision (0.1 MeV); so, it's...

> From what I can tell, this is what the MiniAOD is using ... > which (I think) stores 11 bits of the mantissa and 4 bits of the exponent...

> @slava77 how would you like me to proceed on this question you asked? > > > please add compression details wrt reco::Track generalTracks branch; the other kind of tracks...

> @slava77 how does reconstruction want to proceed? I can only respond for tracking (`reco::Tracks` part of this issue). We could start with no-PU validation using samples of the same...

code-checks to trigger removal of the reco signature

it would be nice to see the line numbers in the crash reports, especially in cases if it's hard to access the node with a specific architecture (ARM)

@VinInn @fwyzard what do `atomicAdd_block` , `__syncthreads` and such translate to without CUDA for the CPU code in https://github.com/cms-sw/cmssw/blob/ca8617f5f5948dde414285b6b72a2aad132fd6d1/RecoPixelVertexing/PixelVertexFinding/plugins/gpuFitVertices.h#L66-L76 ? hopefully the `atomicAdd_block` is still an increment

> > Will that be acceptable? > > No. > > If the warning is something that needs to be followed up, then people should look into it within one-two...

> Hi, I'm checking the reco differences and they are minimal. I see a ~1% decrease in the number of general tracks, maybe it is expected, could you please confirm...