|
Dec 2012
2:37pm, 10 Dec 2012
12,117 posts
|
fetcheveryone
Pick any race that you did, and I'll shove it into my numberator, and it'll look at the training you did, and try to guess what your time would be. Nothing in the last week though, as the data I've used was taken from the live DB a week ago, so it doesn't know about anything since then.
|
|
Dec 2012
2:40pm, 10 Dec 2012
10,739 posts
|
Naomi P
Ok, how about Stevenage 1/2, on 4th November 2012. It was about 90% effort so should be a fair reflection.
|
|
Dec 2012
2:41pm, 10 Dec 2012
12,118 posts
|
fetcheveryone
For example, I've just asked it to guess my time at the Trent 5, which is my five mile PB (36:23).
Its five best guesses are:
CASE 1 PREDICTS 00:34:09
CASE 2 PREDICTS 00:35:24
CASE 3 PREDICTS 00:36:19
CASE 4 PREDICTS 00:37:55
CASE 5 PREDICTS 00:36:14
|
|
Dec 2012
2:41pm, 10 Dec 2012
12,119 posts
|
fetcheveryone
*spellcasting*
|
|
Dec 2012
2:43pm, 10 Dec 2012
10,740 posts
|
Naomi P
*is transfixed*
|
|
Dec 2012
2:44pm, 10 Dec 2012
12,120 posts
|
fetcheveryone
I've set it to work (it takes a wee while at the moment). I've given it a clue, and suggested that your time will be somewhere between 1:20 and 1:50, but other than that, it doesn't know anything other than your training info.
|
|
Dec 2012
2:45pm, 10 Dec 2012
12,121 posts
|
fetcheveryone
It's a bit off unfortunately. It's come back with:
CASE 1 PREDICTS 01:34:42
CASE 2 PREDICTS 01:30:17
CASE 3 PREDICTS 01:27:09
CASE 4 PREDICTS 01:30:36
CASE 5 PREDICTS 01:27:30
|
|
Dec 2012
2:47pm, 10 Dec 2012
10,741 posts
|
Naomi P
Erm, I might be training a bit fast then. My time was 1:37:07.
Bang in the middle of your 1:20 - 1:50 guess 
|
|
Dec 2012
2:48pm, 10 Dec 2012
12,122 posts
|
fetcheveryone
The closest matching case is this one:
[mileage] => 630.05 (in the 16 weeks pre-prace)
[daysperweek] => 5
[longest] => 15
[longest5] => 70
[inherent] => 506 (this is your average seconds/mile in training)
[speedwork] => 7 (number of speedwork sessions they recorded)
[badweeks] => 0 (weeks with no training)
[previousraces] => 2 (previous races at this distance)
[outcome] => 01:34:42
[conversion] => 0.8572 (ratio of training pace to race pace)
This is compared to your data:
[mileage] => 569.7
[daysperweek] => 5
[longest] => 15.65
[longest5] => 74.09
[inherent] => 504
[speedwork] => 7
[badweeks] => 0
[previousraces] => 12
[outcome] => 01:37:07
[conversion] => 0.8826
|
|
Dec 2012
2:49pm, 10 Dec 2012
12,123 posts
|
fetcheveryone
Unfortunately, my 1:20-1:50 guess was based entirely on looking up your time
I wouldn't read anything into the figures just yet. This process is all about finding the relevant parameters to describe each case - and I don't think I'm nearly there yet.
|
