20260915 - Thin the white outline on tracker scope markers - #88
Merged
Merged
Conversation
blah2 runs a 0.5 s CPI, so a track held across the page's default 15-minute window lays down 1,800 markers. Where a target flies tangentially the range and Doppler barely move, those markers stack, and a 1.2 px white ring is wide enough that each point overpaints the fill of the one before it: the track reads as a white smear rather than a coloured line. 0.5 px still separates neighbouring points where they are sparse, which is what the ring is there for, without bleaching the dense case. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One line, in the Tracker page's track trace:
Why
blah2 runs a 0.5 s CPI and the page's default window is 900 s, so a track held for the full window lays down 1,800 markers. A tangential pass barely moves in either axis, so those markers stack inside about a kilometre of bistatic range and a few Hz of Doppler. At a 1.2 px ring each point overpaints the fill of the one before it and the track reads as a white smear instead of a coloured line. Two tracks running close together do the same to each other.
0.5 px keeps points countable where they are sparse, which is the reason the ring exists, without bleaching the dense case. Dropping the ring entirely was the other option and is worse: the track fuses into one solid stroke and the per-detection reading is lost.
Verification
Judged against a rig that redraws the same scope twice from one dataset, matching the page exactly: Plotly 3.7.0,
scattergl, size-7 markers on thehsl(h,58%,42%)wheel, thergba(0,0,0,0.25)joining line, the detections layer at size 4 / opacity 0.4 beneath, and 1,800 track points at the real cadence. Only the outline width differs between the two panels.pytest tests/test_tracker_routes.pypasses (13 tests). Not yet deployed to a node: jonathan-node-1 is mid-test and a template change needs a GUI restart to take effect, since Flask debug is off there and Jinja caches templates.🤖 Generated with Claude Code