HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
PureStateLabs
sqd-spin-referee
Python2026–2026
PureStateLabs / sqd-spin-referee

sqd-spin-referee

Spin audit of SQD/QSCI quantum-chemistry benchmarks on iron–sulfur clusters: the benchmark states aren't the singlet target. Full code, data, and machine-verified reproduction.

2Distinct people
3Mentions
0Explicit recommenders
2GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Spin audit of SQD/QSCI quantum-chemistry benchmarks on iron–sulfur clusters: the benchmark states aren't the singlet target. Full code, data, and machine-verified reproduction.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval3 dated mentions

Observed mentions: 2026-09-17 15:00:37 UTC to 2026-09-19 14:25:25 UTC.

0122026-09-17 15:00:00 UTC to 2026-09-17 18:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsSep 17, 15:002026-09-17 18:00:00 UTC to 2026-09-17 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-17 21:00:00 UTC to 2026-09-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-18 00:00:00 UTC to 2026-09-18 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-18 03:00:00 UTC to 2026-09-18 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-18 06:00:00 UTC to 2026-09-18 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-18 09:00:00 UTC to 2026-09-18 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-18 12:00:00 UTC to 2026-09-18 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 18, 12:002026-09-18 15:00:00 UTC to 2026-09-18 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-18 18:00:00 UTC to 2026-09-18 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-18 21:00:00 UTC to 2026-09-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-19 00:00:00 UTC to 2026-09-19 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-19 03:00:00 UTC to 2026-09-19 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-19 06:00:00 UTC to 2026-09-19 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-19 09:00:00 UTC to 2026-09-19 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-09-19 12:00:00 UTC to 2026-09-19 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 19, 12:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Sep 17, 15:002026-09-17 15:00:00 UTC2026-09-17 18:00:00 UTC202
Sep 17, 18:002026-09-17 18:00:00 UTC2026-09-17 21:00:00 UTC000
Sep 17, 21:002026-09-17 21:00:00 UTC2026-09-18 00:00:00 UTC000
Sep 18, 00:002026-09-18 00:00:00 UTC2026-09-18 03:00:00 UTC000
Sep 18, 03:002026-09-18 03:00:00 UTC2026-09-18 06:00:00 UTC000
Sep 18, 06:002026-09-18 06:00:00 UTC2026-09-18 09:00:00 UTC000
Sep 18, 09:002026-09-18 09:00:00 UTC2026-09-18 12:00:00 UTC000
Sep 18, 12:002026-09-18 12:00:00 UTC2026-09-18 15:00:00 UTC000
Sep 18, 15:002026-09-18 15:00:00 UTC2026-09-18 18:00:00 UTC000
Sep 18, 18:002026-09-18 18:00:00 UTC2026-09-18 21:00:00 UTC000
Sep 18, 21:002026-09-18 21:00:00 UTC2026-09-19 00:00:00 UTC000
Sep 19, 00:002026-09-19 00:00:00 UTC2026-09-19 03:00:00 UTC000
Sep 19, 03:002026-09-19 03:00:00 UTC2026-09-19 06:00:00 UTC000
Sep 19, 06:002026-09-19 06:00:00 UTC2026-09-19 09:00:00 UTC000
Sep 19, 09:002026-09-19 09:00:00 UTC2026-09-19 12:00:00 UTC000
Sep 19, 12:002026-09-19 12:00:00 UTC2026-09-19 15:00:00 UTC101

What Hacker News says

