The newest explained scan, or with ?scans=N the newest N scans as a window.
GET/api/fusion/explain
The newest scan of a coalesced window is the LAST scan the tracker stepped.
A batch is cut into scans in time order and every positionless return goes
in the first (dome-core/src/fusion/scan.rs), so a sensor reporting below
the fastest source's rate is never in the newest scan: on the simulator that
scan holds the two autopilot telemetry plots and a coast for the intruder,
every window. A reader that draws from a hold window asks for one.
Request
Responses
- 200
- 404
the tracker's newest explained scan; with scans=N, a window of the newest N scans oldest first. The newest scan of a coalesced window is the last scan stepped, which is a coast for any sensor reporting below the fastest source's rate, so a reader folding a hold window asks for scans
no scan has been explained since the pipeline last reset