Add detection_filter
to predict()
method to allow for user-defined logic
#307
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.
Hey @giswqs...I was interested in being able to have finer-grain control over the filtering of detections, especially during
batch_predict
.Just an idea, but what about adding a callable
detection_filter
arg topredict()
?...which expects a function like:
To then be passed in kwargs down the line...
I've implemented the following above, and seems to work well, but would appreciate hearing other people's perspectives on the API for something like this.