Thanks, bitingduck, for the split timer idea.
I have a UI with two buttons that a observer will tap as each rider crosses the start/finish line.
The back-end arrays have this data in them. I had it write out the Rider, Rider's Lap, Split time, Lap time, Lap Avg Speed, and Lap Avg Cadence. I have to flesh out the latter two values later this week. I'll need gear and track length as inputs, but that's not hard.
Rider 2: Lap 1: Split: 24.8002330064774 | Lap: 24.8002330064774 | AVGSPD: 0.0 | AVGCAD: 0
Rider 1: Lap 1: Split: 25.5000630021095 | Lap: 25.5000610351562 | AVGSPD: 0.0 | AVGCAD: 0
Rider 2: Lap 2: Split: 40.7292090058327 | Lap: 15.9289730191231 | AVGSPD: 0.0 | AVGCAD: 0
Rider 1: Lap 2: Split: 41.4492390155792 | Lap: 15.9491750001907 | AVGSPD: 0.0 | AVGCAD: 0
Rider 1: Lap 3: Split: 49.3584740161896 | Lap: 7.90923100709915 | AVGSPD: 0.0 | AVGCAD: 0
Rider 2: Lap 3: Split: 50.1787070035934 | Lap: 9.44949597120285 | AVGSPD: 0.0 | AVGCAD: 0
Rider 1: Lap 4: Split: 57.8990510106087 | Lap: 8.54057198762894 | AVGSPD: 0.0 | AVGCAD: 0
Rider 2: Lap 4: Split: 58.7780510187149 | Lap: 8.59934103488922 | AVGSPD: 0.0 | AVGCAD: 0
Rider 1: Lap 5: Split: 66.0887719988823 | Lap: 8.18971699476242 | AVGSPD: 0.0 | AVGCAD: 0
Rider 2: Lap 5: Split: 68.9882999658585 | Lap: 10.2102480530739 | AVGSPD: 0.0 | AVGCAD: 0
Rider 1: Lap 6: Split: 75.0880590081215 | Lap: 8.99928295612335 | AVGSPD: 0.0 | AVGCAD: 0
Rider 2: Lap 6: Split: 78.8683729767799 | Lap: 9.88006800413132 | AVGSPD: 0.0 | AVGCAD: 0
As you can see in this 6 lap race, Rider 2 went out hot but rider 1 caught him on lap 3 and continued on to win.
I'll make a much more user friendly output. But, I'm happy to have the buttons logging as expected
