<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Spectra-to-Structure and Structure-to-Spectra Inference Across the Periodic Table · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2506.11908/</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/2506.11908/feed.xml" rel="self" type="application/rss+xml" /><item><title>Spectra-to-Structure and Structure-to-Spectra Inference Across the Periodic Table — mentioned by mackeye</title><link>https://news.ycombinator.com/item?id=44966240</link><guid isPermaLink="false">urn:hackerpapers:mention:2506.11908:44966240</guid><pubDate>Wed, 20 Aug 2025 20:44:43 GMT</pubDate><description>&lt;p&gt;&amp;gt; how do you convert a paper into working code? this is something i&amp;#x27;ve found LLMs almost useless at. consider https://arxiv.org/abs/2506.11908 --- the paper explains its proposed methodology pretty well, so i figured this would be a good LLM use case. i tried to get a prototype to run with gemini 2.5 pro, but got nowhere even after a couple of hours, so i wrote it by hand; and i write a fair bit of code with LLMs, but it&amp;#x27;s primarily questions about best practices or simple errors, and i copy/paste from the web interface, which i guess is no longer in vogue. that being said, would cursor excel…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2506.11908/"&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>
