-
Notifications
You must be signed in to change notification settings - Fork 55
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
Pion branch stores hits with x,y,z outside detector volume #22
Comments
@seamusriordan @yxzhao88 This is something that should be mentioned in the simulation meeting as it has the potential to affect other analyses. We discussed it briefly this morning in the pion detector meeting and it was suggested we should alert others of the issue. I'm not sure yet whether using poststep point is the correct solution (though it is what basic example B2a uses, the first one to introduce hits):
|
Yes, that looks very nice. The use of of prestep was a bad habit of mine. Also I'll note yxzhao88 has moved on to a job at INFN |
Can't reproduce this issue. Probably independent of prestep/poststep, and may have been caused by some transients in my code. Closing for now, but feel free to reopen if anything like this shows up for someone... Verified that master branch has no issues like this for hit.det==28. Prestep point results in getting the entry point to the detector. Poststep point gets the exit point from the detector. There will always be a step point on fGeomBoundary. The important thing is to get the position from the prestep/poststep point that the fGeomBoundary test is done on. That's done correctly in remoll. |
The attached image is pion branch 765d86c with pion generator, type pi-, selecting hits in det 4000 == pion PMT. These are clearly not just hits in the PMT. Reopening... |
Duplicate of closed #127 |
The pion branch stores detectors in the cylindrical disks that act as PMTs. These are only 1 mm thick. However, when running the simulation, hits are created in this detector with a variety of hit.x,y,z values outside the disk. Could this be because we get the x,y,z from the G4Step prestep point? Should we use the poststep point?
Image below should only have hits in the disk shaped region on the right. Hits distributed in the middle and to the left are far outside of the PMT volume.
The text was updated successfully, but these errors were encountered: