Development and clinical implementation of eclipse scripting‐based automated patient‐specific collision avoidance software
Bibliographic record
Abstract
PURPOSE: Increased use of Linac-based stereotactic radiosurgery (SRS), which requires highly noncoplanar gantry trajectories, necessitates the development of efficient and accurate methods of collision detection during the treatment planning process. This work outlines the development and clinical implementation of a patient-specific computed tomography (CT) contour-based solution that utilizes Eclipse Scripting to ensure maximum integration with clinical workflow. METHODS: The collision detection application uses triangle mesh structures of the gantry and couch, in addition to the body contour of the patient taken during CT simulation, to virtually simulate patient treatments. Collision detection is performed using Binary Tree Hierarchy detection methods. Algorithm accuracy was first validated for simple cuboidal geometry using a calibration phantom and then extended to an anthropomorphic phantom simulation by comparing the measured minimum distance between structures to the predicted minimum distance for all allowable orientations. The collision space was tested at couch angles every 15° from 90 to 270 with the gantry incremented by 5° through the maximum trajectory. Receiver operating characteristic curve analysis was used to assess algorithm sensitivity and accuracy for predicting collision events. Following extensive validation, the application was implemented clinically for all SRS patients. RESULTS: The application was able to predict minimum distances between structures to within 3 cm. A safety margin of 1.5 cm was sufficient to achieve 100% sensitivity for all test cases. Accuracy obtained was 94.2% with the 5 cm clinical safety margin with 100% true positive collision detection. A total of 88 noncoplanar SRS patients have been currently tested using the application with one collision detected and no undetected collisions occurring. The average time for collision testing per patient was 2 min 58 s. CONCLUSIONS: A collision detection application utilizing patient CT contours was developed and successfully clinically implemented. This application allows collisions to be detected early during the planning process, avoiding patient delays and unnecessary resource utilization if detected during delivery.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.000 | 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.001 |
| Insufficient payload (model declined to judge) | 0.000 | 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 teacher head, 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".