<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OptNet: Differentiable Optimization as a Layer in Neural Networks · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1703.00443/</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.00443/feed.xml" rel="self" type="application/rss+xml" /><item><title>OptNet: Differentiable Optimization as a Layer in Neural Networks — mentioned by dgacmu</title><link>https://news.ycombinator.com/item?id=15701046</link><guid isPermaLink="false">urn:hackerpapers:mention:1703.00443:15701046</guid><pubDate>Wed, 15 Nov 2017 02:32:29 GMT</pubDate><description>&lt;p&gt;&amp;quot;just a bunch of weights and layers and parameters&amp;quot; -- I think you and the GP are agreeing. That&amp;#x27;s the definition of standard: If the model can be expressed using the currently-blessed set of layer definitions in CoreML, then yes. But if you&amp;#x27;re doing nonstandard stuff with weird control flow behavior, or RNNs that don&amp;#x27;t map into some of the common flavors, then all bets are off. An example: Some of my colleagues put a QP solver in tandem with a DNN, so that the neural network could &amp;#x27;shell out&amp;#x27; to the solver as part of its learning, and learned to solve small sudoku problems from examples…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1703.00443/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item><item><title>OptNet: Differentiable Optimization as a Layer in Neural Networks — mentioned by shriphani</title><link>https://news.ycombinator.com/item?id=14539107</link><guid isPermaLink="false">urn:hackerpapers:mention:1703.00443:14539107</guid><pubDate>Mon, 12 Jun 2017 17:33:47 GMT</pubDate><description>&lt;p&gt;Indeed. A simple solution is to add a differential optimization layer (see Amos et al): https://arxiv.org/abs/1703.00443&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1703.00443/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.LG</category></item></channel></rss>
