REVIEW 2 cited by
Shortest Route to Non-Abelian Topological Order on a Quantum Processor
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
abstract
A highly coveted goal is to realize emergent non-Abelian gauge theories and their anyonic excitations, which encode decoherence-free quantum information. While measurements in quantum devices provide new hope for scalably preparing such long-range entangled states, existing protocols using the experimentally established ingredients of a finite-depth circuit and a single round of measurement produce only Abelian states. Surprisingly, we show there exists a broad family of non-Abelian states -- namely those with a Lagrangian subgroup -- which can be created using these same minimal ingredients, bypassing the need for new resources such as feed-forward. To illustrate that this provides realistic protocols, we show how $D_4$ non-Abelian topological order can be realized, e.g., on Google's quantum processors using a depth-11 circuit and a single layer of measurements. Our work opens the way towards the realization and manipulation of non-Abelian topological orders, and highlights counter-intuitive features of the complexity of non-Abelian phases.
Forward citations
Cited by 2 Pith papers
-
Notes on (-2)-form symmetries
Introduces (-2)-form symmetries that modify the SymTFT action to relate QFTs differing by anomaly data or non-invertible symmetry associators, illustrated in 2D-4D models, fusion categories, club-sandwich RG flows, an...
-
Non-Clifford gates between stabilizer codes via non-Abelian topological order
A protocol uses the non-Abelian S3 quantum double as an intermediate to implement a controlled charge-conjugation (CC) gate between qubit and qutrit surface codes.
Discussion (0). Continue with ORCID to comment.