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

Module position #186

Open
YifanC opened this issue Dec 27, 2023 · 0 comments
Open

Module position #186

YifanC opened this issue Dec 27, 2023 · 0 comments

Comments

@YifanC
Copy link
Collaborator

YifanC commented Dec 27, 2023

For MR5, the module position is set in the detector yaml file for Module0123 sequentially as:

tpc_offsets: # cm # [x (drift), y (vertical), z (beam)]
  - [33.5, 0., 33.5]
  - [33.5, 0., -33.5]
  - [-33.5, 0., 33.5]
  - [-33.5, 0., -33.5]

The center of 2x2 is set to be (0,0,0) in the new geometry (.gdml) used in MR5. As a reference, the module position in MR4 is

tpc_offsets: # cm # [x (drift), y (vertical), z (beam)]
  - [33.5, -268, 1333.5]
  - [33.5, -268, 1266.5]
  - [-33.5, -268, 1333.5]
  - [-33.5, -268, 1266.5]

The module layout in MINOS hall is shown in the picture below which is also linked in this slides
Screenshot 2023-12-27 at 12 37 15 PM

I thought we are extremely lucky that the layout coincides with what we have been using so far. However, this is only valid if we are using a right-hand coordinator system which means when you look along the beam, y is vertically pointing up, x is from right to left, which is also unusual when you look at the detector projections... I am not sure how the coordinate system is set in GENIE and edepsim. Need to double check to ensure we are not randomly flipping the coordinates.

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