[davidjohnstone]

The training load is based on the exponentially weighted moving average of the normalised work of rides, where the normalised work is a number that shows how "hard" a ride is. A one hour time trial is worth 100, so if you do just that every day for a long time, you'll end up with a long-term stress and short-term stress of 100, and a stress balance of 0. There's a longer explanation over on the blog: http://www.cyclinganalytics.com/blog/2012/06/the-training-lo...

This isn't able to show any weak spots in your stroke because this data is only being recorded once every second. I think you need a Wattbike or similar to show exactly what your pedal stroke looks like. I'm not sure how to work out optimal cadence, but it sounds like something worth thinking about.

Are you talking about when you're using the Strava phone app? I haven't used it, but I'd definitely be in favour of it showing when you're starting segments and doing other smart stuff like that. I'm planning on doing a bit more Strava integration with my site too, starting with getting the Strava segments for a ride.

Thanks for your feedback!

[chocoheadfred]

I've used a computrainer before to capture this data, weak spots in pedaling. Not sure how this technology works though.

Yes, Strava phone app. I don't have the fancy smancy garmins/power meters/etc. Does it show though on a Garmin when you enter a segment if you are running Strava?

[davidjohnstone]

It looks like Computrainers capture more data[1]. I'd love it if power meters on bikes also captured this data.

Nah, us Garmin users don't even have an app on our devices, we just upload our data to their website when we get home (just like it works with my site).

1. http://www.racermateinc.com/spinscan.asp