The decoder I wrote to parse the STraM .dat files doesn't currently handle the extraction of lap data. What kind of priority should I give to adding that so that lap markers can be plotted somehow?
Is the way that STraM plots lap markers sufficient? What improvements can you think of?
3 comments:
I like the way the laps work in Polar software. When you hover the mouse over the lap mark it will open a new small window with key data about the lap - lap time, lap pace, lap distance. Which is very useful. I would love to see this in the Suunto Training Manager.
As far as priority - I think it is quite useful especially for people that do interval training. On longer tempo runs I do not care much, on bike rides I care only during the regular test protocol, but the most I care about the laps when I do interval training or during the laps swimming (similar to the intervals - I want to know how much time I needed to cover pre-determined distance).
I think a seperate graph of lap times /pace would be nice, as would allow you to quickly see how even your pace/splits were.
Thanks folks. Nick - do you have something specific in mind?
One line per lap with relative time along the X axis for example?
Post a Comment