FLASH Radiotherapy and the Use of Radiation Dosimeters
Bibliographic record
Abstract
Radiotherapy (RT) using ultra-high dose rate (UHDR) radiation, known as FLASH RT, has shown promising results in reducing normal tissue toxicity while maintaining tumor control. However, implementing FLASH RT in clinical settings presents technical challenges, including limited depth penetration and complex treatment planning. Monte Carlo (MC) simulation is a valuable tool for dose calculation in RT and has been investigated for optimizing FLASH RT. Various MC codes, such as EGSnrc, DOSXYZnrc, and Geant4, have been used to simulate dose distributions and optimize treatment plans. Accurate dosimetry is essential for FLASH RT, and radiation detectors play a crucial role in measuring dose delivery. Solid-state detectors, including diamond detectors such as microDiamond, have demonstrated linear responses and good agreement with reference detectors in UHDR and ultra-high dose per pulse (UHDPP) ranges. Ionization chambers are commonly used for dose measurement, and advancements have been made to address their response nonlinearities at UHDPP. Studies have proposed new calculation methods and empirical models for ion recombination in ionization chambers to improve their accuracy in FLASH RT. Additionally, strip-segmented ionization chamber arrays have shown potential for the experimental measurement of dose rate distribution in proton pencil beam scanning. Radiochromic films, such as GafchromicTM EBT3, have been used for absolute dose measurement and to validate MC simulation results in high-energy X-rays, triggering the FLASH effect. These films have been utilized to characterize ionization chambers and measure off-axis and depth dose distributions in FLASH RT. In conclusion, MC simulation provides accurate dose calculation and optimization for FLASH RT, while radiation detectors, including diamond detectors, ionization chambers, and radiochromic films, offer valuable tools for dosimetry in UHDR environments. Further research is needed to refine treatment planning techniques and improve detector performance to facilitate the widespread implementation of FLASH RT, potentially revolutionizing cancer treatment.
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.001 | 0.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.001 |
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".