Hi chris,
Thanks for trying it out! Glad it (mostly) worked. I'll admit to never even considering the interval workouts when I was writing it (I tend to stick to fixed time or distance), so I'm glad someone thought to check!
I remember I originally was detecting the end of the workout the "right" way, but the last time point would (non-reproducibly) have the distance/time reset to 0/0 which was messing up the graphs, so I switched to the time-based method. You'll want to start playing with the line in the LogProcessor class that looks like this:
Code: Select all
if not results is None and results[0] >= self.__data[-1][0]:
That last check makes sure the time is always increasing, which for interval workouts, isn't true. You'll need to remove that part, add some logic to detect if the time has decreased and if so, add back in the amount of time that elapsed in all previous intervals (unless you want your interval plots to overlap, which might be interesting).
I actually might try to fix this . . . one day when I have time. But you might be able to learn enough Python to get it worked out before then.

Especially if you have experience in another language.
[url=http://www.vishalpatel.net/projects/rowmetrics/]RowMetrics[/url] - a workout performance logger/plotter for Linux