Skip to content

Change majority of rock to vac. Add back remaining rock column in front of detectors only #49

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

Merged
merged 6 commits into from
Feb 21, 2025

Conversation

jdkio
Copy link
Contributor

@jdkio jdkio commented Feb 17, 2025

Removes all rocks except those right in front of the detectors, and a little to the sides. It's a bit tall in Y to capture the beam upstream, which is coming down at a 3 degree angle (see below). Working on tech note right now

Here is a comparison of before and after. Green is the rock layer. Note that the shade of green is different because after is using the density change from PR #46, but that isn't present in this PR. Left image is X vs Z, and right is Y vs Z.

Before

image

After

image

Where do neutrinos hit?

We can use the MC to see which interactions make particles which ultimately hit our detectors. To be safe, I defined a region encompases the entire cave (without the prism offshoot or open ceiling):

const TVector3 ND_CAVE_START(-5.0, -6.0, 0.0);
const TVector3 ND_CAVE_END(5.0, 4.0, 30.0);

If any particle (except muons) from a vertex reached that point, the neutrino vertex was included in the distributions below. Muons or secondary particles which include muon parents weren't included because they can travel much further. They are covered by the rockbox technique. This was more about establishing what the size of the anti-fiducial needed to be, including the amount of rocks on the sides. I don't think rockbox expands sideways, just in front
image
One interesting thing is that we get a small amount of events from the ceiling and from the opening left by prism. This makes sense as there's nothing blocking those particles. We also get some from as deep as about 10m underground. The rate is small, but I'm still working out how small. We likely will want to change our flux window

Why not rotate it 3 degrees?

The geometry is setup in a strange way. If we want to rotate and/or move the rock volume then that also rotates the ND geometry because they are nested inside. So I purposely didn't rotate anything once I figured this out

@jdkio jdkio added the enhancement New feature or request label Feb 17, 2025
@jdkio jdkio requested review from ast0815 and alexbooth92 February 17, 2025 20:32
@jdkio
Copy link
Contributor Author

jdkio commented Feb 18, 2025

The tech note is here. It's a work in progress

Copy link
Member

@ast0815 ast0815 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please don't leave any commented-out lines in the code, unless they are there for a good reason. If so, please state that reason as part of the comment. Otherwise remove them. If it is just to keep old configs for posterity, that is what the git history is for.

Copy link
Member

@alexbooth92 alexbooth92 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is looking great Jeffrey, excellent that there is a technote in progress as well.

Unrelated to the code change itself - when you are defining your region "encompassing the entire cave", these number are rough right, even discounting the PRISM offshoot and the funky roof shape as you have noted? I got cavern starting at ~ -30 cm rather than 0 cm in z for example.

@alexbooth92
Copy link
Member

One more thought I just had - will this change propagate to both what we call fiducial and antificudial geometries?

@jdkio
Copy link
Contributor Author

jdkio commented Feb 18, 2025

One more thought I just had - will this change propagate to both what we call fiducial and antificudial geometries?

Yes, WORLDggd.cfg and ND_Hall_Rock.cfg are also used by antifiducial so the change is picked up there too

Unrelated to the code change itself - when you are defining your region "encompassing the entire cave", these number are rough right, even discounting the PRISM offshoot and the funky roof shape as you have noted? I got cavern starting at ~ -30 cm rather than 0 cm in z for example.

Yes, I eyeballed the numbers from some low resolution vtx plots. I probably couldn've done that better. I can update the numbers in the code if you have a better set for X and Y as well

Please don't leave any commented-out lines in the code, unless they are there for a good reason. If so, please state that reason as part of the comment. Otherwise remove them. If it is just to keep old configs for posterity, that is what the git history is for.

Fair point, I removed all comments that didn't have a clear comment explaining them

@jdkio jdkio requested a review from ast0815 February 19, 2025 08:36
@ast0815
Copy link
Member

ast0815 commented Feb 19, 2025

@jdkio @alexbooth92 What is this about the hall not starting at z=0 ? I always heard that the origin of the coordinate system is defined by the position where the beam axis enters the hall. Is that not true? Is this a bug in this PR or in the geometry before?

@jdkio
Copy link
Contributor Author

jdkio commented Feb 20, 2025

What is this about the hall not starting at z=0 ? I always heard that the origin of the coordinate system is defined by the position where the beam axis enters the hall. Is that not true? Is this a bug in this PR or in the geometry before?

I heard the same thing. This PR doesn't move the location of anything, so the z position at the start is the same. It's hard to translate gdml coordinates to real coordinates so it's possible that z=0 is only roughly true. But since that's unrelated, I assume I'm okay to merge @ast0815?

@alexbooth92
Copy link
Member

alexbooth92 commented Feb 20, 2025

@jdkio @alexbooth92 What is this about the hall not starting at z=0 ? I always heard that the origin of the coordinate system is defined by the position where the beam axis enters the hall. Is that not true? Is this a bug in this PR or in the geometry before?

I did the working out on pen and paper to get the corners of volDetEnclosure and found the front face of that volume to be at -30.54 cm. This is in the gdml we've been using for all the recent work. Someone who knows their way around gdml better than me should definitely check though.

@ast0815
Copy link
Member

ast0815 commented Feb 21, 2025

I think those 30 cm might just be the door:

image

I'm happy to merge.

@ast0815 ast0815 merged commit 0d33e49 into master Feb 21, 2025
4 checks passed
@ast0815 ast0815 deleted the jdkio-adjust-rocks branch February 21, 2025 16:17
@alexbooth92
Copy link
Member

I think those 30 cm might just be the door:

image

I'm happy to merge.

Excellent, glad there is an explanation! This is good to know moving forward as we think about the point beyond which we are using the rockbox assumption.

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

Successfully merging this pull request may close these issues.

3 participants