Run

A run is one recorded pass down a track — a single video file uploaded into Racecraft.

What a run is

• a single, continuous video of one descent
• one file (if your camera records in chunks, stitch them together into one file before upload)
• attached to exactly one track session or one public event
• tagged with the rider in the video (the athlete name), which is not necessarily the account that uploaded it

What a run is not

• not a collection of attempts
• not a multi-lap recording (one lap per run)
• not the analysis itself — the analysis is what Racecraft computes from the run

What you can do with a run

• mark its splits (manually if it's a reference run, by reviewing predictions if it's a target run)
• set it as the reference run for its session or event
• compare it against the reference to see splits, deltas, and the continuous time delta

Run states

A newly uploaded run goes through:

• uploading — the file is being transferred to Racecraft
• processing — Racecraft is building an internal index of the video and, if a reference exists, predicting splits
• ready — the run is available for comparison and on the leaderboard

You can leave the app while a run is processing; it continues in the background.

Run identity vs uploader identity

A run carries an athlete name — the rider in the video. This matters because:

• the leaderboard ranks athletes, not uploader accounts
• a coach uploading footage of three athletes ends up with three runs, each tagged with a different athlete
• a public event leaderboard shows the athlete name, not the uploader's account

If a run is showing under the wrong name, the uploader can edit the athlete tag and any leaderboard or comparison updates accordingly.