-
Notifications
You must be signed in to change notification settings - Fork 54
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
Reimplimentation of strict thresholding #316
Reimplimentation of strict thresholding #316
Conversation
… and provides the same results as strict_thresholding=False if n_min_threshold is a fixed value
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## RC_v1.5_hotfix #316 +/- ##
==================================================
- Coverage 56.04% 55.84% -0.21%
==================================================
Files 15 15
Lines 3290 3302 +12
==================================================
Hits 1844 1844
- Misses 1446 1458 +12
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
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.
This looks all good to me and I am happy with letting remove_parents
take care of the strict thresholding. Great solution @w-k-jones !
Thanks! In future we should possibly either rename |
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.
This all looks good! I also tested new implementation with own data and it appears to be working as expected. There are no longer tracks detected at a lower minimum value than the dataset.min()
when using threshold='minimum'
and strict_thresholding=True
. It also produces the same number of tracks when using a single nminthreshold
with strict_thresholding=True
and strict_thresholding=False
. Thanks for sorting this out :)
Thanks for the review! I'll merge now |
Fix for the bugs identified in strict thresholding in #314 and #315 . Strict thresholding is now handled in
remove_parents
, by removing features which do not have parents, rather than by modifying the input data.target="minimum"
n_min_threshold
is a fixed value