Jump to content

Talk:Surface code

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Requested move 29 December 2025

[edit]
The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion.

The result of the move request was: moved. Moved as an uncontested request with minimal participation. If there is any objection within a reasonable time frame, please ask me to reopen the discussion; if I am not available, please ask at the technical requests page. (closed by non-admin page mover) Jeffrey34555 (talk) 04:20, 8 January 2026 (UTC)[reply]


Toric codeSurface code – Currently surface code redirects here, but the planar surface code has been studied more than the toric code due to ease of implementation, especially on hardware with limited qubit connectivity, so much that the term "surface code" often means the planar code by default. Many concepts about the toric code are directly applicable to surface codes in general. Bbbbbbbbba (talk) 06:08, 29 December 2025 (UTC) — Relisting. Jeffrey34555 (talk) 05:57, 5 January 2026 (UTC)[reply]

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Image problem

[edit]

File:ToricCodeLattice.png is currently missing a dot representing a qubit at the middle point of the rightmost vertical line. Furthermore, if this image is supposed to represent an entire toric code, each of the edges that "wrap around" should also have a single dot (maybe two half-dots) on it. Could anyone help me fix this? It would be nice to convert the image to a vector format while we are at it, preferably with something like tikz code to facilitate working on it. Bbbbbbbbba (talk) 01:21, 12 January 2026 (UTC)[reply]