Analysis of RapidArc optimization strategies using objective function values and dose‐volume histograms
Bibliographic record
Abstract
RapidArc is a novel treatment planning and delivery system that has recently been made available for clinical use. Included within the Eclipse treatment planning system are a number of different optimization strategies that can be employed to improve the quality of the final treatment plan. The purpose of this study is to systematically assess three categories of strategies for four phantoms, and then apply proven strategies to clinical head and neck cases. Four phantoms were created within Eclipse with varying shapes and locations for the planning target volumes and organs at risk. A baseline optimization consisting of a single 359.8 degrees arc with collimator at 45 degrees was applied to all phantoms. Three categories of strategies were assessed and compared to the baseline strategy. They include changing the initialization parameters, increasing the total number of control points, and increasing the total optimization time. Optimization log files were extracted from the treatment planning system along with final dose-volume histograms for plan assessment. Treatment plans were also generated for four head and neck patients to determine whether the results for phantom plans can be extended to clinical plans. The strategies that resulted in a significant difference from baseline were: changing the maximum leaf speed prior to optimization ( p < 0.05), increasing the total number of segments by adding an arc ( p < 0.05), and increasing the total optimization time by either continuing the optimization ( p < 0.01) or adding time to the optimization by pausing the optimization ( p < 0.01). The reductions in objective function values correlated with improvements in the dose-volume histogram (DVH). The addition of arcs and pausing strategies were applied to head and neck cancer cases, which demonstrated similar benefits with respect to the final objective function value and DVH. Analysis of the optimization log files is a useful way to intercompare treatment plans that have the same dose-volume objectives and importance values. The results for clinical head and neck plans were consistent with phantom plans.
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.002 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| 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".