<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Self-Referencing Embedded Strings (SELFIES): A 100% robust molecular string representation · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1905.13741/</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/1905.13741/feed.xml" rel="self" type="application/rss+xml" /><item><title>Self-Referencing Embedded Strings (SELFIES): A 100% robust molecular string representation — mentioned by dekhn</title><link>https://news.ycombinator.com/item?id=45829504</link><guid isPermaLink="false">urn:hackerpapers:mention:1905.13741:45829504</guid><pubDate>Wed, 05 Nov 2025 23:31:54 GMT</pubDate><description>&lt;p&gt;Let me start with an example- some time ago I worked on a VAE that encoded and decoded SMILES strings. The idea is that you should be able to encode a SMILES into an embedding space, do all the normal things you would do in that space, and then convert the resulting embedding vector back to a valid molecule. The VAE is trained with a very large number of valid SMILES strings, typically tokenized at the character level (so &amp;quot;C&amp;quot; is a token, and &amp;quot;Br&amp;quot; is &amp;quot;B&amp;quot; then &amp;quot;r&amp;quot;). I and others have observed that VAEs trained like this produce large number of embedding vectors that do not decode to valid…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1905.13741/"&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>
