-
Notifications
You must be signed in to change notification settings - Fork 35
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?
Conversation
cerati
left a comment
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.
Thanks, overall it looks great -- especially removing the need for the hit mapping makes things much simpler.
The two things I would suggest to change are:
- Avoid erasing elements from vectors. I think it should be much easier to simply add a check that the element is non-null in the Fill*NuGraph method. Or is there another reason for erasing the elements with null nugraph score?
- There is no need to get the NuGraph slices from the event if then we just use
slices(whenUsePandoraAfterNuGraph=true)
|
I have addressed Giuseppe’s comments (with which I agree). I also added more code to fill some new NuGraph2 CAF variables we developed. I opened the corresponding sbnanaobj PR #183. |
This PR adds a mode governed by the
UsePandoraAfterNuGraphFHiCL flag to handle NuGraph2 variables in the CAF maker, when using a second-pass Pandora after filtering noise with NuGraph2, based on work by summer intern Leonardo Lena.This PR also provides code to fill new NuGraph2 slice-level variables in CAF files.
Relevant information about the NuGraph2 chain is provided in icaruscode PR #868.
Associated PRs
Review
Tagging for review @acampani and @PetrilloAtWork as reconstruction and infrastructure experts. Thanks a lot!
Description
Please provide a detailed description of the changes this pull request introduces. If available, also link to a docdb link where the issue/change have been presented on/discussed.