The Commute by Magic Watch

[Andrew G]

Got myself one of those magic watches as they were flogging them off cheap (Forerunner 205).

Finally got round to working out how it works and tried it out on the commute today, clever bit of kit .

I knew it was fairly lumpy but...

Elevation Gain : 1,047m
Distance : 44km
A very un-retro graph
[img]http://trail.motionbased.com/trail/chart/get.mb?xy.domain=totalDistance&xy.ranges=elevation&xy.histogram=false&xy.legendVisible=false&xy.primaryRangeAxisVisible=true&xy.secondaryRangeAxisVisible=true&xy.rangeTitlesVisible=true&xy.domainAxisVisible=true&xy.plotForegroundOpacity=0.75&episodePk.pkValue=5898845&xy.plotForegroundOpacity=0.75&xy.autoFit=true&xy.width=340&xy.height=227[/img]

[Marky Mark]

You'll be able you pragramme the video next Andrew. Are you going to go all tecky on us now??

[Andrew G]

No don't worry, got it for holidays and "different" rides mainly. Just testing it so I could use it on Saturday and then for the Dragon and know how it worked.

[Ivor]

but what's the power....

[Sylv]

You sure about the 1,047m thing Andrew - 3,435ft?
Looking at graph would have said more like 2,000ft?
Am probably wrong ... if so it's a good training commute!

[Andrew G]

Nope not sure at all Sylv, just the numbers it spat out at me. Distance was correct though and average speed seemed right. We'll see what it says after the Dragon, maybe it gets a little bit confused if you raise your arm as it's a watch not clipped to the bars - mind you my arls aren't that long.

[Snoop Doug]

[quote="Andrew G"]Nope not sure at all Sylv, just the numbers it spat out at me. Distance was correct though and average speed seemed right. We'll see what it says after the Dragon, maybe it gets a little bit confused if you raise your arm as it's a watch not clipped to the bars - mind you my arms aren't that long.

[Andrew G]

Don't know why it mas in miles and feet either as I had it set on kms/metres
Think you're right Sylv, having switched it to kms/metres and "bigged it". Commute probably not the best test as my arm keeps getting lifted to signal at junctions and hold on to traffic lights/railings etc when stopped - There's a lot of sharp pointy bits in the middle which is when I'd have been in the City so flat roads but me holding on to things at traffic lights, signalling, "waving" at drivers - A huge spike at the time I'd have been next to the River Thames . The number is probably "correct" but includes numerous false readings, probably also have got confused with all the secret squirrel surveillance stuff in the City keeping an eye on me incase I grow a beard and get a tan or something.

The Grimpeurs Challenge thing on Saturday (below) gave an elevation gain of 1,861 metres which sounds a lot more likely than 1,000 going to work and back . It's also much cleaner without loads of funny spikes - not in a city .
[img]http://trail.motionbased.com/trail/chart/get.mb?xy.domain=totalDistance&xy.ranges=elevation&xy.histogram=false&xy.legendVisible=false&xy.primaryRangeAxisVisible=true&xy.secondaryRangeAxisVisible=true&xy.rangeTitlesVisible=true&xy.domainAxisVisible=true&xy.plotForegroundOpacity=0.75&episodePk.pkValue=5905367&xy.plotForegroundOpacity=0.75&xy.autoFit=true&xy.width=340&xy.height=227[/img]

Looks like it'll take me a while yet to learn how to use the video MM .

[Elliot M]

you want an algorithm to throw out impossible altitude changes, say anything which implies over 50% grade

then maybe smooth using a rolling average over 3 points

ivor?

[Jon H]

Andrew, you must have very long arms for a short fella; that big spike in the middle is about 150ft !

[Andrew G]

Not that long Jon, sort of confirms my City screwing it up theory as they middle bit is all pan flat but the graph's up and down like a fiddler's elbow.