Christophe Vila 252c8fa0d1 Filter start-of-run pace artifacts, use a percentile-based Y scale, round pace ticks to 30s
Samples right as recording starts (before the run itself begins) can compute
an implausible pace like 50+ min/km from a near-zero speed reading; these
are now treated as unknown rather than plotted. The pace/HR domain is also
now built from the 2nd-98th percentile of the actual trace instead of true
min/max, so an occasional stray point (a brief pause, GPS noise) can't
single-handedly stretch the scale and squash the rest of a steady effort --
the target band, which is deliberate data rather than noisy telemetry, is
still always fully included. Pace axis ticks always land on a round
30-second mark (7:30, 8:00, 8:30, ...).
2026-07-19 15:42:49 +02:00
Description
No description provided
1.5 MiB
Languages
Go 72.8%
TypeScript 20.3%
Python 4.7%
CSS 2.1%