Hello,
I've encountered some strange behavior with the ->GetPosWithRespectToPixel() function for hits. In particular, when a sensor is tilted, I find that the coordinates suggest that a particle has crossed pixel boundaries before the pixel number (with (*hitsCollection)[itr]->GetPixelNbY()) reflects this. Specifically, if I print out the phi-direction coordinate, I'll see it cross from negative to positive (indicating that the MIP is now in a different pixel) but the pixel number is only updated 2 hits later. I think I've tracked this down to a mismatch in src/AllPixTrackerSD.cc. The attached slides contain a little bit more detail. Please advise. Thank you!
Sincerely,
Ben
AllpixMisMatch_09122016.pdf
Hello,
I've encountered some strange behavior with the ->GetPosWithRespectToPixel() function for hits. In particular, when a sensor is tilted, I find that the coordinates suggest that a particle has crossed pixel boundaries before the pixel number (with (*hitsCollection)[itr]->GetPixelNbY()) reflects this. Specifically, if I print out the phi-direction coordinate, I'll see it cross from negative to positive (indicating that the MIP is now in a different pixel) but the pixel number is only updated 2 hits later. I think I've tracked this down to a mismatch in src/AllPixTrackerSD.cc. The attached slides contain a little bit more detail. Please advise. Thank you!
Sincerely,
Ben
AllpixMisMatch_09122016.pdf