The colours!

I've been working on the training calendar some more and the entries are coloured coded in line with the chart presented in the training summary. There's a session inventory too, again coloured matched detailing key figures from each training session.

The session inventory supports filtering and grouping to help you find what looking for. The two things are not 100% linked up yet, but it's getting there.



In case anyone notices that I'm a very slow runner, that's a bug, or rather I'm not yet converting from meters per second which is the internal data presented by the T6.

Bang for buck

Where do I get the best return (based on energy consumption)? Hopefully this type of chart will answer the question.


(the unlabeled vertical axis is energy consumption (kcal))

At the moment, it's not much of a shocker. Gosh! Lengthy exercise results in more energy usage, but there are a couple of points here which I'll be looking to address.

The points are aggregated time/kcal figures on a daily basis. So each Bike point is actually two sessions (well, most are. Cycle to work, cycle home again). If I break them out into their constituent parts there may be more clustering.

The other option is rather than plotting cumulative energy output, I can output kcal/minute. I don't even have a sample display for that one yet as it requires more effort than I'm prepared to put in on a Friday night. It might not be any more interesting but I won't know until I try it out.

GPS

One of the things I want to add is the ability to attach a GPS session to a work out to record where I've been. I purchased a tiny GPS receiver that arrived yesterday, failed to make it work on the cycle home but got success this morning on a rather dull, route wise run this morning.


Because I was too lazy to calibrate my foot-pod properly when I got it, I'm happy to see that it looks like it's been under reporting distance. (7.24k from POD, 8.44k from the data imported to Live Maps).

I'll need to work out who to display and manipulate the map control (other people have done this so I'm hoping to learn from them) and then overlay standard GPX formatted data.

Local language

Code localization is hard work and Microsoft has my respect for their efforts to support local language, number and symbol preferences (see Sorting it out for all sorts of details on Unicode and non-roman alphabet representation).

With the exception of some menu French gained from cooking and eating over the years, I speak no languages other than English. I've no idea what will become of this project but I'm taking the time to make the string literals that represent titles of graphical elements like menu items, axis descriptions and other labels, dialog headers and so on into formal resource items so that they can be localized later.

Visual Studio could make it easier in the symbolic naming and .Net's xx-yy resource notations aren't all that straight-forward either.

Laps

Do people use the T6 lap function often? Until recently most of my exercise has been of the start-stop variety but I'm doing more running so I'm finding that I am using the lap button more and more.

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?

Weight chart / pie(s) chart?

STrAM lets you edit session properties; you can assign an activity and so on.



I don't use resting HR or feeling but I do use the weight field for record keeping. Each day I weigh myself and use that as the basis. Annoyingly STraM doesn't automatically re-analyse the log if you change the weight and often I forget to.

Do any of you use the weight field? If you do, I guess a chart would be useful. If you don't currently, is it of interest?