3 sources
Hi again! I like https://github.com/PureStateLabs/sqd-spin-referee/blob/main/... better, the link at the top looks like standard AI generated stuff. Links to the previous posts: * https://news.ycombinator.com/item?id=49097083 (with my old comment) * https://news.ycombinator.com/item?id=49203707 (with an interesting comment by alpineidyll3) > [2Fe-2S] is two high-spin Fe(III) centres, each d5 with S = 5/2. I assumed S = 1/2 but a quick google search says that it may be 1/2 or 5/2. So it makes a lot of sense. > I've submitted the underlying paper here twice before as a Zenodo link, but it didn't get much discussion. There has been too much slop recently, I'm using a modified version of https://math.ucr.edu/home/baez/crackpot.html where you start at +5 instead of -5. Nature and Science adds -1. Zenodo adds +1. As I said before, this post mak
Read the rest
es sense. I'm still not sure it's correct and I didn't miss any detail, but it's not stupid-AI-slop.
In Quantum computing's flagship chemistry results don't say which state they found
gus_massa took the time to actually read this on the last thread and asked three things. That thread locked before I answered, which was my fault for being slow, so here they are. You suggested a short version, two or three pages, that goes straight to the Table 1 results. I wrote one. It's about three pages and it's here: https://github.com/PureStateLabs/sqd-spin-referee/blob/main/... You asked how many states sit near that energy, and whether there's a graphic. Yes. The four lowest roots of the flagship subspace span 12.5 mHa, with the ground gap at 0.285 mHa, and their spin values are S^2 = 1.371, 2.363, 4.738 and 11.590. Climbing the energy ladder climbs the spin ladder. The figure is fig_flagship_s4.png in the archive: panel A is that ladder, B is the residual against S^2, C is the per-root variance. You said you couldn't picture how
Read the rest
S greater than 1 arises, and wondered if it needed extra freedom in the d orbitals. It doesn't. [2Fe-2S] is two high-spin Fe(III) centres, each d5 with S = 5/2. Coupling 5/2 with 5/2 gives total S = 0,1,2,3,4,5, so S^2 runs 0, 2, 6, 12, 20, 30. That's the whole Heisenberg ladder and it's ordinary Clebsch-Gordan, no d-orbital subtlety needed. It also puts your objection on solid ground: 4.7 isn't an exotic value, it sits between the S=1 and S=2 rungs, which is exactly why it reads as a mixture rather than a contaminated singlet. You wrote that some contamination is expected but 4.7 was too much in your opinion. I've since measured the second moment on those states, and the variance is the part that settles it. A spin eigenstate has Var(S^2) = 0. The low-lying roots here run 3.5 to 7.4. They aren't slightly perturbed eigenstates, they're broad mixtures, and a scalar mean of 4.7 understates how broad.
In Quantum computing's flagship chemistry results don't say which state they found
I've submitted the underlying paper here twice before as a Zenodo link, but it didn't get much discussion. I wrote this new post to be more accessible to non-chemists, plus a couple of things have happened since the last time. First, IBM merged two PRs (364 and 366) to qiskit-addon-sqd on Sept 9 after I reported the issue. The docs for the symmetrize_spin option now clarify that it "does not guarantee that the state is an eigenvector of the total spin operator S^2". That covers one of the options. IBM hasn't commented on the paper itself, which I've recently updated to v2 on ChemRxiv. The short version of the post: IBM's released random-input control actually matches their quantum hardware on the smaller iron-sulfur cluster. Also, IBM's flagship paper, the published critique of it, and the RIKEN-IBM Fugaku follow-up all report energies wi
Read the rest
thout stating which spin state those energies belong to. If you rebuild the data for the largest [2Fe-2S] size they published, the lowest state has S^2 = 1.3711. They were aiming for a singlet, which should be 0. You can verify this without relying on my code: Hardware vs random (takes about 10 seconds in a browser, reading IBM's files directly): https://colab.research.google.com/github/PureStateLabs/sqd-s... Spin check (takes about 35 seconds, running PySCF on IBM's public integrals): https://github.com/PureStateLabs/sqd-spin-referee/blob/main/... The last section of the post outlines exactly what would change my mind. If you try to reproduce a number and it doesn't match, let me know here. Paper: https://doi.org/10.26434/chemrxiv.15006382/v2 Data and code: https://doi.org/10.5281/zenodo.21359922
In Quantum computing's flagship chemistry results don't say which state they found

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.