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

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.

  • Ranting is good as it takes the stress off :-). Kidding aside, have you ran(t) those 4 laps in order to calibrate? If yes and this is the outcome - please delete the contents of the folder Garmin/RunningTrack (there should be a file in it) - and do the calibration again (stand on lane 1, make sure you have good gps do the 4 laps and end the activity). Calibration is important because it recognizes that there is a track (and from an algorithm point of view, all 400m tracks have the same shape)

  • I warmed up 4-5 laps as a calibration but didn't save those laps. I had understood that if you don't care about accuracy in those first laps you're just fine. In this area by the river usually GPS is very good, guess I didn't see it coming, let's see see next time, thanks!

  • With the link, its much better do talk about it.
    GPS coverage should be no problem. You can really see when the algorithm kicks in. I can't see in Connect where it tracked laps short (350m rounds).

    Try a second run know that the watch nows the track. I think, the shift of the tracked laps to the image is because the image data is slightly shifted/missaligned (do you get it? Im not a native English speaker).

    , 400m tracks dont have the same shape, that is why the watch has to calibrate/learn the shape of each track you want to run. One of the bloggers, I think it was DCRainmaker, linked to an article about it: therunnereclectic.com/.../

  • A link to the FR745 manual, dont know if Garmin already inserted into the FR945 manual:

  • It may be the case, the image is misaligned but tracking is good. Well, it will look ugly but if it gets the distance correctly I´m fine with that. Maybe was part of calibration process but I expected all laps (400m automatic) starting/finishing more or less at the same point where I started the activity.  If you check the laps, the watch nailed the 1st one (400m, 8:36 min/mile) but second one apparently I ran faster (7:44) but I did not, lap alert popped up like 50 meters before, then a weird 270m lap... Well, I don´t know, perhaps I expected something better, or GPS is better that GPS+glonass after all... What I don´t know whether I should leave like this and try again or delete the folder as tsofron suggested and start over. Thanks!

  • well there you go ;-). you need to create a different activity for the calibration run, otherwise it won't work. so please check your runningtrack folder and detele that file in there, as if something got saved, it has definitely bogus data and subsequent runs won't look good on the map ;-)

    I warmed up 4-5 laps as a calibration but didn't save those laps
  • Will do, thanks!

  • Has anyone noticed SW 5.2 changed the Track Mode displayed accuracy to 10 meters? All distances are a factor of 10m. The Beta SW versions would display single meter distances.