With regards to my comment in a thread that got some notice [1]:<p>I incorrectly assumed some relationship between @rocauc and the guys behind YOLOv5 due to some shared language and diagrams, sometimes our brains jump to conclusions - sorry. Unfortunately the edit timed out before I could do much about it.<p>I really appreciate the follow up and the hard work that has gone in since by RoboFlow. This controversy isn't their fault and they really shouldn't get a bad rep for it - in fact their handling of the situation has been good. Maybe some more due diligence, but we're all guilty sometimes. These are the sorts of actions that earn my respect in terms of being an authoritative source.<p>My original comment was quite reactionary, the YOLOv5 guys have done some interesting work. We now have two new interesting approaches based on YOLOv3, I look forward to reading more about the YOLOv5 internals in the future. There was some strangeness around comments being deleted from their GitHub issues once they started getting noticed, but I'll give them the benefit of the doubt.<p>With regards to naming, I really think there needs to be some clear change. YOLOv5 does not build on top of YOLOv4 in any way. I appreciate that the team was "scooped" on the name, but I don't think bumping the version number was the correct approach. It's extremely weird to people coming across this for the first time that YOLOv4 can outperform YOLOv5.<p>There are still some open issues to be addressed with regards to which network performs better and in which use cases, hopefully in the coming weeks it can be worked out.<p>[1] <a href="https://news.ycombinator.com/item?id=23480884" rel="nofollow">https://news.ycombinator.com/item?id=23480884</a>
This post is in response to the discussion[1] on Hacker News this week on the post "YOLOv5: State-of-the-art object detection at 140 FPS" and the objections raised by AlexeyAB on Github[2].<p>The controversy surrounded around two points:<p>• Should the model truly be named YOLOv5?<p>• Are the initial benchmarks Roboflow published accurate and reproducible?<p>We have published more details surrounding our methodology, clear steps and notebooks for reproducing our results, a correction of an unfair comparison we made (re relative inference speed and batch sizes), how we think about the naming controversy and a request for the community to weigh in.<p>[1] <a href="https://news.ycombinator.com/item?id=23478151" rel="nofollow">https://news.ycombinator.com/item?id=23478151</a><p>[2] <a href="https://github.com/AlexeyAB/darknet/issues/5920#issuecomment-642812152" rel="nofollow">https://github.com/AlexeyAB/darknet/issues/5920#issuecomment...</a>