Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Track Run test

timgrose
over 4 years ago

If anybody is curious about the new Track Run app in the latest beta, I got myself down to an actual track and gave it a go.

Here is what I found https://www.youtube.com/watch?v=AOzCGeUi_1I

Must say was impressed by the results.

  • 0 over 4 years ago in reply to Normar

    I bet the jog in the one spot produces the strange deviations from the track (oval).  My interval workout included a 400m jog, so I just continues to run around the track and started the next interval where ever the 400 jog ended.

  • 0 over 4 years ago in reply to olni65

    , I tried to follow the Garmin instructions you referenced but for whatever reason it didn't seem to work.  I'll have to have another go at it.

    The track that I ran was an older dirt track at a middle school in a town that I'm visiting for work.  It could be old enough that it might be a 440yard track and not a 400meter track.  I'm not sure how the Track Run would handle that situation.

  • 0 over 4 years ago in reply to Dan.Boilermaker

    I agree that that might be the case. But that severely limits how usable the mode is.

    - You can rarely perform the rest jog in the same lane as the interval, so you'll have to change lane on the watch twice in each rest 

    - I suspect most people prefer to start the interval at one of the shoulders of the track, so then you will either have to time your rest duration or have a distance specific rest.

    The watch should "understand" when you are actually running in a lane or when you are just jogging around.

  • 0 over 4 years ago in reply to Normar

    I think there are endless ways track workouts are played out and would be difficult to account for all the various workout types.  I don't know if the Track Run Activity was meant to be used with track workouts or just to track (and auto lap) a continuous track run/race.   

  • 0 over 4 years ago

    Looks like we need more aggressive algorithm in case of less-than-perfect GPS signal.

    Today I remove fit file and try to re-calibrate track by running one mile:

    Looks quite good -- less than 10 meters mistake on each of 400m laps. And than, I try to run 2*3200 (2 * two miles), and things go into mess:

    It nailed almost all track, except bottom curved path. For me it looks like all the track is moved up a bit, and GPS points in the bottom are bit too far from track, created by FR945 -- which leads to such distortions, 1km at 0:00 among others.

    I do not know if the calibration of the track under ideal reception conditions will be sufficient to prevent such artifacts from occurring?

  • 0 over 4 years ago

    As i did a factory reset on my 945 - i re-did the calibration run and had a regular workout afterwards:

    1. the calibration run was ok-ish:

    there were some smaller misalignments here and there, but nothing major:

    After finishing the calibration run and starting the workout - all went great:

    really, a rock solid performance.  

  • 0 over 4 years ago

    Tried on a proper 400m all weather track.  Calibration of 4 laps has the GPS wobble.  Saved off calibration run.

    Next workout.  Solid looking track and 400 splits dead on.

  • 0 over 4 years ago

    Hello all,

    I have the same issue on fenix 6.

    I guess the smoothering of gps coordinates outside the "optimal" oval track needs to be more aggressive too. Especially when gps conditions are not perfect (cloudy weather for example)...

  • 0 over 4 years ago

    Another day, same track.

    Everything was perfect until lap 18. Every time i cross start line, I saw the numbers 400, 800, 1200 and so on. The weather was disgusting, life was beautiful.

    And somewhere at mile five Garmin add 4 km to my 400m track. Yes, this little loop is about 4 km long. Kinda wormhole.

    All further laps were perfect again.

    Funny thing -- best pace in every mile was 3:30~3:40/km. But average pace at mile five was 1:13/km, three times faster then best pace in that mile. So it's obvious that the algorithm contains errors that allow such things.

    Other than that, the Track Run mode is very promising. Hopefully it gets polished and made super-reliable.