-
Notifications
You must be signed in to change notification settings - Fork 574
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix image_demo bug. #613
Fix image_demo bug. #613
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## dev-1.x #613 +/- ##
==========================================
Coverage ? 80.15%
==========================================
Files ? 95
Lines ? 6415
Branches ? 906
==========================================
Hits ? 5142
Misses ? 976
Partials ? 297 Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@zytx121 Hi, I tried to test this PR, but I seem to run into another bug with https://github.com/open-mmlab/mmrotate/blame/dev-1.x/mmrotate/datasets/transforms/transforms.py#L424
Where the keys in |
Hi @austinmw If you want to use
BTW, |
Hi @zytx121, I trained a v1.0.0rc0 Oriented R-CNN model on SRSDD dataset and exported with mmrotate2torchserve script. I then tried to use the contents of the torchserve export (configs, checkpoint) to run Here's my launch training command:
I'm not sure where |
* update * Update local_visualizer.py
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
To handle tensor bboxes in
RotLocalVisualizer
.reslove #611
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the back-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist