Handle CAF making when Pandora runs after the NuGraph2 filter#616
Handle CAF making when Pandora runs after the NuGraph2 filter#616
Conversation
cerati
left a comment
There was a problem hiding this comment.
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. |
|
Thanks! @cerati do the changes look good to you? |
sbncode/CAFMaker/FillReco.cxx
Outdated
| nHIPHits += 1; | ||
|
|
||
| // shower hits | ||
| if (highestScoreIdx == 2) { |
There was a problem hiding this comment.
Please use the NuGraphCategory enum here (and in similar places I might have missed): https://github.com/SBNSoftware/sbnanaobj/blob/develop/sbnanaobj/StandardRecord/SRNuGraphScore.h#L23
There was a problem hiding this comment.
Right, thanks! Fixed (and sneaked in some more variables)!
|
Looks great! I only left a single comment above |
cerati
left a comment
There was a problem hiding this comment.
Thanks for addressing my comments!
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.