Changes

'''Update: Lumo has gone bankrupt and as far as I can see their sensors are effectively bricked. Unlike BSX, who made some of their software open source, Lumo has just disappeared. '''Lumo Run is a [[Running Sensors| Running Sensor]] that mounts on the rear waistband of your shorts. It measures a number of aspects of your [[Running Form]], including [[Cadence]], [[Vertical Osculation Oscillation]] (bounce), breakingbraking, pelvic drop, and pelvic twist. Lumo uses a 9-axis sensor, which is a 3-axis accelerometer plus a 3-axis gyroscope and a 3-axis magnetometer allowing it to sense movement far better than sensors that rely on the accelerometer alone. It's this 9-axis sensor that allows some of the potentially interesting metrics to be gathered.

* '''Vertical Oscillation'''. This is how much your torso moves up and down with each stride. It is generally believed that less Vertical Oscillation is a better, but I suspect that this is an oversimplification. Some are part of a runner's vertical movement [[Vertical Oscillation]] is likely to be elastic in nature (consider a bouncing rubber ball), some of the vertical motion will be while the runner is airborne (ballistic), and some of the vertical motion is the deceleration as the runner lands. So , it seems likely to me that excessive vertical oscillation is bad, but it's a tricky to know what excessive is likely to be, or how to correct it. The measure of Vertical Oscillation (which Lumo terms "bounce") is similar to other devices and I will perform some verification using an objective measure in the future. Lumo recommend less than 3"/7.6cm of bounce. * '''BreakingBraking'''. Lumo measures how much your torso slows up on each stride, and recommends that it should be under 1.65 feet/second. I'll be curious to see how this compares to [[RunScribe]]'s foot breaking braking and [[Wahoo TICKR Run]]'s smoothness. (I'm not sure why this is measured as a velocity rather than acceleration.)

Lumo Run is available for <jfs id="B01K22SOYE" noreferb="true"/> which is a comparable price for a 9-axis device. (Early versions of the Lumo have a fault where light causes a bad battery reading, so you have to insert it into its holder the other way round.)

* Other than Cadence which is more easily and effectively gathered using cheaper technology, there's not much evidence that any of the other metrics are valuable to a runner. While reducing "breakingbraking" may seem intuitively a good thing, I'd like to see some research to back this up. * Unfortunately, you not only have to run with your smartphone for The Lumo to work, but there's app has no display of any of the data in real time, not even Cadence. However, you don't have to run with your phone as the app will synchronize with the sensor when you finished. I've found the detection of when you start and stop your runs without the phone seems to work reasonably well.* The measure of Vertical Oscillation (which Lumo terms "bounce") is similar to other devices and I will perform some verification using an objective measure in the future. Lumo recommend less than 3"/7.6cm of bounce. * You have to wait until after your run to get summary data, and there are no graphs of how the metrics changed over the course of the run though you can see the metrics for each split. The split is 1 mile for metric runs with the phone and 5 minutes for runs without the phone, which is not very granular. * There are some audio "coaching" messages, but I found those both annoying and useless. These audio messages are no substitute for real time data. * There's no option to export the data for analysis or importing into other tools. * There's also no "treadmill mode"; web interface, so you can use it only view your data on your mobile phone. * Lumo finally added a "treadmillmode" to their app, but so it disables GPS is still used on your phone, which is less than ideal.