Skip to content
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

Assumptions in pixels_from_track.py #221

Open
jaafar-chakrani opened this issue May 2, 2024 · 0 comments
Open

Assumptions in pixels_from_track.py #221

jaafar-chakrani opened this issue May 2, 2024 · 0 comments

Comments

@jaafar-chakrani
Copy link
Member

The functions in pixels_from_track.py do not use all the information from the yaml geometry files. They only use the pixel_pitch value and assume that all tiles (and pixels) are contiguous. A more general implementation should be using the tile centers as well.

This issue was observed because of a bug in the pixel pitch of the Module 2 geometry file. This geometry file mistakenly used a small pitch such that the number of pixels per tile side times the pitch is smaller than the distance between the tile centers, which leads to gaps (dead region) around each tile. When this issue was found, it was observed that this was not reflected in the output of larnd-sim. See this presentation for a sketch.

#218 addressed this by updating the pixel pitch for Module 2 to the correct value such that there are no gaps around the tile. In this specific case, the existing implementation works. However, for a more general implementation, I think that most of the functions in pixels_from_track.py need to be changed, with a particular care regarding get_neighboring_pixels since gaps between tiles would impact the list of neighboring pixels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant