Run Timer
Time practice runs with one big button, keep every time in a list you can fix, and send the whole list to the statistics tools. Includes a match clock for full practice matches.
Inputs
Stopped
Space bar starts and stops when you aren't typing in a box.
Each run is added here. Fix or delete a time by editing the list.
Match clock
Counts down a 15 second autonomous period, then 1:45 of driver control, for the Override season.
Ready
Results
Runs timed
—
Average
—
Fastest
—
Slowest
—
How much runs vary (standard deviation)
—
Last run
—
Watch the average settle
Every run you have timed, in the order you took them. The line across is the average of the runs counted so far, and the band around it is how much they vary. Early on the average jumps about with each new run; after a handful it stops moving much, and that is the point at which the number is worth quoting.
How this is calculated
Each run is the time between your two presses, read from the browser's high-resolution clock and shown to a hundredth of a second.
How good is a hand-timed run?
The clock is far more precise than your thumb. A person takes a moment to react to the robot starting and stopping, and that moment changes a little from press to press. When the same person times every run, the delay at the start and the delay at the end largely cancel, and what is left shows up as a little extra run-to-run spread. Swapping timers between runs doesn't cancel, so keep one timer per test.
For anything finer than about a tenth of a second, time it in code instead: log the robot's own timer at the start and end of the routine.
What to do with the list
Send it to Descriptive Stats for an average you can trust and its interval, or to theOutlier Detector if one run looks wrong.
Make a notebook page
Turns this calculation into a dated engineering notebook page: the setup, data, results, figures, working and sources, numbered and cited. You add the goal, the decision and the reflection in your own words, plus photos and sketches. Print it, paste it into Google Docs, or download a Word file or slides.
Sources & assumptions
Match periods. 15 seconds of autonomous and 105 seconds of driver control, from the Overridegame manual. They change with the season in src/data/vex.ts.
Nothing is saved. The list lives on this page. Copy it, or send it to another tool, before you close the tab.
- V5RC Override Game Manual v1.1 (2026-27) — checked August 2026
Where this goes next
Explore further on the full mapWhere the answers on this page can be used, and which tools could have given you the numbers it asks for.
Comes after
Sample-Size PlannerYou are here
Run Timer
Where your answer goes
Descriptive Statssee the average these runs support, and how sure you can be of itbrings your trial results with itOutlier Detectorcheck whether one odd run really sits apart before you drop itbrings your trial results with itAutonomous Time Estimatorcheck a timed routine fits the autonomous perioda number carries across the next question it raises