8,153
edits
Changes
From Fellrnr.com, Running tips
no edit summary
{{DISPLAYTITLE:Stryd footpod review}}
Stryd is one of the most useful and impressive running technologies available. It's a [[Footpod]] that analyzes the movement of your foot with greater accuracy than most traditional Footpods. While a lot of the Stryd marketing focuses on their "running power meter" functionality, I see the greatest value coming from their accurate measurement of pace and distance. If you look at my [[GPS Accuracy| testing of GPS Accuracy]], you will see that Stryd gives a far more accurate measurement of distance than any GPS watch. It accurate enough that it really doesn't need any calibration, and unlike GPS, it should work in any situation(see below for details. ) Not only is it providing accurate distance measurement, but it provides real-time pace, something that's impractical to achieve with any GPS device. While I believe [[Running Power Meters]] are quite different to cycling power meters and are more of a "power estimate" than a meter, I think that Stryd's power estimate has improved to the point where it's a valuable training and racing tool. At $200 220 I think that Stryd is good value for money, and it's one of the few running devices that I would replace unhesitatingly if I lost it. The current version of Stryd has "wind detection" to adjust the power estimate based on ambient wind. I've not tested this version yet. (Note that you need to have access to an iOS or Android device to setup Stryd.)
{{BuyStryd}}
=The Metrics=
Stryd provides an array of different metrics, which vary both in accuracy and usefulness.
* '''Pace and Distance'''. My testing has shown that the Stryd is stunningly accurate in its measurement of distance. It's the only [[Footpod]] that is accurate enough that it doesn't require calibration, something that greatly improves its usability. (It's possible to tweak the accuracy with calibration, but out of the box is should be much better than GPS.) If you look at [[GPS Accuracy| my testing of distance accuracy]] you'll see that the Stryd is right at the top of the chart, and is far more accurate than any GPS device I've tested. This accuracy is also reflected in its measurement of current running pace. I think that this feature alone makes the Stryd good value for money. (Stryd doesn't use or provide GPS data, it uses accelerometers. Depending on the watch, the data from Stryd can be combined with the Watch's GPS data so that Stryd gives distance and pace, and the watch's GPS can be used for navigation.)
* '''Elevation. '''I suspect that Stryd is providing remarkably accurate elevation information. Due to limitations on data export I've not been able to perform any statistical evaluation, but anecdotally the data looks really good. Obviously, the Stryd cannot provide any absolute altitude information, but it does seem to be able to measure relative changes far better than either GPS or barometric altimeter's. At the moment, this information is not as directly usable as I'd like, as it's only available in real time via their, not their watch integration. If you use the Connect IQ data field, it will record elevation as a custom data track, and it is possible to copy this to the standard elevation track using plugins to Sport Tracks.
* '''Running Power'''. As I talk about in my page on [[Running Power Meters]], I believe that they are not power meters at all. Like other running power meters, Stryd does not actually measure running power, but attempts to estimate what the power would be based on the things it can measure. My assumption is that it is mostly using pace and elevation change, possibly along with [[Cadence]] or Ground Contact Time. As discussed in the section below on the testing running power, I have found that the latest Stryd firmware gives a good estimate of relative intensity. I've been able to use Stryd to more effectively pace myself on hilly runs, as well as giving additional insight into [[High Intensity Interval Training]].
==Bluetooth or Ant+==
Stryd supports both Bluetooth and Ant+, and both work well. Bluetooth has the limitation that you can only have one receiver talking to Stryd at a time, so you can't have it linked to two different watches simultaneously, or to a watch and your smart phone at the same time. (I have had occasions where the Stryd has stayed linked to my smart phone, so I've had to turn off Bluetooth on my phone to allow Stryd to link to a watch.) With Ant+ you can have as many watches linked simultaneously, and it's possible to have Stryd linked to both one Bluetooth watch and several Ant+ watches at the same time. If you're using Garmin [[Connect IQ]], you can have Stryd work as both a standard Footpod and connected via the Connect IQ data field.
=Calibrating Stryd=
My testing shows that Stryd is remarkably accurate, but the company has reported that there can be some variation between Stryd devices. If you'd like to check your calibration, I'd recommend this process. (Note that the Suunto Spartan watches don't allow for any calibration.)
* Check that your watch is set to get pace and distance from Stryd. The best way I've found to verify this is to set the calibration factor to 0.5 and go for a short run. It will be immediately obvious that your pace is only half what it should be.
* Check the calibration factor is set to 1.0, and that any auto calibration is disabled. Auto calibration uses GPS, which is going to be far less accurate than Stryd. (If you're verifying a previous calibration, leave it set to that value but remember to adjust in the final calculations.)
* Use a standard 400 m oval track at a time when you're confident you can run in a single lane for a number of laps. The accuracy of a 400m track should be more than adequate for calibration, but if you're interested in the details, tracks are built in the US to various levels, with level 4 being suitable for national collegiate events.
* You should run approximately 30cm/12" from the inside edge of the lane, not down the middle. For the first lane, running along the inside marker will reduce the distance by ~1m, running the outside edge will increase the distance by ~3m, and running down the middle will increase the distance by ~1m.
* You don't have to run down the first lane, but you have to adjust your distances for lanes that are farther out. (See table below.)
* Start your watch and start running some distance before the start line. I would suggest at least 100 m. This is partly because the stride will do some smoothing, and obviously when you're run starts you're going from stationary to running. However, I've also noticed a number of watches that can be slow to start recording, so there first lap is rather short. You'll need to discard this first lap.
* Run a number of laps hitting the lap marker as you parse the start, or some other landmark.
* After the run, look at the lap distances for the measured laps, ignoring the first. The calculation is then fairly trivial; divide the actual lap distance by the average lap distance to give your calibration factor.
{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none;"
! Lane
! Total length
|-
| 1
| 400.00 m
|-
| 2
| 407.67 m
|-
| 3
| 415.33 m
|-
| 4
| 423.00 m
|-
| 5
| 430.66 m
|-
| 6
| 438.33 m
|-
| 7
| 446.00 m
|-
| 8
| 453.66 m
|-
| 9
| 461.33 m
|}
Don't use a race to calibrate, as it typically very difficult to precisely run a straight line and hit the tangents perfectly. You can also have problems with start up on some watches, where it doesn't record the first few seconds of the run.
==Example Calibration Data==
I ran a calibration test on a university track, running in the third lane with my Stryd on the inside (left) foot. I not only wanted to validate the calibration, but I also wanted to check the stability across a range of paces, so I gradually increased my speed on each lap. My previously calculated calibration was 1.013x (or 101.3% in my Garmin) and the average error was 100.15%, so my new calibration was 1.013 / 1.0015 = 1.011507, which works out to 101.2% on my Garmin.
{| class="wikitable" style="margin-left: auto; margin-right: auto; border: none;"
! Distance (m)
! Ratio
! Error
! Avg Pace
! Best Pace
|-
| 414.8
| 0.998724
| -0.53
| 9:40
| 8:17
|-
| 414.1
| 0.997038
| -1.23
| 9:40
| 9:13
|-
| 416.7
| 1.003299
| 1.37
| 9:14
| 8:59
|-
| 414.8
| 0.998724
| -0.53
| 8:59
| 8:24
|-
| 416.3
| 1.002335
| 0.97
| 8:33
| 8:17
|-
| 414
| 0.996798
| -1.33
| 8:31
| 8:09
|-
| 415.8
| 1.001132
| 0.47
| 8:03
| 7:49
|-
| 417.4
| 1.004984
| 2.07
| 7:46
| 7:34
|-
| 417.2
| 1.004502
| 1.87
| 7:31
| 7:21
|-
| 415.5
| 1.000409
| 0.17
| 7:12
| 7:00
|-
| 416.4
| 1.002576
| 1.07
| 6:46
| 6:32
|-
| 417.2
| 1.004502
| 1.87
| 6:34
| 6:18
|-
| 417.9
| 1.006188
| 2.57
| 6:10
| 5:51
|-
| 415.1
| 0.999446
| -0.23
| 5:41
| 5:02
|}
=The Stryd App=
The Stryd app is rather limited, and I mostly use it just to sync data with the web site. It is needed for use on a treadmill. See below under "smartphone apps" for more details.
==Accuracy Walking==
I've not done any statistical analysis of the accuracy of the Stryd while walking, mostly due to time constraints. However, my anecdotal use of Stryd while hiking on my testing course suggests that it's equally accurate when hiking in boots as it is when running.
==Accuracy and Consistency at Different Paces==
My testing showed that Stryd remains consistent across a wide range of paces. I tested from 9:40 min/mile to 5:40 min/mile with no differences.
==Responsiveness ==
Stryd seems reasonably responsive to changes in pace, though it's hard to determine how the smoothing of Stryd interacts with any smoothing of the watch. I've found Stryd responds within a few seconds, though the power estimate is a little slower to adjust. Recent firmware updates have improved the responsiveness of the power estimate, though it's still a little slower than I'd like on rapidly changing slopes.
=Treadmill Problems=
The Stryd is so accurate outdoors, I couldn't understand why it was so bad on a treadmill. To my chagrin, I discovered that the Stryd Footpod was right, and my treadmill was wrong. Accurately calibrating a treadmill proves to be rather more complex than I'd have expected, as the treadmill will slow down when your foot is in contact with the belt, then speed up when you're in the air. For details on how to evaluate your treadmill have a read of [[Treadmill Calibration]].
The claimed battery life for Stryd is only 20 hours, which is not long enough for many ultramarathons. Obviously, if you could have two Stryd pods, but that would be expensive. One option would be to use a Garmin watch that supports UltraTrac to extend the battery life along with the Stryd for accurate distance and pace. This would last for around 20 hours, and when the Stryd battery is dead, things would fall back to GPS. You may even be able to switch to normal GPS mode mid-run. I found that this worked nicely on a short run when I tested it out with the [[Garmin Fenix 3]]. I started off with the watch in UltraTrac mode and the Stryd connected. I then took the Stryd pod off to simulate the battery running out, and swapped to normal GPS mode.
[[File:Stryd And Ultratrac.jpg|center|thumb|200px|Here's the GPS track, and hopefully you can see the straight lines that you get when the watch is in UltraTrac mode and only checking GPS infrequently. On the way back I had normal GPS mode.]]
=Stryd Internals=
For those that are interested, here are the internals of a Stryd. (Thanks for Paul Day for the photo and the willingness to do the work.)
[[File:Stryd Internals Paul Day.jpg|center|thumb|300px|Stryd Internals (Copyright Paul Day, used with permission.)]]
=Stryd and Critical Power=
The Stryd app has started to support [[Critical Power]], a concept more widely used in cycling. The Stryd method of calculating Critical Power is to use one of 5Km/10Km race time, or a test protocol using just two durations. The research I've found on Critical Power suggests that more data points are needed to provide a valid measure of Critical Power, and especially W' (anaerobic work capacity). I'd recommend using more test runs and using one of the many Critical Power calculators available online. Stryd also has an [https://blog.stryd.com/2019/07/09/introducing-auto-calculated-critical-power/ automatically calculated Critical Power], but I've not seen any independent validation.
=Using Stryd With Your Watch=
Here's my notes on the compatibility testing I've done so far. I've had occasional issues with devices connecting to Stryd at the beginning of a run. I've not found any pattern to this, and it seems to impact both Bluetooth and Ant+ devices, so make sure you have a connection before starting your run. I've also occasionally forgotten to turn off auto-calibrate, which is another gotcha.
