For the most part, the assumptions I've made thus far are pretty sound it would seem.  The precision of the curves is ridiculously good.  The raw data has gone through a couple transformations before rendering, and the "still linear" nature (and the match up with data I observed externally while riding) indicates that my transformations aren't polluting the data to a significant degree.

I've got three more hours of "all by myself" this evening and what to do… what to do….

I've also nailed down a few external system interfaces, primarily Google Maps and Geonames.org for (surprise!) mapping and name lookups respectively.  There's also a lot of framework wiring that has been done, mostly to little benefit so far, but the payoffs of that will starting rolling in now that I'm ready to start working on the UI and business layers a bit more.

Now that might not sound like a big deal, but it really is. I use Fusebox. So all my links are parameterized with XFAs. But XFAs are server-side. Client-side JS (especially static JS in *.js files) can't really access XFAs very well, so URL building is a pain for remoting endpoints and/or hard context switches, But if you're generating the JS server-side….

The specific use case was a login form. I want to "submit" it asynchronously and either display a "denied" message if there's a failure, or forward to the inside of the app if it succeeds. Ordinarily, you'd have to submit the credentials, get some sort of status back from the server, and then use JS to do something with it. Now I can just submit the credentials and let CF emit the JS that I want to execute as a result. I love it.

While I was out, I did manage to get a bit of work done on my app for visualizing the data from my Edge. Not as much as I'd hoped, but more than I'd expected. I've got the MotionBased packet importer all built, along with a couple cleanup routines, and all feeding a database. I also set up a new site, www.gpsracr.com (check my way-hip missing 'e'!!!), to host the app. Currently there isn't much of interest, just a report from processing the import queue, but at least for me, having a home for an app all set up is a huge hurdle to cross. Infrastructure surrounding it is pretty sparse, just deploying as a SVN working copy, but it's adequate.

Still contemplating architecture for the app. Definitely going HTML instead of Flex now that a highly dynamic data entry interface isn't needed, though there will be a few Flex bits where appropriate (like charts). ColdSpring for sure. I'm debating between Fusebox 5.5 and my modified Fusebox 3 for the UI framework. I'm thinking that decision is actually a pretty minor one with the improvements in 5.5 that Sean has made, but I haven't dug in real deeply yet.

First task, which is of rather limited interest, is plotting cadence/speed curves to identify my relative gear ratios and more specifically, the overlap between my large and small chainrings. Most of my riding is pretty flat and I like having relatively large rings, but when I get into big climbs (like the friggin' cliff I went up Saturday) I need some lower gears. Pushing 45 rpm at 5 mph for 15 minutes sucks. So I want to quantify what I've got, and then extrapolate what effect different size rings would have. That's a relatively easy task, so I thought it's make a good first foray into actually using the data.