Speedmarks
10 watchers
Jul 2013
3:06pm, 9 Jul 2013
13,776 posts
|
Nick Cook
Mine was done and loaded this afternoon.
|
Jul 2013
3:08pm, 9 Jul 2013
13,159 posts
|
fetcheveryone
Whoops, I missed your post Nick. Let me take a look at the code.
|
|
Jul 2013
3:10pm, 9 Jul 2013
13,160 posts
|
fetcheveryone
In the mean time, please entertain yourselves by entering this competition: http://www.fetcheveryone.com/book-theartofrunningfaster.php 
|
|
Jul 2013
3:11pm, 9 Jul 2013
13,778 posts
|
Nick Cook
Yes...I keep following those links. I've done it!!
|
Jul 2013
3:45pm, 9 Jul 2013
655 posts
|
Dochart
I love you, Fetch.
|
|
Jul 2013
3:47pm, 9 Jul 2013
656 posts
|
Dochart
I love you so much I'm going for run to night even though it's a rest day
|
|
Jul 2013
3:52pm, 9 Jul 2013
13,161 posts
|
fetcheveryone
I've found some (terrible) bugs, and things have improved somewhat (you won't see it on runs you've already uploaded, but if you want to upload again, go for it - although you'll be burned at the stake by the Conquercise and Fetchpoint tribes :0)) For you Nick, it now reports: Fastest 400m in 43 Fastest 800m in 1:35 Fastest 1km in 1:54 Fastest 1200m in 2:17 Fastest mile in 3:13 which is obviously a big improvement on what it was saying: Fastest 400m in 1:19 Fastest 800m in 2:08 Fastest 1km in 2:34 Fastest 1200m in 3:06 Fastest mile in 3:54 but even that improvement doesn't really add up when you're showing a fastest mile split of 2:46. The answer is in the way it works out when you've done a mile. It builds up a series of points along your route, until it's got a solid mile worth - and then calculates end_time - start_time. Here's the progression as you lower your best mile time: For mile lowering time to 234 for 2069.28291572 For mile lowering time to 233 for 2056.3447592 For mile lowering time to 228 for 2010.89239414 For mile lowering time to 225 for 1970.68985447 For mile lowering time to 222 for 1941.77858773 For mile lowering time to 215 for 1876.11193991 For mile lowering time to 213 for 1852.18427268 For mile lowering time to 209 for 1808.40180955 For mile lowering time to 203 for 1752.25601336 For mile lowering time to 202 for 1725.18988554 For mile lowering time to 199 for 1681.61125773 For mile lowering time to 193 for 1625.42509519 The figure at the end is the distance in metres. As you can see, most are over the required 1609.344 metres to make up a mile. So I need to adjust them downwards e.g. taking the last one - 1625.43 metres in 193 seconds is equivalent to 1609.344 metres in 191 seconds. I just need to apply that logic across the board and we'll get closer to accurate times. |
|
Jul 2013
3:56pm, 9 Jul 2013
13,162 posts
|
fetcheveryone
Steady on Dochart
|
|
Jul 2013
3:59pm, 9 Jul 2013
13,782 posts
|
Nick Cook
Ta Fetch.
|
|
Jul 2013
3:59pm, 9 Jul 2013
13,163 posts
|
fetcheveryone
Nickintrude - I've just run your data through the mangler again, and this time it's done pretty well. It said: Fastest 400m in 40 Fastest 800m in 1:23 Fastest 1km in 1:44 Fastest 1200m in 2:04 Fastest mile in 2:47 |
Related Threads
-
Anotther Q about Beats per Mile
Dec 2024
-
Stuff you didn't know in the Fetch training log
Nov 2024
-
Query about training log display
Oct 2021
-
Uploads doubled?
Jun 2021
-
Training log tags - do they tell a story?! :-)
Jun 2021
-
Website query: My calendar view has changed.
Apr 2015
-
favourite activities
Sep 2014
-
Upload bike rides in MPH
Sep 2014
-
New Glasses View - Coming Soon
Jun 2014
-
Benchmarks - what do the red and grey bars mean?
Oct 2013
