-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
SOTA claims vs leaderboards mismalignment #40
Comments
They are much slower than 5 FPS on GPU Tesla V100, and they are not Real-time.
There are |
@AlexeyAB Great answer! I can see the significant value proposition of this implementation now :)
to
bonus question: |
Real-time is 30 FPS or higher. YOLOv7 surpasses not only real-time detectors from 30 to 160 FPS, but also non-real-time detectors in the range from 4 to 30 FPS.
Page 11: https://arxiv.org/pdf/2207.02696.pdf |
@AlexeyAB it includes generally applicable innovations that improve accuracy, such as: his library makes the integration and selection of optimizations passes easy. It is a tragedy that those innovations are generally ignored by all despite their huge potential in increasing SOTA for free, in key tasks. |
If you will train your own model on your custom dataset, you will get higher accuracy for YOLOv7 than for YOLOR. And YOLOv7 is faster. |
What is the definition that you use to define a detector as real-time or not? I saw a lot of authors mentioning it on their works, but no definition at all... |
AlexeyAB commented on Jul 10, 2022:
So, real-time is 30FPS or higher. |
@WongKinYiu @AlexeyAB
Hi friendly pings
Weird claim when you actually rank #20 on COCO
If we exclude all models with extra training data you still rank #11.
the #1 without extra data is Dual-Swin-L(HTC, multi-scale), with 60.1 box AP
with extra data it is DINO(Swim-L,multi-scale) with 63.3 box AP
The text was updated successfully, but these errors were encountered: