Quantum error correction can constantly recalibrate a processor - Ars Technica 6%

By John Timmer34%

7/10/2026, 11:02:30 PM

BS Summary: This article contains 28 faulty reasoning types, including Unattributed Quote, Biased Writer Voice, and Confirmation Bias, with Appeal to Authority as the most egregious example at 16.4% saturation with 173 hits. Analysis detected 1,273 faulty-reasoning hits from 1,052 analyzed words, generating a BS Score of 22% and a BS Rank of 6% (20,640 of 21,886 articles). This article is better (less manipulative) than 94.30% of the article peer group.

There are some obvious big picture issues that stand between us and useful quantum computing. 
Issues like whether we can make enough high-quality hardware qubits to connect into the error-corrected logical qubits we need, and how we generate the states needed to perform universal computation on those logical qubits. 
But there are also many less prominent challenges that will need to be solved before we can perform calculations. 
One of those challenges, which only affects some types of hardware, is calibration. 
For devices we manufacture, like superconducting qubits, there are always subtle variations among individual qubits. 
(This is not true when we use something like an atom to hold the qubit, but the lasers that control them can drift.) 
As a result, this hardware is put through a process called calibration, where we test different frequencies and amplitudes of the microwave pulses that control them to find the combination that produces the lowest error rates, and then save those settings for use in calculations. 
However, you can’t perform the typical calibration process while you’re doing calculations, which means drift becomes an issue for long and complicated algorithms. 
Google, though, has figured out that it’s possible to do calibration using the same data that’s used for error correction. 
Reinforcement learning 
The hardware that Google and a number of other companies rely on are transmons. 
They consist of a loop of superconducting wire connected to a resonator, and they’re controlled by pulses of microwave photons. 
Those pulses are controlled by hardware that is kept outside of the refrigeration, including classical computers and the microwave sources they control. 
This hardware is used to test different combinations of wavelengths and amplitudes during calibration. 
This equipment can also drift from its initial settings due to random factors, such as the hardware heating up as it’s used. 
And that could be an issue for the sorts of complicated algorithms we ultimately intend to run on quantum computers, like those that could crack current encryption. 
Currently, if the system shows signs of drifting away from calibration, Google says that it simply stops the computations and recalibrates. 
However, that is not going to be an option partway through a complicated calculation. 
These computations will be taking place using error-corrected qubits, in which measurements on a subset of the hardware qubits are used to detect and characterize any errors that occur on the ones that hold the data. 
As the Google researchers point out in their paper, some of the errors they’ll detect will be the product of calibration failures: “errors from imperfect calibrations produce detectable syndromes just like all other errors.” 
In theory, we could use the same error detection to identify both random errors and those produced by calibration issues. 
The challenge is telling the two apart. 
The team’s solution? 
Reinforcement learning, in which the computer tries different configurations of the 1,000 or so control parameters it has access to, and scores their effectiveness at limiting errors. 
“We deliberately apply small, simultaneous perturbations to all control parameters during the computation to explore the control space,” the team wrote. 
“These perturbations translate into subtle changes in the statistics of error-detection events.” 
Using that information, the system can infer how adjusting these parameters can minimize certain errors. 
If those errors start to show up, it can make the appropriate adjustments. 
And that can be done in parallel with the error detection and correction system that manages the logical qubit. 
The system was put in charge of two logical qubits hosted on a calibrated system. 
The two were using different error correction schemes (a surface code and a color code). 
These were set in a specific state, and the error-correction system was then used with and without reinforcement-learning-driven corrections. 
Having the system active led to a 20 percent increase in the ability to detect and correct errors in the logical qubits. 
The limitation of this approach is that it works only if the drift keeps the system reasonably close to the state the system was trained in. 
The corrections that might bring things back into alignment from one state might not be effective when the system’s in a significantly different state. 
The solution to this is to constantly re-evaluate the effectiveness of different changes. 
But this has an obvious problem: You can’t simply randomize all the potential control configurations in the middle of a calculation. 
Even with limited variation, the system will necessarily operate outside its optimal error correction. 
So, the question was whether the frequent sub-optimal error correction paid off by keeping drift from causing even larger problems. 
“The favourable resolution of the exploration–exploitation trade-off would mean that the aggregate performance of all sampled policy candidates, most of which are worse than [the optimal one], is still better than the performance without reinforcement learning steering,” the researchers write. 
Performing many simulations with a very small error-corrected qubit showed that the trade-off worked out, provided that drift was slow enough. 
The team showed that it could work in real time with a large error-corrected qubit, in which the reinforcement learning system had control over roughly 40,000 parameters. 
This is clearly not a solution for the present; we can only keep systems operating for long enough to perform relatively short, simple algorithms, so drift isn’t even a concern. 
Ultimately, our intention is to build hardware that can perform the sorts of calculations where issues like this will matter. 
And there’s some value in demonstrating that something we know could be a problem can be dealt with. 
Nature, 2026. 
DOI: 10.1038/s41586-026-10759-2 ( About DOIs ). 
Senior Science Editor 
John is Ars Technica's science editor. 
He has a Bachelor of Arts in Biochemistry from Columbia University, and a Ph.D. in Molecular and Cell Biology from the University of California, Berkeley. 
When physically separated from his keyboard, he tends to seek out a bicycle, or a scenic location for communing with his hiking boots. 
China recovered its first reusable rocket and showed a new way to do it 
Increased drone surveillance of illegal July 4th fireworks led to $100K fine 
Suspecting AI cheating, Ivy League prof ordered an in-person final; scores fell 50% 
Check out the first images of Quest shipwreck 
Study shows how toxic RFK Jr.’s change to measles vaccine is for US toddlers 
Article reasoning-pattern comparisonThis article: 7.8%John Timmer: 4.6%Ars Technica: 2.8%Confirmation Bias7.8%This article: 0.0%John Timmer: 0.2%Ars Technica: 1.2%Anchoring Bias0.0%This article: 1.4%John Timmer: 1.4%Ars Technica: 2.4%Availability Heuristic1.4%This article: 1.2%John Timmer: 0.7%Ars Technica: 1.0%Representativeness Heuristic1.2%This article: 2.0%John Timmer: 0.3%Ars Technica: 0.6%Hindsight Bias2.0%This article: 5.2%John Timmer: 1.5%Ars Technica: 2.1%Overconfidence Bias5.2%This article: 3.2%John Timmer: 2.0%Ars Technica: 3.4%Framing Effect3.2%This article: 2.5%John Timmer: 0.6%Ars Technica: 0.5%Loss Aversion2.5%This article: 0.0%John Timmer: 0.4%Ars Technica: 0.5%Status Quo Bias0.0%This article: 0.0%John Timmer: 0.0%Ars Technica: 0.1%Sunk Cost Effect0.0%This article: 7.6%John Timmer: 2.2%Ars Technica: 4.2%Optimism Bias7.6%This article: 7.7%John Timmer: 3.0%Ars Technica: 1.7%Pessimism Bias7.7%This article: 7.1%John Timmer: 9.5%Ars Technica: 6.2%Negativity Bias7.1%This article: 0.0%John Timmer: 0.6%Ars Technica: 1.2%Self-Serving Bias0.0%This article: 0.0%John Timmer: 0.4%Ars Technica: 0.6%Fundamental Attribution Error0.0%This article: 0.0%John Timmer: 0.2%Ars Technica: 0.1%Actor-Observer Bias0.0%This article: 0.0%John Timmer: 0.5%Ars Technica: 0.6%In-Group Bias0.0%This article: 0.0%John Timmer: 0.4%Ars Technica: 0.2%Out-Group Homogeneity Bias0.0%This article: 4.1%John Timmer: 0.8%Ars Technica: 2.0%Halo Effect4.1%This article: 0.0%John Timmer: 0.3%Ars Technica: 0.1%Horn Effect0.0%This article: 0.0%John Timmer: 0.1%Ars Technica: 0.0%Dunning-Kruger Effect0.0%This article: 0.0%John Timmer: 0.7%Ars Technica: 1.0%Recency Bias0.0%This article: 2.0%John Timmer: 0.4%Ars Technica: 0.3%Primacy Effect2.0%This article: 0.0%John Timmer: 0.1%Ars Technica: 0.1%Blind-Spot Bias0.0%This article: 0.0%John Timmer: 1.8%Ars Technica: 0.5%Ad Hominem0.0%This article: 0.0%John Timmer: 0.7%Ars Technica: 0.2%Straw Man0.0%This article: 16.4%John Timmer: 4.0%Ars Technica: 4.1%Appeal to Authority16.4%This article: 5.4%John Timmer: 1.5%Ars Technica: 1.1%False Dilemma5.4%This article: 1.3%John Timmer: 2.3%Ars Technica: 0.7%Slippery Slope1.3%This article: 0.0%John Timmer: 0.0%Ars Technica: 0.1%Circular Reasoning0.0%This article: 3.4%John Timmer: 7.1%Ars Technica: 3.8%Hasty Generalization3.4%This article: 0.3%John Timmer: 0.3%Ars Technica: 0.2%Red Herring0.3%This article: 0.0%John Timmer: 0.8%Ars Technica: 0.6%Bandwagon0.0%This article: 3.9%John Timmer: 4.9%Ars Technica: 2.7%Appeal to Emotion3.9%This article: 1.9%John Timmer: 0.6%Ars Technica: 0.6%Begging the Question1.9%This article: 2.4%John Timmer: 0.8%Ars Technica: 2.3%Post Hoc (False Cause)2.4%This article: 0.0%John Timmer: 1.3%Ars Technica: 0.2%Tu Quoque0.0%This article: 0.0%John Timmer: 1.2%Ars Technica: 0.5%Burden of Proof0.0%This article: 1.7%John Timmer: 0.2%Ars Technica: 0.2%Appeal to Nature1.7%This article: 0.0%John Timmer: 0.1%Ars Technica: 0.2%Composition/Division0.0%This article: 0.0%John Timmer: 1.1%Ars Technica: 1.5%Anecdotal0.0%This article: 2.2%John Timmer: 0.1%Ars Technica: 0.1%No True Scotsman2.2%This article: 4.8%John Timmer: 1.0%Ars Technica: 1.7%Ambiguity (Equivocation)4.8%This article: 0.0%John Timmer: 0.0%Ars Technica: 0.0%Gambler’s Fallacy0.0%This article: 1.9%John Timmer: 0.1%Ars Technica: 0.1%Middle Ground1.9%This article: 0.0%John Timmer: 0.2%Ars Technica: 0.1%Personal Incredulity0.0%This article: 0.0%John Timmer: 0.2%Ars Technica: 0.1%Special Pleading0.0%This article: 0.0%John Timmer: 0.6%Ars Technica: 0.1%Genetic Fallacy0.0%This article: 12.7%John Timmer: 3.0%Ars Technica: 1.5%Unattributed Quote12.7%This article: 0.2%John Timmer: 1.3%Ars Technica: 1.0%Quote-first Misdirection0.2%This article: 9.7%John Timmer: 9.4%Ars Technica: 4.5%Biased Writer Voice9.7%This article: 0.0%John Timmer: 5.0%Ars Technica: 1.0%Indoctrination0.0%This article: 0.0%John Timmer: 1.5%Ars Technica: 0.7%Politically Left Leaning Bias0.0%This article: 0.0%John Timmer: 0.1%Ars Technica: 0.2%Politically Right Leaning Bias0.0%This article: 0.8%John Timmer: 0.5%Ars Technica: 1.3%Attempt to Sell a Product or S…0.8%

