Strava export not correctly recording pauses

[Šón Čestr]

@Dimitrios-Kanellopoulos not sure if you want a new thread opened for this? But I had a very bad Strava export today after a fartlek run. The data looks quite appropriate in Suunto App, but the Strava activity has spikes reaching 45 km/hr:

https://app.suunto.com/move/seanchester/5d37ac7617683a5924ecafe3
https://www.strava.com/activities/2557972773/overview

[Dimitrios Kanellopoulos]

Looks like it lost GPS ?

[Šón Čestr]

@Dimitrios-Kanellopoulos Yep! But the pace/distance data is coming from the Stryd footpod and looks fine in both Stryd Power Center and Suunto App. Only Strava appears affected (except, of course, for the gps trace).

[Dimitrios Kanellopoulos]

@Šón-Čestr hmmm. IS it sure that Pace on Strava is from Stryd? I am not sure about that. Just to understand on TP is it ok?

[Šón Čestr]

@Dimitrios-Kanellopoulos I don’t see any instantaneous velocity faster than about 3’56/mi (downhill) on TrainingPeaks:
http://tpks.ws/36ICQZJU6AL5JSYJIILU4465OA

[Šón Čestr]

@Dimitrios-Kanellopoulos okay, it looks like you’re right. Here’s the data from Stryd:
https://www.stryd.com/powercenter/run/6416472546017280

(I see now the peaks in TP and the errors in SA: I’m not accustomed to either interface.)

So this implies that I’m still getting speed/distance from gps/wrist acceleration? It’s very frustrating both how hard it is:
a) to set up the S9 to take pace/distance only from Stryd; and
b) to know what is the data source that the watch is currently using.

I’ve been trying to get these settings correct since I upgraded from the A3P several months ago.

[Dimitrios Kanellopoulos]

@Šón-Čestr let me help. Its easy.

1. Repair Stryd as a footpod. The moment you do it go on the watch to the paired devices list, find the footpod and turn off immediately the autocalibration. That will make the watch take pace ONLY from stryd and the track will be recorded as well.
2. That it.

[Šón Čestr]

Thanks, @Dimitrios-Kanellopoulos , but this is exactly what I’ve done. I repaired the foot pod (it’s not connected as a power pod) and immediately disabled “auto-calibration” based on the “auto-calibration” thread that I had started, and I did it again last night (in addition to switching from GPS+GLONASS to GPS+Galileo). In both cases, I waited at least 30 minutes until moving the footpod again, to ensure that it didn’t perceive the pairing as part of an activity.

This is why it was so surprising to me when you identified (correctly) that I seem to have gotten data from wrist acceleration when the gps + glonass signal dropped. I was convinced that it should have just come from the foot pod in the first place.

[Dimitrios Kanellopoulos]

@Šón-Čestr I bet that should not be the case really and I see no reason for that to happen.

I do suspect though an export error perhaps or other services doing their thing. I am checkin now this claim

[Dimitrios Kanellopoulos]

@Šón-Čestr I am sure the exported data are wrong

I loaded my activity on QS and this has the speed spike you mention.

[Dimitrios Kanellopoulos]

@Šón-Čestr I also looked at your data and I can see that autocalibration was not used.

So there is for sure a bug I suppose except in this case:

• Connection to stryd was lost as well.

However I do wonder: Did those spikes show also in realtime? I mean: Did you see that nasty pace?

[Dimitrios Kanellopoulos]

@Šón-Čestr said in Strava export not correctly recording pauses:

https://www.stryd.com/powercenter/run/6416472546017280

WAIT!

Stryd also has these SPIKES ! !!!

[Bulkan]

I use stryd as a footpod, in my s9 I don’t have the spikes. The 4 you see were a little of uphill short interval.

[Dimitrios Kanellopoulos]

@Bulkan can you also check his data? I see many spikes at Powercenter.

I am not a Stryd user so I am not so familiar with the latest news.

Also his pace looks very erratic.

[Bulkan]

@Dimitrios-Kanellopoulos It doesn’t have GPS signal, is a trail running or in a road? Looks like a trail running.

The stryd if you are jumping, specially in downhills, can have downspikes . The spikes also appears uphill if you are walking running in a very step hill. It has the logic, each time you start running uphill you deliver power.

For a better analysis is good to have a look with the ascend.

[Dimitrios Kanellopoulos]

@Bulkan yeah ok. But take a look. One spike on pace 2:30 pace could justify the issue that the user @Šón-Čestr has no ?

To me those 2 look aligned with what Strava / SA / QS shows.
So the watch indeed did use Strud but stryd gave the wrong data no?

[Bulkan]

@Dimitrios-Kanellopoulos said in Strava export not correctly recording pauses:

@Bulkan yeah ok. But take a look. One spike on pace 2:30 pace could justify the issue that the user @Šón-Čestr has no ?

To me those 2 look aligned with what Strava / SA / QS shows.
So the watch indeed did use Strud but stryd gave the wrong data no?

Totally, the power delivered is there, so the pace if is coming from the stryd it will go up. Looks like if @Šón-Čestr was running and start walking,. Was doing accelerations or interval before the spike?

I zoomed in that part. The data is ok, the stryd got the power correctly, suunto app did well, I think. Is running close to 400w before the spike, so looks like he was accelerating and then slow down.

[Šón Čestr]

Hi @Dimitrios-Kanellopoulos , @Bulkan ,

Yep, this was a fartlek workout. The spikes in Stryd occur for 10-20 second surges downhill (expected). These reflect perceived pace at the time. The huge spikes in Suunto App occurred on uphill surges with really exaggerated arm motion and reach paces that are much faster than one could achieve (circa 1:30/km).

What really surprises me is that the data doesn’t match exactly. Auto-calibration had been disabled, so I expected all the pace/distance to come directly from the footpod…

[Šón Čestr]

Just following up with a few more details/responses:

• when running a fartlek workout like this, I tend to look at the power after a surge, not during. So, I can’t say definitively that the connection to Stryd was maintained, but power was visible and plausible every time I looked
• I don’t display pace on my watch (which shows lap time/lap distance/elevation/10s power/lap avg power); so, I’m not sure what pace the S9 would have shown in real-time
• the spikes in Power Centre and Suunto App (for pace) do not coincide. If you enable elevation, one can see that the largest Stryd spikes are on downhill (expected), but many of the Suunto spikes are on uphill (where power and arm motion were maximised)
• The running was a mix of trail and road, but the spikes occurred on road.

To reiterate, for me it is this third bullet point that is surprising. I am trying to set up my S9 such that pace/distance is taken directly from the Stryd, so I don’t expect any difference across the various analysis platforms (up to a bit of proprietary smoothing).

[Šón Čestr]

Okay, sorry, one more clarification. It looks to me like the Suunto App data is fine. (I struggled to read the web version, so I am looking at it in the mobile app now, which makes the pace range clearer.) There, the pace seems to peak at 2’52/km. So, I agree with @Dimitrios-Kanellopoulos : this seems to be an export error. (There does also appear to be some smoothing of both pace and power compared to Stryd Power Center, which I ideally would prefer wasn’t there, particularly for workouts such as this with many short, fast surges. I notice the smoothing on my morning strides every day, too, where Suunto App shows lower power numbers than the real-time 10s power displayed on the watch and than in Stryd Power Center.).