Movescount is the sports community where every Move counts.Make your Move, track your progress, share it online. Or be private if you wish.Use Suunto device or get the free app for iPhone.
Marathon time calculates your estimated finish time for a full marathon in real-time. This is a great tool when striving for a new personal goal. Include this App in your running mode and use it pace yourself to reach your goal.
Compatible POD(s) might be required
What are Apps? Learn more.
Sorry, "<" and ">" characters are not allowed.
I do not work. Always shows me several seconds or even a negative value.
How to plugg this App on my Ambit please?
You can find instruction from faq: http://www.movescount.com/faq#Suunto Apps
This "App" is to complicated, 42.195 * AVG_SPD is tho same result!
This takes into account if you have done very fast the first 30km.. and then you start to slow down. More intelligence!
yeah, this calculates what you've already done so that you can look down and see what your time should be at any given point - it tracks your performance up to that point and knows where you stand in the race.
No, it doesn't, because AVG_SPD is exactly DISTANCE/DURATION. To get a better result there should be used also SPEED, LAP_SPEED and/or LAP_SPD_PREV. There is an other App doing it a little bit better.
I also think it is better to use the speed that you had for the last and current
lap since this actual takes in to account how fast your going at the moment
and faster detects if you are starting to slow down. Lets says you ran 30 km
too fast and you are starting to slow down. This app wont show this change
immediatley since your average speed wont change much until you have ran a couple of
slow km. By replacing AVG_SPEED with (0,5*PREV_LAP_SPEED) (0.5*LAP_SPEED) you can accomplish this
At least for me the question normally is this: "Is it enough that I can keep my current pace for the rest of race?" It's not possible to change history, so I claim that only distance left and current lap pace are relevant variables. There is no reason to look back and calculate anything based on previous lap(s). If you agree, try this one: http://www.movescount.com/apps/app1640-Responsive_Marathon_Time_Forecast
I would recommend you to try mine. I take in account speed reduction of 6% if distance doubles. I had to use polynomial function to approximate unavailable power fonction in appl. Test it and let me know what you think!