Papers › Variational quantum eigensolver for the Heisenberg antiferromagnet on the kagome lattice

Variational quantum eigensolver for the Heisenberg antiferromagnet on the kagome lattice

4 Aug 2021arXiv:2108.02175links table onlyarchive 2025-07-28

Joris Kattemölle, Jasper van Wezel

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

Establishing the nature of the ground state of the Heisenberg antiferromagnet (HAFM) on the kagome lattice is well known to be a prohibitively difficult problem for classical computers. Here, we give a detailed proposal for a Variational Quantum Eigensolver (VQE) intending to solve this physical problem on a quantum computer. At the same time, this VQE constitutes an explicit experimental proposal for showing a useful quantum advantage on Noisy Intermediate-Scale Quantum (NISQ) devices because of its natural hardware compatibility. We classically emulate noiseless and noisy quantum computers with either 2D-grid or all-to-all connectivity and simulate patches of the kagome HAFM of up to 20 sites. In the noiseless case, the ground-state energy, as found by the VQE, approaches the true ground-state energy exponentially as a function of the circuit depth. Furthermore, VQEs for the HAFM on any graph can inherently perform their quantum computations in a decoherence-free subspace that protects against collective longitudinal and collective transversal noise, adding to the noise-resilience of these algorithms. Nevertheless, the extent of the effects of other noise types suggests the need for error mitigation and performance targets alternative to high-fidelity ground-state preparation, even for essentially hardware-native VQEs.

Code

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

7 samples harvested; 0 ran; 0 honoured the contract we drafted; 7 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

Licence: 0 of the 7 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; each sample names its own and says which. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections