8,153
edits
Changes
no edit summary
* There are a few graphs that are available but these are rather small and tricky to interpret. They show "pace vs. cadence", "pace vs. stride length", "pace vs. stance time", "pace vs. runficiency", plus a graph of Foot Strike, Rate of Impact, and Leg Angle.
* Data can be exported as an excel spreadsheet with one row per run. This makes it far easier to analyze your data.
|- valign="top"
|[[File:MilestonePod 1.png|none|thumb|200px|Summary data from a run]]
|[[File:MilestonePod 6.png|none|thumb|200px|A sample of the graphs in the app.]]
|}
=Support This Site=
{{BuyAmazon|AZID=B01JLHCRFS |AZN=MilestonePod}}
=Limitations=
There are a number of limitations to the MilestonePod, though it should be noted that similar limitations occur in [[Running Sensors]] costing many times as much.
=Testing Milestone Pod=
I've tested a number of the metrics for the Milestone Pod, and I'll continue testing against other systems.
* '''Distance'''. Because I tested Milestone is not with the beta firmware using the same methodology I use for GPS devices and found it remarkably accurate. ** The beta firmware version allows the MilestonePod to act as a GPS device, standard Bluetooth footpod. I found this works with all the watches I can't perform my statistical analysis have that support Bluetooth Footpods ([[Polar V800]], [[Polar M400]], and [[Suunto Ambit3]].) ** I do for [[GPS Accuracy| tested the accuracy]]and when calibrated it's more accurate than any GPS watch. However, my informal testing suggests that Milestone can be quite accurateThe details of the beta are at the [http://www.milestonepod.com/blog/now-beta-pod-metrics-real-time/ milestone blog].
** The placement of the pod on the laces seems to be important. The pod should be placed over the arch of the foot, which is typically the second or third crossing of the laces (counting from near the toes.) This seems to give the pod a stable position, as wobbling our bouncing will cause problems.
** The pod requires calibration. If you place it badly and don't calibrate, the error can be as much as 25%, though if it's well placed I've typically seen errors of 6-8%. ** Radical changes of footstrike[[Foot Strike]], from heelstrike heel strike to forefoot can result in greater errors, though I've normally only seen this when I've also not placed the pod in the right place. (It took me a while to realize placement was important.)
** Milestone will work out when your run starts and stops, but you can confuse it if you take breaks in the middle of a run.
* '''Cadence '''seems accurate when compared with other systems and verifying with a metronome. Note that walking breaks might impact your reading.
* '''Ground Contact Time '''is surprisingly accurate; I found it to be better than the far more expensive [[RunScribe]]. I validated this using High Speed Video.