Generalize collection_subcollection branchname patterns for TreeMakerSchema #619
Conversation
This file contains 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
yimuchen
changed the title
|
Could you make a small test for this as well? Like a 10-event treemaker Ntuple to read in and and build the structure of, check for a few branches, etc. |
|
Should be ready once checks are complete. |
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.
In TreeMaker, sub-collections are indicated with branch names
<collection>_<subcollection>and a counting array<collection>_<subcollection>Countsto indicate sub-collection grouping. Originally, a special case was provided for the most commonly used sub-collection (JetsAK8andJetsAK8_subjets). In this pull request, we generalized the branch name parsing to allow for arbitrary sub-collection structures to be extracted.