Trying to figure out the best strategy for computer set up to record this race. I had to put it down in TR as a 12 hour event since I’m swapping laps with a teammate over 24 hours. Obviously that’s not our strategy, but I’m not sure how to account for the hour+ break I’ll have in between laps. Do you pause your device? Start a new event every lap? Any tips?
In the past I have done it both ways - start a new “ride” each lap as well as just keep the device running but lap it each time. Lapping it each time but running a continuous activity makes for a more interesting combined file by the end, which I appreciate.
Ultimately if you are actually stopping the device recording after each lap and restarting for the next, there should be little to no difference in the total metrics.
1 Like
I went with stopping and starting again when not on the track. Mostly because I didn’t trust my device to survive otherwise (older model with less than perfect battery). It’s also relatively easy to patch together the fit files of multiple rides into one if desired. Especially if the alternative is to not have data because the device failed. Unless you need to start up very quick and don’t want to wait for whatever time GPS needs to fully connect again, stoping and starting is definitely the safer bet and should allow for faster charging in-between.
Of course, if you have a relatively new, solar powered device or ride with a powerbank, my arguments are easily dismissed
1 Like
I have always just started a new event for every lap. Seems better for battery life and then you have a bunch of really clean files for comparison.
Also seems less complicated to me, and at 2:00am I just need the simplest answer. Turn on device, press start and stop.
1 Like