-
Notifications
You must be signed in to change notification settings - Fork 36
Handle CAF making when Pandora runs after the NuGraph2 filter #616
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
base: develop
Are you sure you want to change the base?
Changes from all commits
351d379
762e6ed
78a0667
d5d32a0
cf283cb
98a4654
612ae6a
55812bc
d483222
deb9088
6aa4a4c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think the changes made here are overall consistent with my expectations and I didn't find anything specific explicitly wrong. I have just a couple of clarifications to ask:
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also I wonder why slice vertex-related info are highlighted as a change with respect to the previous code version but I hope it's an accident (this info should not have been changed based on nu-graph correct?)
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, the interpretation is correct. The flag was needed because the slices in the two paths change a bit, but we want NuGraph2 variables in the CAF regardless of the chosen reconstruction path. The NuGraph2 PID is very strong, and can be helpful for selections even if the reconstruction is the classic Pandora one. Some of the variables I added rely on the vertex information (e.g., the HIP tagger on the three planes), so I had to move some things here and there to make sure, e.g., that the vertex information was retrieved before I needed it. Effectively, there are no changes for other CAF variables. |
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 guess I have only a curiosity on how the TPC wire (tick) distance default is decided (a presentation to look at/a short explanation would suffice for me thanks!)
Uh oh!
There was an error while loading. Please reload this page.
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.
The default values sort of hint at a "3 cm" range around the reconstructed vertex. How such a distance translates onto the different wire planes is not obvious, so I just set default numbers that kind of make sense. They can be tuned at the FHiCL level, if anyone wants to play with the variables. An application of this is to reject HIP activity at the vertex, for example for selecting 1e0p0π final states; you can find something along these lines here (+ data/MC comparisons): https://sbn-docdb.fnal.gov/cgi-bin/sso/RetrieveFile?docid=45736&filename=EventSelection_20260220.pdf&version=1.