Strava

Can anyone explain the difference between Training Impulse and Suffer Score on Strava ?
Especially in relation to calculating Form/TSB on the Fitness and Freshness chart

I've been using Suffer Score on an excel spreadsheet to calculate Form/TSB, but suspect I should be using Training Impulse instead ?

you want to be looking at training load

What is the reason betweed top speed differences on the garmin (36mph) and when uploaded to strava (29mph)?

I am using the garmin speed and cadence sensor on a stationary trainer. So no gps speed involved.

How is strava working out the speed from the garmin file?

My biggest gripe with Strava: rides recorded using a Garmin usually have a higher average speed and greater recorded elevation than the same ride recorded using the smartphone app.
I understand why the speed might be different (assuming both based on GPS, no sensors), particularly on a commute/through town, because ten seconds pass before Auto-Pause does what it is supposed to (and this doesn't always work if it's cloudy/wet/congested, due to poor GPS signal)... But, I've always envied friends' stats at the end of a week where we've ridden together; I look like the wimp who only rides on the flat (although, in/around Manchester, this isn't difficult).

Example: 14km morning commute when plotted in Route Planner estimates 57m or elevation, but the Strava records zero.
The same route in reverse, in the evening, allegedly rises 101m, but the app only records around 50m.

I know Garmin gets its data from an inbuilt barometric altimeter, or something, so should be/IS more accurate, but I feel aggreived at the prospect of having to pay Garmin Tax for that extra performance.

http://www.digitalepo.com/

Haha!

I know Garmin gets its data from an inbuilt barometric altimeter, or something, so should be/IS more accurate

It's not really any more accurate, it's just a different number.

GPSes just don't do climbing calculation well enough for it to be anywhere near reliable. Even the barometric altimeter in Garmin's is fraught with absurdities.

(I went for a long run last weekend. When I got to the Thames my Garmin was claiming I was at -5m altitude, 3 hours of running along the tow path, and getting back to that exact same point, it has steadily climbed to 11m altitude.)

Here's some science: http://www.staff.city.ac.uk/~jwo/landserf/audax/elevation.html

Nice article, and there's comfort in knowing it's probably just as (in)accurate.

On my tour I ended up riding with a German software engineer for a long time, he was really interested in this stuff and had set up his own way of measuring altitude and was using a couple to try and verify the results. I'm being deliberately vague because I can't remember much of what he was talking about but it was really interesting, I'll drop him an email today and see if he can send any info about his setup over

Thanks Al, that would be great!

Any idea why Strava wouldn't log a ride. Synced today's ride but it's not appearing and no longer seems to be on my garmin. No biggie, just wondering.

Same happened for my Friday morning commute (via iPhone app) but it reappeared the following morning. Yours ok in the end?

Nah, think it's disappeared into the ether for good. Not too bothered, just wondered if it was something I'd done wrong.

Having recently acquired an edge 1000, I'm now finding myself chasing @eyebrows up some of my most commonly ridden Kentish cols as he has the fastest segment times of those I follow

Literally and metaphorically chasing shadows

Distance on this is not, I believe, correct: https://www.strava.com/activities/534362056

How do I change the distance?

What does the distance show on the device ? Corrupted file or corrupted transfer ?

If corrupted transfer (i.e. ok on device), you can try deleting from Strava and re-uploading, pulling the file directly from the device if needed rather than going via Connect.
If file on device wrong, you can try editing it in something like Golden Cheetah or Training Peaks. Strava doesn't allow you to do much (if anything) with the data itself

Distance showed as 10k on the device as well.

See what you can do in Golden Cheetah or Training Peaks I guess then ?

You can see (now that Garmin Connect has un-failed) that when we stopped for a coffee the Fenix lost the speed sensor (it lost all the sensors bar HR, but I manually re-paired the Powermeter) which accounts for it only having 10K recorded: https://connect.garmin.com/modern/activity/1112037801

It's a real pain in the arse that the Fenix doesn't re-acquire sensors when you start off again.

Pretty decent average speed...

Strava uses the GPS data as last resort for the distance measurement. If you've got info from something equivalent to a GSC-10 (speed/cadence sensor) then it'll use that, even if it's woefully inaccurate or only partial data.

Stripping that stuff out of the file and reuploading will work; so that Strava will then default to the GPS trackpoints.

If it's a .fit file then convert it to .gpx (or .tcx). Then edit that and remove the DistanceMeters tags (there will be hundreds so it'll need a text editor that can do regex search/replace).

Feel free to email whatever you've got to me (alex @ <username> .org) and I can do it.

anyone got a free premium trial code going spare? want to check out these live segments on the 520

http://www.latimes.com/business/la-fi-tn-strava-dopers-20160415-story.html

Comparing your segment times to anybody other than yourself (or close friends) is a bit pointless really.

very.