<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Detecting Adversarial Samples from Artifacts · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1703.00410/</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/1703.00410/feed.xml" rel="self" type="application/rss+xml" /><item><title>Detecting Adversarial Samples from Artifacts — mentioned by tMcGrath</title><link>https://news.ycombinator.com/item?id=15608604</link><guid isPermaLink="false">urn:hackerpapers:mention:1703.00410:15608604</guid><pubDate>Thu, 02 Nov 2017 07:57:57 GMT</pubDate><description>&lt;p&gt;I agree - it&amp;#x27;s a surprising and cool paper. There has been some work done on fooling network ensembles by constructing constructing a Bayesian posterior over weights using dropout [0]. This is an ensemble of weights for the same network, not over different architectures, however. The basic idea here is that most of the time, each member of the ensemble will misclassify the adversarial example in a different way. This means that the posterior predictive distribution for adversarial examples ends up much broader, and you can detect them this way. Surprisingly, even this can be beaten in the…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1703.00410/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>stat.ML</category></item></channel></rss>
