CNV Radar: an improved method for somatic copy number alteration characterization in oncology
Bibliographic record
Abstract
BACKGROUND: Cancer associated copy number variation (CNV) events provide important information for identifying patient subgroups and suggesting treatment strategies. Technical and logistical issues, however, make it challenging to accurately detect abnormal copy number events in a cost-effective manner in clinical studies. RESULTS: Here we present CNV Radar, a software tool that utilizes next-generation sequencing read depth information and variant allele frequency patterns, to infer the true copy number status of genes and genomic regions from whole exome sequencing data. Evaluation of CNV Radar in a public multiple myeloma dataset demonstrated that CNV Radar was able to detect a variety of CNVs associated with risk of progression, and we observed > 70% concordance with fluorescence in situ hybridization (FISH) results. Compared to other CNV callers, CNV Radar showed high sensitivity and specificity. Similar results were observed when comparing CNV Radar calls to single nucleotide polymorphism array results from acute myeloid leukemia and prostate cancer datasets available on TCGA. More importantly, CNV Radar demonstrated its utility in the clinical trial setting: in POLLUX and CASTOR, two phase 3 studies in patients with relapsed or refractory multiple myeloma, we observed a high concordance rate with FISH for del17p, a risk defining CNV event (88% in POLLUX and 90% in CASTOR), therefore allowing for efficacy assessments in clinically relevant disease subgroups. Our case studies also showed that CNV Radar is capable of detecting abnormalities such as copy-neutral loss of heterozygosity that elude other approaches. CONCLUSIONS: We demonstrated that CNV Radar is more sensitive than other CNV detection methods, accurately detects clinically important cytogenetic events, and allows for further interrogation of novel disease biology. Overall, CNV Radar exhibited high concordance with standard methods such as FISH, and its success in the POLLUX and CASTOR clinical trials demonstrated its potential utility for informing clinical and therapeutic decisions.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.005 | 0.016 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.007 | 0.002 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.012 | 0.005 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".