You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(position-estimation): max-accuracy cutoff + gate circles by Show Accuracy
Two follow-ups addressing oversized estimated-position uncertainty circles.
1. Maximum Acceptable Accuracy setting. New global setting
position_estimation_max_uncertainty_km (0 = no limit). When set, the
scheduler passes it to recomputeAll, which discards any solved estimate
whose uncertainty radius exceeds the ceiling rather than storing it — and
deletes that node's stale estimate so a now-too-uncertain node doesn't keep
an oversized circle. Surfaced in the global Settings → Position Estimation
section with a km input and reflected in the last-run summary (N discarded).
The dominant "huge circle" case is the 5km single-anchor default
(DEFAULT_SINGLE_ANCHOR_KM); a 2-3km cutoff drops those low-confidence guesses.
2. Gate the estimated-position uncertainty circles behind the existing
"Show Accuracy" map toggle (showAccuracyRegions) instead of
"Show Estimated Positions". Now one control governs every accuracy overlay
(precision-bits rectangles + estimated-position circles); the estimated
markers stay under "Show Estimated Positions". Both are required so a circle
never renders without its marker.
Tests: scheduler passes maxUncertaintyKm through (incl. 0=no-limit default);
service discards over-threshold estimates + clears stale rows, keeps within-
threshold, and treats 0 as unlimited.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
'Estimates with an uncertainty radius larger than this are discarded rather than stored, so low-confidence guesses don’t draw huge circles on the map. Set 0 for no limit.')}
0 commit comments