watchman wrote:
Thanks. I am not surprised that there are features that I haven't uncovered.
I'm eagerly waiting for the app that automatically clusters and summarizes progress on my 1000-meter repeats, my tempos, etc. "You averaged 2 seconds/K faster than any similar workout since 2019, with less recovery."
Not trivial to code, I'm sure, but well within Google's capabilities.
One feature that sometimes gets poo-poo'ed is Garmin's VO2max prediction and Race Predictor, but these features may be under-appreciated. From my experience, firstly, it takes a few weeks of familiarity for the watch to dial-in on its fitness predictions. Secondly, these values should be looked at in terms of there relative use, rather than absolute values. For example, a VDOT prediction of, for example, 63, may not be as meaningful as the change in VDOT. And so, that change in predicted fitness is based on the algorithm's evaluation of a series of historical workout data, over time.
Now granted, I tend to run workouts all at the same track, and sometimes the same workout over many sessions. But the algorithm is supposed to be smart enough to throw out obviously wonky data that, if taken into account, would throw off its fitness assessment. For example, I've driven away from the track once or twice without remembering to 'end' (stop) the workout on the watch, so although it initially appeared to the watch that, all-of-sudden, I became incredibly fast as I drove down the road in my car, the watch threw that data out and did not include it when assessing my fitness, and it did it automatically, without my intervention.
(I'm speaking from the experience of using a 945.)