OWL-ViT precompute box_bias #29713
Closed
OWL-ViT precompute box_bias #29713
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
…h-owlvit-precompute-box-bias
…h-owlvit-precompute-box-bias
Contributor
Author
|
Also update the OWLv2 model with a similar speed-up. |
Contributor
|
Hi @nvbinh15, thanks for opening this PR! As per the contributing guidelines, we give priority to PRs opened, vs comments on issues. As #29712 was opened first, that will be reviewed before this PR. |
Contributor
|
This issue has been automatically marked as stale because it has not had recent activity. If you think this still needs to be addressed please comment on this thread. Please note that issues that do not follow the contributing guidelines are likely to be ignored. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #26099.
Precompute box_bias at initialization using the number of ViT patches and move it to the correct device at inference.
Appreciate your review @amyeroberts @5hadytru!