-
Notifications
You must be signed in to change notification settings - Fork 4
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
Update on S1PatternLikelihood cut #123
Conversation
It was found that previous s1 pattern likelihood is calculated based on observed positions. Because expected PMT hit-patterns are calculated using true interact positions, thus s1 pattern likelihood should also be calculated using field-distortion-corrected positions. In PositionReconstruction minitrees, there is a variable named "s1_pattern_fit_hax", and the cut is reoptimized based on this variable. Details can be seen in https://xe1t-wiki.lngs.infn.it/doku.php?id=xenon:xenon1t:kazama:s1_pattern_cut_sr1#update_2018_jan_4th
Hi Shingo. Linked note Figure U.1. Do you mean 'r' instead of 'z'? I think if we decide to adopt this variable we should rename it 's1_pattern_fit' and keep as default, but that's a hax issue probably. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think should be fine to keep this variable name for now so we don't have to change Extended
treemaker and regenerate all those minitrees.
@skazama Can you please cross-check acceptance on SR0 too?
@coderdj In Fig U.1, it is actually "z" (I divided z-region into two regions). Because field distortion effect in low-z region is more significant than that for top-z region, thus I compared them, but will also check inner and outer region. |
I'm ok to merge, and re-check SR0 acceptance in @sreichard's framework later. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pdeperio we can definitely do that
It was found that previous s1 pattern likelihood is calculated based on observed positions. Because expected PMT hit-patterns are calculated using true interact positions, thus s1 pattern likelihood should also be calculated using field-distortion-corrected positions.
In PositionReconstruction minitrees, there is a variable named "s1_pattern_fit_hax", and the cut is reoptimized based on this variable. Details can be seen in https://xe1t-wiki.lngs.infn.it/doku.php?id=xenon:xenon1t:kazama:s1_pattern_cut_sr1#update_2018_jan_4th