OrcaDose
Sign in

Skills

The techniques that get re-explained in every write-up that uses them — a ring for fall-off, a tuning structure for a hotspot. Written once and quotable, so a notebook can point at one instead and stay about its own case.

In the order you would do them, not in alphabetical order. Read top to bottom and you have read a planning workflow.

1 · Know what your machine can do

Before any of the rest. The same case is a different problem on a robot, a ring, a fan beam and a gimbal, and half the arguments about planning are really arguments about which machine somebody is standing at.

2 · Contour, and check the contours

Everything downstream is computed on these. A structure that is wrong here is wrong in every number the plan is later judged by, and no optimizer setting recovers it.

3 · Build the structures the optimizer needs

Not anatomy — the shells, rings and subtractions that exist only so there is something to put an objective on. The optimizer cannot be asked about a region nobody drew.

4 · Decide where the beam comes from

Geometry first, and geometry is the one thing an objective cannot undo. A direction you never removed is a direction the optimizer has to spend dose fighting.

5 · Enter the objectives, in an order

The part every write-up leaves out. Which goal went in first, what it cost, and what was changed next — the sequence is the reasoning, and only the planner has it.

6 · Read what came out

Before changing anything. Most re-optimizations are spent undoing a change made for the wrong reason, and the DVH usually said so first.

Everything else

Added since this ordering was last revised, and not yet placed in it.