In the hardware-in-the-loop simulator the car drove a loop twice under three lighting
presets, carrying a simulated RealSense infrared pair (SGBM), a planar lidar ring and exact depth. Every source went through
our SLAM; trajectory error (ATE) is measured against the true poses. Our student is in-distribution here: it was fine-tuned
on exact depth rendered in this same yard.
The numbers behind this: per session, the front end, the scale error
True scale, on more seeds and lighting. Giving exact depth
its true scale instead of the per-frame floor-fit scale from camera height cuts the error 6.8× on the original loop
(6.3–7.4× per session; 3.1× for the front end alone). On seven further start seeds, fixed in advance, it is 6.5× (95 % CI 5.5–7.7): 0.620 to 0.094 m,
every seed lower; three seeds excluded (one displaced at spawn, two with blank depth renders). Re-rendered at evening and dusk (the
same drives; exact depth ignores lighting), the true scale lowers the error in every session: evening 6.8× (5.7–8.1) and dusk 6.2× (5.4–7.1). Driven the other way round (each place seen from the opposite
direction; seven of ten seeds valid) it is 6.3× (95 % CI 5.7–6.9), lower in every seed.
Our network against exact depth. Under the same floor-fit scale our network's error over exact
depth's is 0.75× at noon (95 % CI 0.49–1.14, at most 14 % worse), 0.66× at evening (0.57–0.78, lower) and 0.97× at dusk (0.70–1.36, at most 36 % worse), and 0.98× driven the other way (95 % CI 0.68–1.42, at most 42 % worse): never distinguishably worse. For exact depth the bottleneck is the scale; for our network, fitting the scale to exact depth never closes
the gap.
Fitting the scale to exact depth. Fitted per frame (scale and shift) over the whole image, the network's error falls only
1.5× (95 % CI 1.1–2.3; exact depth's falls 6.5×): at noon, on the terrain it was fine-tuned on, it stays 3.2× exact depth's true-scale error (95 % CI 2.4–4.2), at evening and dusk 8.1× (5.6–11.6) and 9.0× (7.8–10.4), driven the other way 7.0× (5.9–8.3). Fitted on the
scan's own rows instead, the network's error stays 5.3× at noon (95 % CI 4.1–6.7), and at evening and dusk the network's own floor fit beats both fits. None of the
three affine scales tried (the floor fit, the two fits to exact depth) closes the gap. The closer fit on the scan's rows (rms
0.09–0.12 m−1, against 0.19–0.23 image-wide) is no better, and at noon and dusk worse, so
this SLAM's error does not track how well the scale fits: beyond any per-frame affine scale tried, what limits it is the network's depth
itself, not its scale (its disparity is also not affine to exact inverse depth, 1/Z).
Smoothing and other scale sources. Smoothing the floor-fit scale in time does not recover the true scale's gain: on exact depth the fit puts a true 2 m at a median
1.07×, and at 1–2 m that error drifts slowly along the route rather than jittering, so a filter cannot remove it (slow drift is one explanation; the fit's distance-dependent bias is another, untested).
Every camera arm except true-scale exact depth is worse than the commands alone. Of the ways to get a correct scale, only
stereo was tested here; an IMU or a metric model is untested.