Add Owlv2; Add option to use owlvit / owlv2's image preprocessing procedure (the roi_align in current implementation processes images differently and results in distribution shifts and subpar performance) - #23
Open
xuanlinli17 wants to merge 8 commits into
Conversation
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
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.
no_roi_align) in theOwlPredictorclass ofnanoowl/owl_predictor.pyto use the original owlvit / owlv2 implementation's image preprocessing procedure. From my debugging, I find that the current nanoowl repo preprocesses images differently from the original owlvit / owlv2 implementations due to the use of "roi_align". This causes the larger models (base-16, large-14) to perform subpar compared to the original owlvit / owlv2. Passing inno_roi_align=Truefixes this issue.nms_threshold) to use non-maximal suppression bounding box filtering