1052 words analyzed.

Speakers

1speaker7.1%attributed speech977writer words
Voice mapSelect a segment to jump to its words
Writer's voice • 11 words • 0.0% coverageWriter's voice • 15 words • 100.0% coverageWriter's voice • 34 words • 0.0% coverageWriter's voice • 19 words • 100.0% coverageWriter's voice • 13 words • 0.0% coverageWriter's voice • 15 words • 0.0% coverageWriter's voice • 23 words • 0.0% coverageWriter's voice • 45 words • 0.0% coverageWriter's voice • 23 words • 0.0% coverageGoogle • 20 words • 0.0% coverageWriter's voice • 2 words • 100.0% coverageWriter's voice • 14 words • 0.0% coverageWriter's voice • 20 words • 0.0% coverageWriter's voice • 22 words • 0.0% coverageWriter's voice • 14 words • 0.0% coverageWriter's voice • 22 words • 0.0% coverageWriter's voice • 27 words • 0.0% coverageGoogle • 21 words • 0.0% coverageWriter's voice • 14 words • 0.0% coverageWriter's voice • 36 words • 0.0% coverageGoogle • 34 words • 100.0% coverageWriter's voice • 20 words • 0.0% coverageWriter's voice • 7 words • 0.0% coverageWriter's voice • 3 words • 100.0% coverageWriter's voice • 27 words • 0.0% coverageWriter's voice • 21 words • 100.0% coverageWriter's voice • 12 words • 100.0% coverageWriter's voice • 15 words • 0.0% coverageWriter's voice • 13 words • 0.0% coverageWriter's voice • 19 words • 0.0% coverageWriter's voice • 15 words • 0.0% coverageWriter's voice • 15 words • 0.0% coverageWriter's voice • 19 words • 0.0% coverageWriter's voice • 22 words • 0.0% coverageWriter's voice • 26 words • 0.0% coverageWriter's voice • 24 words • 0.0% coverageWriter's voice • 13 words • 0.0% coverageWriter's voice • 21 words • 100.0% coverageWriter's voice • 14 words • 0.0% coverageWriter's voice • 20 words • 0.0% coverageWriter's voice • 40 words • 100.0% coverageWriter's voice • 21 words • 0.0% coverageWriter's voice • 27 words • 100.0% coverageWriter's voice • 30 words • 100.0% coverageWriter's voice • 20 words • 0.0% coverageWriter's voice • 18 words • 0.0% coverageWriter's voice • 2 words • 0.0% coverageWriter's voice • 6 words • 0.0% coverageWriter's voice • 3 words • 0.0% coverageWriter's voice • 6 words • 0.0% coverageWriter's voice • 25 words • 0.0% coverageWriter's voice • 23 words • 0.0% coverageWriter's voice • 14 words • 0.0% coverageWriter's voice • 12 words • 0.0% coverageWriter's voice • 13 words • 0.0% coverageWriter's voice • 8 words • 100.0% coverageWriter's voice • 14 words • 100.0% coverage
Selected voice

Google

100%flagged-word coverage
75 attributed words100% of attributed speech66% writer coverage
0%25.0%50.0%Unattributed Quote+35.1 ptsWriter: 10.2%Google: 45.3%45.3%Biased Writer Voice-10.4 ptsWriter: 10.4%Google: 0.0%0.0%Attempt to Sell a Product -0.8 ptsWriter: 0.8%Google: 0.0%0.0%Quote-first Misdirection-0.2 ptsWriter: 0.2%Google: 0.0%0.0%

Attribution is sentence-level. Pattern percentages are calculated only from words assigned to that voice.

Loading…
Loading…
Loading…
Loading…

Analysis

Hover over highlighted words in the article to view the associated bias or fallacy analysis.