<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>xYOLO: A Model For Real-Time Object Detection In Humanoid Soccer On Low-End Hardware · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1910.03159/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1910.03159/feed.xml" rel="self" type="application/rss+xml" /><item><title>xYOLO: A Model For Real-Time Object Detection In Humanoid Soccer On Low-End Hardware — mentioned by bArray</title><link>https://news.ycombinator.com/item?id=23486200</link><guid isPermaLink="false">urn:hackerpapers:mention:1910.03159:23486200</guid><pubDate>Thu, 11 Jun 2020 07:46:51 GMT</pubDate><description>&lt;p&gt;This is why I have so much doubt. To claim it&amp;#x27;s better in any meaningful way you need to show it on the same framework, varied datasets, varied input sizes and you should be able to use it in your detection problem and also see some benefits from the previous version. &amp;gt; SIZE: YOLOv5 is about 88% smaller than YOLOv4 (27 MB vs 244 MB) Is that a benefit of Darknet vs TF, YOLOv4 vs YOLOv5, or did you win the NN lottery [1]? &amp;gt; SPEED: YOLOv5 is about 180% faster than YOLOv4 (140 FPS vs 50 FPS) Again, where does this improvement come from? &amp;gt; ACCURACY: YOLOv5 is roughly as accurate as YOLOv4 on the…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1910.03159/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CV</category></item></channel></rss>
