Changing one thing per optimization in Varian Eclipse
Two changes at once and you have learned nothing about either. The chain of versions is the write-up.
Written from documentation and not yet confirmed on a real Varian Eclipse. Control names may differ by version — if you use this system, the skill page has a button to confirm or correct it.
Until somebody does, this page is kept out of search results: naming your console in the title is a claim about it, and an unchecked claim is not one worth advertising.
Controls
| Continue Optimization | only for small weight changes |
| Plan copies | one per structural change |
| MR level | same level when comparing two runs |
Use Continue Optimization deliberately, not by default. Continuing from the previous fluence converges faster but carries the previous run's compromises with it, so a plan built entirely by continuing can end up somewhere a fresh optimization would never have gone.
When you change something structural — an objective removed, a new structure, different geometry — restart from scratch. When you are nudging a priority, continuing is fine.
Keep the plan version, not just the final one. Eclipse makes copying a plan cheap, and a copy per change is what lets you say later which change did what.
Why this works, and where the numbers come from →
The recipe is the console; the skill page is the reasoning and the papers behind it.
Same skill elsewhere:Accuray PrecisionElekta Monaco