Blip improvements - #92
Open
wforeman wants to merge 4 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR enables new BlipReco improvements introduced in
ubreco(PR 40) so that they can be applied in production.New information added to the ntuple:
elifetimeThe blip categories encoded in
blip_true_categoryare:// -9 = no truth match (data/overlay)
// 0 = truth-matched, but not falling in category
// 1 = primary (n,1p)
// 2 = primary (n,Np)
// 3 = secondary (n,1p)
// 4 = secondary (n,Np)
// 5 = primary (n,gamma)
// 6 = secondary (n,gamma)
// 7 = ncapture gamma
// 8 = mu capture gamma
Since these improvements require new capabilities in
ubreco/BlipReco, the reconstruction has to be re-run (instead of just reading the blip objects already saved to the art::Event from reco2). A FCL configuration was added to enable the re-running of BlipReco, which is now set to true by default. This is very quick and the added computation time is negligible in comparison to all the other analysis tools that are run in the NeutrinoSelection module.The advantage to this is that you only need to re-run the ntuple-generation stage on existing reco2 files to get these improvements.