-
Notifications
You must be signed in to change notification settings - Fork 577
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
RTDETR implementation #940
Conversation
Amazing contribution @edugzlez ! If you could also include some tests for RTDETR (you can check the yolov8 tests), we would gladly merge your PR 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unittests needed
c3986f1
to
f04e446
Compare
Very interested in RT-DETR support, please complete this PR |
@edugzlez Can you add the commits on this PR edugzlez#1 and we can merge this PR. Moreover, about removing device placement on |
RTDETR unit tests added, unused imports removed.
Sorry @devrimcavusoglu for the delay. I've already accepted the PR and refreshed the branch. Thank you |
Thank you @edugzlez, I mentioned 1 more issue in the comment that changing the device behavior in |
@edugzlez Hi, how could I start testing ultralytics' SAHI implementation for RTDETR? since it is not yet incorporated into the library when installing it with pip |
@edugzlez Thank you for the amazing contribution. 🎉 |
Thank you! @edugzlez |
I have included a basic wrapper to use RTDETR (which is implemented in the ultralytics library).
RTDETR: https://docs.ultralytics.com/models/rtdetr/
I had to change the behavior of the
device
parameter because it was not responding correctly. In this case, I pass it directly to the ultralytics prediction method.I have included the demo and the download functions of the base model.