Finishing time estimation. What does it show exactly?

Would also like to know

It seems to me to be a calculation based on current pace, but must be a moving average over the previous few minutes, as if you walk for eg the finish time moves out progressively. Likewise when you start running again the fnish time slowly comes down even if you run a constant pace, (hence my moving average assumption)...

I tried it with a HM on Sunday. Whilst we will never know the exact algorithm then (B) out of your three best matches it. So what's done is done and it takes your current pace and distance left and computes what time that will take and effectively adds to the time already taken.

In my race it was a bit easier "out" but we had to contend with a headwind for the last 3 miles. As such for much of the race it was predicting a time just under 80 mins but in those last few miles it gradually slipped past 80 until got to about 80:30 with about 0.5 mile to go. I put a finishing spurt in and managed to get back a few seconds and ended up with 80:21.

It did seem quite "sensitive" and although my mile splits were mostly no more than 10 secs apart the predicted time was sometimes 78 or 79 on the way out. I suspect there is some smoothing of current pace that goes into the computations but not a huge amount.

Best thing to do is to try it on a run where you aim to run at a steady pace over a known distance and see if you like it.
Not sure if I really found it helpful or not TBH. Sadly when it slipped over 80 mins there wasn't much could do about it - just was going as hard as I could that day.

Thanks.
Moving average of the last minute or so, instead of current pace is MUCH better estimate.
If it takes into consideration the part fo the workout already done, would be a great estimat¡on.

And thanks also TIMGROSE. I had not read your post when I wrote mine.
Good and clarifying description. It seems the moving average mentioned by ZRACS could be the algorithm.
Knowing that it takes into consideration what is already run and that there is an algorithm more elaborated than the "current pace" for the remaining part, it can be of some help for example in a marathon.
At least I wanted to know that it is not a useless feature.
I will try to find out more and if so, I will post it here.
Regards

* BTW, Congrats for the 80 minutes

In my race it was a bit easier "out" but we had to contend with a headwind for the last 3 miles. As such for much of the race it was predicting a time just under 80 mins but in those last few miles it gradually slipped past 80 until got to about 80:30 with about 0.5 mile to go. I put a finishing spurt in and managed to get back a few seconds and ended up with 80:21.

I'm sure your post is technically correct since you seem to be the most knowledgeable contributor on here. But all I could focus on was you casually referring to a 1:20 half marathon effort. Stud... :)

Well there you go, I never knew this existed!

I had actually just coded up my own race predictor field the other day in fact! I probably wouldn't have bothered. I guess at least my one also shows seconds ahead/behind your goal time.