Preparing Hubbard-model ground states by Lindblad simulation may cost ~7.7×10^8 T gates for 36 sites
Researchers estimated how many fault‑tolerant quantum gates are needed to prepare ground states using a Lindblad simulation method that needs only one ancilla qubit. They derived rigorous error bounds with constant prefactors, ran circuit-level simulations for small Hubbard models, and turned those results into full gate counts. Their main concrete estimate: about 7.7 × 10^8 T gates to implement one unit of the required time evolution for a 36‑site fermionic Hubbard model. (T gates are a costly type of quantum gate in fault‑tolerant machines.)
Lindblad dynamics describes quantum evolution that combines the system’s usual coherent motion with dissipative transitions that can remove energy. The single‑ancilla algorithm studied here implements one jump operator per short time step by coupling the system to one ancilla qubit, doing a unitary on the larger register, and then tracing out (discarding) the ancilla. A central design choice is a filter function in the energy domain. This filter suppresses unwanted energy increases and favors transitions that cool the system toward its ground state.
The authors extended earlier asymptotic analyses by computing full prefactors for the scaling of errors and costs. They implemented resource estimation in the Qualtran tool and ran circuit‑level simulations for one‑dimensional Hubbard instances. These simulations let them compare conservative, provable error bounds to empirical error behavior. They also tested different choices of mixing operators and filter functions that respect particle number and spin symmetry, and they converted the resulting gate counts into a fault‑tolerant cost using a Pauli‑based computation model.
Why this matters: preparing low‑energy states is a core subroutine for many quantum algorithms, and the Hubbard model is a leading candidate for early quantum advantage. Giving a concrete fault‑tolerant cost helps set expectations for near‑term hardware and highlights which parts of the algorithm need improvement. It also shows how much difference there can be between rigorous worst‑case bounds and what small‑scale simulations suggest is possible in practice.