fix: wrong grid device w.r.t. output in yolox head#1679
Open
pierrot-lc wants to merge 1 commit intoMegvii-BaseDetection:mainfrom
Open
fix: wrong grid device w.r.t. output in yolox head#1679pierrot-lc wants to merge 1 commit intoMegvii-BaseDetection:mainfrom
pierrot-lc wants to merge 1 commit intoMegvii-BaseDetection:mainfrom
Conversation
|
Pierre Pereira seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
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.
Hi,
When using your amazing repo, I had to fix a small issue where the devices were wrong because some tensor is not using the same device as the model.
The issue can be found here:
A simple fix could be:
I'm not sure why I seem to be the only one having this issue, I hope I'm not using the model the wrong way. Note that my use case is a little bit complicated so I had to implement the training loops myself (that may explain why I faced this issue).
Thank you for your time and have a great day.