One body's path, in universe coordinates, starting at where it is now.
devtools/src/orbitPaths.ts:40Members
addressreadonly
anchorreadonly
depthreadonly
How deep in the moon hierarchy: 1 for a planet, 2 for a moon.
kindreadonly
What is on this orbit, so a host can decide whether the trace is context.
A planetarium draws a subject's siblings to show where it sits. That was
unambiguous while a star's children were eight planets; with fifty-nine
dwarf planets, asteroids and comets in Sol it is a cage of a hundred and
twenty-nine lines
across the frame, and Bennu is somewhere behind it. kind is what lets a
host draw the worlds and leave the rubble out.
namereadonly
parentreadonly
The primary's frame, and where it was when this trace was built.
Together they are what lets a host keep a trace correct without rebuilding it. The shape of the curve is fixed in the primary's frame; only the anchor moves, so re-hanging it is one vector difference for the whole path rather than a fresh period of Kepler solves. That matters: rebuilding every trace in a system costs a few milliseconds, which is a visible hitch at 60 Hz and would happen on every frame of time warp.
pointsreadonly
Closed: the last point is one full period on, which is the first again.
radiusreadonly
The body's radius, so a host can place each point the way it places the
body itself. It matters more than it looks: render compression keys off an
object's own radius, so a path placed as a radius-zero point is drawn at a
completely different depth from the planet it belongs to — six times
nearer, at Jupiter's range. See placement.ts.