Reading a hard constraint against coverage in Varian Eclipse
A disqualifying limit is not one objective among many. Spend everything else before you spend it.
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
| Upper Objective | Volume 0 %, Dose = limit − 5 % |
| Priority | 2× the target objectives |
| Dose grid | 1–1.5 mm for near-max metrics |
An Upper Objective at (0 %, limit − 5 %) with a Priority well above the target objectives, or a Line Objective if the constraint is a dose-volume point rather than a maximum.
Priority in Eclipse is relative, so raising one number only matters against the others. Doubling the constrained structure's priority while leaving the targets alone is the change; raising everything is not.
For a near-max constraint like D0.03cc, remember Eclipse objectives act on the optimizer's dose grid. Calculate the final dose on a fine grid before reading the number you will be judged on — a 2.5 mm grid and a 1 mm grid disagree on a near-max metric.
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