Merged
Conversation
samuelbaldwin05
suggested changes
Mar 26, 2026
…nerateNU/StrideTrack into 92-event-comparison-over-time
samuelbaldwin05
suggested changes
Mar 30, 2026
samuelbaldwin05
approved these changes
Apr 3, 2026
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
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.
Summary
Closes # 92
What changed:
Added an event time history visualization that lets coaches see an athlete's times for a single event across multiple completions. in trends section of the toggle on the athletes' profile. Includes a filter bar with an event type dropdown and an amount picker (last N runs or date range) or input a range, and a line chart showing run number vs total time in seconds with a reference line for the best time.
Why:
Coaches needed a way to track performance trends for a specific event over time, rather than viewing individual run analyses in isolation.
Technical decisions worth noting:
Any non-obvious choices and their rationale.
-Elapsed_ms is read directly from the run table since total run time is already stored there
-The chart only fetches data on explicit Apply click rather than reactively, to avoid unnecessary requests while the coach is still making selections
Screenshot
Notes