feat: 🚀 add force_postprocess_type option to get_sliced_prediction for improved control over postprocessing#1346
Merged
Merged
Conversation
…r improved control over postprocessing Signed-off-by: Onuralp SEZER <thunderbirdtr@gmail.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Related Discussion: #1291
PR Images
Main Branch - (before changes images or force_postprocess_type=True case)
@majar5c could you also check results
@fcakyon I made this changes to give control people can have more bbox (depend case they might wanna change that but based on discussion link I understand it happens because of bbox covering larger area but change to True of course generate a lot more bbox as a result as well.