Jul 2018
12:22am, 18 Jul 2018
26,716 posts
|
SPR
3000m was rubbish. Ran 9:54.98 (3:13, 3:23, 3:17). Didn't feel like I was dying but legs didn't cooperate. First properly poor race for about 18 months though so shouldn't complain. Guess it'll make me appreciate the good races more.
|
Jul 2018
10:05pm, 19 Jul 2018
1,005 posts
|
rhb
17.10 tonight, a gun PB.
Watch splits 1) 3.30 2) 3.26 3) 3.33 4) 3.19 5) 3.23
Km markers are always in same spots, not sure my pacing was that wayward tho!
|
Jul 2018
10:05pm, 19 Jul 2018
1,006 posts
|
rhb
17.10 tonight, a gun PB.
Watch splits 1) 3.30 2) 3.26 3) 3.33 4) 3.19 5) 3.23
Km markers are always in same spots, not sure my pacing was that wayward tho!
|
Jul 2018
10:05pm, 19 Jul 2018
1,007 posts
|
rhb
Oops double post.
|
Jul 2018
10:11pm, 19 Jul 2018
1,441 posts
|
Uyuni
A very strong second half that rhb, well done
|
Jul 2018
10:42pm, 19 Jul 2018
1,008 posts
|
rhb
Thanks Uyun... interestingly strava disagrees with watch!
|
Jul 2018
6:32am, 20 Jul 2018
1,021 posts
|
Chris
Got to love how strava thinks it knows better than the makers of the watch.
Good running, was it fairly flat?
|
Jul 2018
7:25am, 20 Jul 2018
64,345 posts
|
Gobi
Nice RHB
We love conflicting tech
|
Jul 2018
7:31am, 20 Jul 2018
5,891 posts
|
chunkywizard
Your watch just records positions into a file, how those positions translate to a course are open to interpretation ie, what happened between this second and the next second (or longer if your watch uses smart recording) did you travel straight, in a curve or something else. strava and Garmin use different interpretations hence the different values.
|
Jul 2018
8:23am, 20 Jul 2018
26,747 posts
|
SPR
Good work Rhb.
The watch physically laps doesn't it? I've notice my watch not react to lap presses immediately so can see errors creeping in there.
strava is just splitting your run every km, I'd guess Fetch and strava agree?
|