-
Notifications
You must be signed in to change notification settings - Fork 173
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
refactor: Set defaults for GreedyAmbiguityResolution
#2784
refactor: Set defaults for GreedyAmbiguityResolution
#2784
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2784 +/- ##
=======================================
Coverage 48.71% 48.71%
=======================================
Files 479 479
Lines 27898 27898
Branches 13177 13177
=======================================
Hits 13591 13591
Misses 4763 4763
Partials 9544 9544 ☔ View full report in Codecov by Sentry. |
📊: Physics performance monitoring for 56bbf68physmon summary
|
Invalidated by push of 7e0cd1b
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.
Does this have a measurable runtime impact?
…iwand/acts into refactor-greedy-ambi-solver-defaults
Invalidated by push of 56bbf68
I didn't check but it should not be too bad. The problem is that we were left with a bunch of duplicates in busy events because the number of iterations also determines how many tracks will be removed at max which was not sufficient in the ttbar case |
1000
iterations is not sufficient for some of our common workflows. I also set the parameter explicitly in the python examples