Automatically interpreting qPCR Ct values: what a model trained on 41,770 amplification curves shows
A Chinese team trained machine-learning models on 41,770 qPCR amplification curves from four routine diagnostic assays to learn what a "normal" Ct value looks like and flag abnormal amplifications automatically. On a single instrument, XGBoost matches the machine’s Ct to within 0.04 cycles; transferred to another instrument without recalibration, it drifts to a 2.62-cycle error and wrongly flags nearly a quarter of samples. The work is honest about its limits, but its "ground truth" is the machine’s, not the patient’s — and neither code nor data are public.
The context
Quantitative PCR (qPCR) is the silent engine of molecular diagnostics: it detects SARS-CoV-2, respiratory viruses or hand-foot-mouth disease virus in laboratories worldwide. Its key output is the Ct value (cycle threshold): the number of amplification cycles needed for the fluorescent signal to cross a detection threshold. The more target the sample contains, the fewer cycles are needed, so the lower the Ct. It is a proxy for viral load.
The known catch is that Ct is not a universal quantity. The same sample can yield a markedly different Ct depending on the reagent kit, amplification chemistry, instrument or operator. Comparing Ct values across assays or instruments is therefore treacherous. Existing safeguards — the MIQE guidelines, technical replicates, manual curve inspection — are sound but do not scale: in a high-throughput lab, no one can eyeball tens of thousands of curves. The few published machine-learning approaches mostly tried to predict Ct curve by curve, for a single assay. This paper reframes the problem: rather than "computing" a Ct, learn from a large body of past data what normal amplification behaviour looks like, and flag what departs from it. The authors call this a consensus problem.
The method
The authors assemble 41,770 amplification curves from four routine assays: hand-foot-mouth disease, a multiplex respiratory panel (six pathogens), and two COVID-19 assays based on distinct commercial kits (Maccura and Liferiver) with different primers and chemistries. The data come from two instruments: the SLAN-96S (all four assays) and the Gentier 96R (an independent COVID-19 set). Each curve is summarised by 45 features describing amplification dynamics and signal. Feature normalisation is computed on the training data only and then applied to the test data, to avoid information leakage.
Three models are compared on the Ct-prediction task: XGBoost (an ensemble method that combines many decision trees, progressively correcting their errors), a recurrent neural network (RNN) and a multilayer perceptron (MLP). Performance is measured by mean absolute error (MAE — the average gap, in cycles, between predicted and instrument-reported values) and RMSE. Crucially, the authors introduce a deviation metric, |ΔCt|: the absolute difference between the model-predicted Ct and the instrument-reported Ct. A large |ΔCt| flags a curve that does not behave like the historical "consensus." Three scenarios are tested: within-instrument validation, generalisation to other assays, and transfer to another instrument. Samples with no amplification are assigned a Ct of 40, per diagnostic reporting convention.
The results
On a single instrument with abundant data (Maccura COVID-19 assay on the SLAN-96S, 26,820 samples, 6,704 held out for testing), XGBoost tracks the instrument very closely: MAE of 0.0419 cycles, stable across three random seeds. Only 1.48% of samples deviate by more than 0.5 cycles, and 0.34% by more than one cycle. The MLP does markedly worse (MAE 0.17–0.26) and the RNN is unstable across seeds. Boosted decision trees thus model these curves better than neural networks, given identical features.
For cross-assay generalisation on the same instrument, the "pooled" model (trained on all four assays) holds up better than the single-assay model: on out-of-domain assays (respiratory panel, Liferiver COVID-19, hand-foot-mouth), it produces fewer large deviations. Exposure to varied amplification profiles reduces overfitting to the quirks of a single assay.
The verdict comes when the instrument changes. Applied as is to the Maccura COVID-19 set generated on the Gentier 96R (2,864 samples), without recalibration, the model collapses: MAE of 2.62 cycles, with 24.58% of samples deviating by more than 3 cycles. The authors show this is a systematic offset, likely tied to each instrument’s optical sensitivity, not random noise. In concrete terms: out of 1,000 curves analysed on the same instrument, about fifteen would be flagged beyond half a cycle and three beyond one cycle; but out of 1,000 curves from a different instrument, nearly 246 would be wrongly marked "abnormal" — a flood of false alarms that would make the tool unusable without recalibration.
What is good
Scale and a foothold in reality. 41,770 curves from four routine assays and two commercial COVID-19 kits with distinct chemistries is no toy dataset: it is real, heterogeneous laboratory data that reflects operating conditions — precisely the kind of material that machine-learning work in biology often lacks.
An evaluation that does not hide the failure. The authors could have stopped at the 0.04-cycle MAE and headlined near-perfection. Instead they explicitly test transfer between instruments, report the collapse, and analyse it as a systematic offset. Normalisation computed on the training set only, and repetition over three random seeds, reflect genuine methodological care.
A useful reframing. Thinking of quality control as anomaly detection against a data consensus, rather than curve-by-curve Ct computation, is a fertile idea. Positioned as an objective "second opinion" to triage curves needing review in high-throughput labs — complementing, not replacing, staff — it addresses a real operational bottleneck.
What is less good
A circular reference, and a leakage risk. This is the central limit. The model’s "ground truth" is the Ct reported by the instrument itself. So the model does not learn real viral load or any clinical truth: it learns to reproduce the machine’s algorithm. The 0.0419 MAE measures fidelity to the instrument, not correctness. Worse, the 45 features are extracted from the very curve the instrument used to compute its Ct — predicting Ct from variables that encode it is almost re-deriving it arithmetically. This is a textbook case of potential data leakage: the near-perfect within-instrument result is partly tautological.
A massive platform bias, on a narrow ecosystem. Only two instruments, a single cross-instrument transfer test, and reagents from the same Chinese industrial ecosystem. The learned "consensus of normality" turns out to be instrument-specific: deployed elsewhere, it mistakes perfectly normal curves for anomalies (24.58% beyond 3 cycles). It is a population bias transposed to hardware — the claimed generalisation stops at the boundary of the training instrument.
Unquantified anomaly detection, and total opacity. The core application — flagging dubious curves — is never evaluated by a sensitivity or specificity: only an informal retrospective look at |ΔCt| > 3 cases, with no denominator. The hand-foot-mouth assay has just 90 samples, too few to conclude. Finally, neither code nor data are public, citing commercial confidentiality and a Chinese patent filed by the authors (ZL 202411108830.6); several of them work for a commercial lab-automation company, and funding is declared as "none." Zero reproducibility, a clear conflict of interest.
What it changes
For the research community, the "quality control = consensus anomaly detection" reframing is worth pursuing, but it calls for exactly what is missing here: multi-vendor, multi-country data, a ground truth independent of the instrument, and public datasets to compare methods. As long as the reference remains the machine’s Ct, one is optimising a copy, not a measurement.
For laboratories, nothing is deployable as is: the tool is closed and locked to one instrument. The idea of automatically triaging curves to review via |ΔCt| could ease the manual-inspection burden in very-high-throughput centres, but only after instrument-specific recalibration — which the paper acknowledges and defers to future work.
For patients and the public, this is a piece of invisible infrastructure. Better qPCR quality control means, in the long run, fewer mis-reported viral loads and fewer false alarms — but this work changes nothing about a diagnosis today. It is a laboratory quality-control tool, not a diagnostic test, and one should resist any reading that turns it into "an AI that reads PCRs."
Further reading
The preprint "A data-driven consensus framework for Ct interpretation in real-world multi-assay qPCR diagnostics" (Wang et al., medRxiv, 2026, DOI 10.64898/2026.06.11.26355491) is open access under CC-BY. It has not been peer reviewed. Code and data are not public. For the reference framework on qPCR quality control, see the MIQE 2.0 guidelines (Bustin et al., 2025).