Another picture - Summary Page

Most recent screenshots. This is the training summary page.



Any of the chart tabs that are circled can be reposition (the position's are not yet persistant across sessions but will be) so you could have something like this if you wanted;



The component moving and resizing isn't visually perfect yet. In the picture above the TE scale is scrunched up and the same thing happens sometimes on the date X Axis for charts. On the 'Minutes per day' bar chart the value lables need to appear/disappear depending on density. Conversely, the TE/EPOC chart is perhaps too aggressive in hiding of point lables and the grid lines are too 'heavy'

It's this kind of detail that a) annoys me when it's not present in other software or doesn't work correctly and b) as the developer, takes lots of effort to get right.

The session detail page -



Needs completing (following a re-work to support the 'panel' interface). The session figures need to go on the left, the speed/distance chart needs adding at the bottom and a sample data table needs adding. The chart and table are dead easy, the session figures require more 'manual' labour and will probably take several hours to extract and format nicely. There's a bunch of work to add the necessary buttons to the ribbon GUI and on, and on and on it goes.

All going well I'm hoping to have a first version available by the end of the weekend. I also have a file-server rebuild/upgrade from Windows x86 2003 to 2008 x64 on the list so something's bound to slip. Somewhere my wife would like us to have a social life and we're gearing up to move from Australia back to the UK in 8-10 weeks time. You can imagine the havoc that will bring...

All your laps are belong to us

I extended the test application for laps and as they say here, "It's all good"



Now that I have the data I need to consider how to represent it. On the whole though, I'm fed up with laps (though still have to do my autolap investigations this weekend)

As I mentioned before, there's data inside the lap 'records' that I can't account for. If anyone has any thoughts or suggestion as to what it might be, please let me know.

Simon 1, Lap times 0

Isn't it funny how you complain about something and then make a break-through? So the lap times are done and dusted - mostly. With my data, lap records are 576 bytes long and to be honest there's an awful lot of data in those 576 bytes that I can't account for.

One of my jobs over the weekend will be to use the autolap features of my Bike and Foot Pods to see if that makes a difference, but for now, manual laps work just fine. The one caveat here is that I've only recently started using laps and so far have only tested a few of my files (2.1.x and 2.3.x). I need to expand the test application to parse all the sessions I have for further verification.



I'd like to say thanks to Willem Minten whose document I referred to to shortcut the process of working out the contents of an exported .sdf file. There's an huge difference between the textual .sdf representations and the underlying binary files but it was really helpful to have an additional reference - and one that I hope to be able to refer to over the weekend regarding the lap source types (manual, autolap, inserted via STRaM etc)

If anyone has any special requests regarding the representation of lap data, speak up!

Cheers

Laps

Laps are turning out to be quite a lot more complicated than I thought they'd be. I'm gradually pulling out the data but there seems to be a lot more recorded than is rendered by STraM when looking at the Marks detail.

I'll keep at it over the weekend and see what I can come up with.

File format changes for 2.3

It turns out that the file format changes aren't all that significant. Speed samples appear to have been made optional (before speeds were recorded for each HR sample even if they were zero where you didn't have a connected POD), there's a new container for cadence and temperature samples. There's a new "CorrectedSamples" container which I've not yet had a chance to look at.

There might be some other spot figures that come out of the woodwork, but nothing major. There's a new AVGCADENCE element to go with CADENCESAMPLES.

I've done the initial steps for determining Lap offset data but need to see if there's anything other than a relative time marker present.

v2.3 - Spoke to soon

I've clearly spoken to soon about v2.3. So far it's behaved itself although I'm not sure I agree with the interface changes (I'd prefer to see kcal values on the main tab like before) but usage aside, the raw data format has changed.

I'd expected changes naturally. The sessions now need to maintain data for the new T6 bike POD's cadence data, but I'd expected addition data not changes to the existing structures. At the least they've re-ordered some of the internal sample sets and seemingly made some of them optional.

I'll need to play around a bit with the hex editor for a while to see what's what exactly. It's not all bad news though as I can take this opportunity to re-visit the parsing of lap data that I'd asked about previously and for which I'd had on the to-do list.

Stram 2.3 upgrade

Went without a hitch (unlike 2.2). There doesn't seem to be any changes in data formats so I can plod on with my efforts (which relate to GPX/Virtual Earth) and making all the chart locations flexible.

Tags

I'll be adding note searching (the notes that can be added within STRAM) and tagging. Searching will just examine the STrAM notes but tagging will allow you to free-associate labels to sessions.

Virtual Earth integration

Everyone thinks of Google Maps but the service from Microsoft (Live Maps) is just as, or I personally believe more compelling (The big G still has it on search though). For a Windows developer it's quite easy to get to grips with and they're adding fantastically detailed imaging at the rate of 60TB each time.

Here in Australia ADSL accounts are capped to a set quota per month. Mine's just run out (until tomorrow when the new billing period starts) so I can't easily upload an image but I've got Virtual Earth integration going.

If you have a GPX file associated with a session, you'll be able to add that and view the VE map within the application.

My GPS (tiny, not always clear if it's recording but water-resistant and <$50) is all I've got to test with and frankly the whole XML/GPX thing smells a bit like witchcraft but so far it seems to work. Mine doesn't record altitude but the space shuttle (yep, actual NASA craft) recorded and made altitude data available for pretty much everywhere. The next step will be to associate lat/lon measurements with height in order to plot a better altitude graph.

The colours! - pt2

The colours all match now and the textual summary data, the activity selector and the charts all match.

Selecting/de-selecting activities in the activity selector toggles the appropriate category from the training summary and the calendar. Duration and Kcal figures in in each day entry in the calendar are updated accordingly.

Ideally there would be a video of this but I've not got that sorted out yet.