<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Speed/accuracy trade-offs for modern convolutional object detectors · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1611.10012/</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/1611.10012/feed.xml" rel="self" type="application/rss+xml" /><item><title>Speed/accuracy trade-offs for modern convolutional object detectors — mentioned by mendeza</title><link>https://news.ycombinator.com/item?id=21464315</link><guid isPermaLink="false">urn:hackerpapers:mention:1611.10012:21464315</guid><pubDate>Wed, 06 Nov 2019 16:50:40 GMT</pubDate><description>&lt;p&gt;Also, what is a hard but an important question to figure out is how well are these models are preforming, and will they perform well to your problem. This paper gives a lot of insight into how image size and other factors really impact performance of modern object detection: https://arxiv.org/pdf/1611.10012.pdf. How large or small your object is in your dataset is also something to consider since there is a limit to how small of an object your detector can recognize. Also, I would recommend this repo to better understand how object detection models are evaluated as well…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1611.10012/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CV</category></item><item><title>Speed/accuracy trade-offs for modern convolutional object detectors — mentioned by hedgehog</title><link>https://news.ycombinator.com/item?id=15062359</link><guid isPermaLink="false">urn:hackerpapers:mention:1611.10012:15062359</guid><pubDate>Mon, 21 Aug 2017 06:23:51 GMT</pubDate><description>&lt;p&gt;I missed that the site was updated for YOLO9000, it is very impressive. The Google paper is recent though (July), maybe you&amp;#x27;re thinking of https://arxiv.org/abs/1611.10012? Anyway, what I meant to point out was that there has been a lot of work since on improving the efficiency of the architectures used for feature extraction (Xception, MobileNet, ShuffleNet, NASNet).&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1611.10012/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CV</category></item><item><title>Speed/accuracy trade-offs for modern convolutional object detectors — mentioned by pveierland</title><link>https://news.ycombinator.com/item?id=14575255</link><guid isPermaLink="false">urn:hackerpapers:mention:1611.10012:14575255</guid><pubDate>Sat, 17 Jun 2017 10:51:36 GMT</pubDate><description>&lt;p&gt;The researchers have created a framework for object detection such that one can easily experiment with using different feature extraction networks, separated from the &amp;quot;meta-architecture&amp;quot; such as Faster R-CNN, R-FCN, or SSD, used to handle the object detection task. They compare many models using this framework, described in https://arxiv.org/abs/1611.10012 - and they were able to construct the winning entry of the COCO 2016 detection challenge based on this research.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1611.10012/"&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>
