Skip to main content

Publish Live Predictive Tracking

Upload structured JSON only. Unstructured text cannot drive Live Predictive Tracking (LPT).

Do not mix AutoResults and AutoResultsLPT

LPT races use @AutoResultsLPT only. Non-LPT races use @AutoResults only. Both listings use the same ##id##. Running both posts two JSON shapes to one results race and breaks the Race Roster API.

Before you start​

  1. Race Roster results race is structured, segments exist, LPT is on — Race Roster setup.
  2. Events, fields, and the JSON listing match those segments — RunScore setup.
  3. Mats feed those events; start is copied to a field — Decoders.
  4. Tools → Online system → RaceRoster, then Online → Login and Online → Select race.

Send once​

Double-click @AutoResultsLPT (for example @AutoResultsLPT.5.M.lst). It:

  1. Recalculates places (@CalcPlaces)
  2. Sets Race Status (@CalcStatus)
  3. Uploads via @ResultsLPTToRR → the 5K, 10K, and Half LPT listings

Or right-click ResultsOnlineLPT5K.rsm, ResultsOnlineLPT10K.rsm, ResultsOnlineLPTHalf.rsm, or @ResultsLPTToRR and choose Send results to online. Status will be stale unless @CalcStatus has just run.

Preview with Output To Editor before the first live send. Confirm column headers match Race Roster segment names and that missing splits are blank, not DNF.

Leave missing times blank

Do not use List DNF on this upload. Empty cell = not yet there. See List DNF.

Auto-run during the race​

Right-click @AutoResultsLPT → Auto Run, or:

Auto Run File       @AutoResultsLPT.5.M.lst
Auto Run Seconds    120

Use the @AutoResultsLPT filename in your race folder. The .5.M suffix is menu placement (group 5, sort M), not run order.

See Auto Run File and Auto Run Seconds.

Run Event To Database (start/splits) on a short interval. Post JSON less often.

Without 0 on the dummy status event, the post only contains people who already crossed a split. Put 0 on every validated bib so STARTING rows go up from gun, with empty times (and estimated finish time if you have it). See RunScore setup.

Verify​

  • RunScore: Online → View results online
  • Race Roster timer dashboard: Edit results — check each column's map type, and that split columns point at the right segment

If tracking is wrong, the usual cause is a name/distance mismatch, List DNF filling cells, or @AutoResults colliding on the same ##id##.