Performance stability evaluation of atlas-based machine learning radiation therapy treatment planning in prostate cancer
Bibliographic record
Abstract
Atlas-based machine learning (ML) for radiation therapy (RT) treatment planning is effective at tailoring dose distributions to account for unique patient anatomies by selecting the most appropriate patients from the training database (atlases) to inform dose prediction for new patients. However, variations in clinical practice between the training dataset and a new patient to be planned may impact ML performance by confounding atlas selection. In this study, we simulated various contouring practices in prostate cancer RT to investigate the impact of changing input data on atlas-based ML treatment planning. We generated 225 ML plans for nine bespoke contouring protocol scenarios (reduced target margins, modified organ-at-risk (OAR) definitions, and inclusion of optional OARs less represented in the training database) on 25 patient datasets by applying a single, previously trained and validated ML model for prostate cancer followed by dose mimicking to create a final deliverable plan. ML treatment plans for each scenario were compared to base ML treatment plans that followed a contouring protocol consistent with the model training data. ML performance was evaluated based on atlas distance metrics that are calculated during ML dose prediction. There were significant changes between atlases selected for the base ML treatment plans and treatment plans when planning target volume margins were reduced and/or optional OARs were included. The deliverability of ML predicted dose distributions based on gamma analysis between predicted and mimicked final deliverable dose showed significant differences for seven out of eight scenarios compared with the base ML treatment plans. Overall, there were small but statistically significant dosimetric changes in predicted and mimicked dose with addition of optional OAR contours. This work presents a framework for benchmarking and performance monitoring of ML treatment planning algorithms in the context of evolving clinical practices.
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.007 | 0.014 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
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".