-
Notifications
You must be signed in to change notification settings - Fork 10
Add jet parents retrieval #121
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
Conversation
Add parent_jets() accessor, that returns a jet's parents or nothing. Export this method. "Promote" has_parents() to ClusterSequence source file and ensure it works with both jet types. Add tests for parent jet retrieval, in case where a jet has parents and also when it doesn't.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #121 +/- ##
==========================================
+ Coverage 73.49% 73.73% +0.23%
==========================================
Files 18 18
Lines 1249 1245 -4
==========================================
Hits 918 918
+ Misses 331 327 -4 ☔ View full report in Codecov by Sentry. |
Ensure that jet and ClusterSequence have the same type Co-authored-by: Mateusz Jakub Fila <[email protected]>
Use the new get_parents() function
Normally a jet has either two parents or none (initial particle). However, for a beam merge step there is only one parent, so protect mass_drop and soft_drop by checking both parents are valid.
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.
LGTM
Thanks for the useful review @m-fila ! |
Add
parent_jets()
accessor, that returns a jet's parents or nothing. Export this method."Promote"Removehas_parents
to ClusterSequence source file and ensure it works with both jet types (or anyFourMomentum
).has_parents
as unneededAdd tests for parent jet retrieval, in case where a jet has parents and also when it doesn't.
Closes #100