I believe Garmin coders need to re-examine how they calculate/use zones when downloading HRM-TRI data after an activity.
Here is a classic example but I notice this happens every time.
This is from an hour long run, no GPS loss, every-second recording on Fenix5s with HRM-TRI using contact-gel and brand new battery so there is no dropout (optical turned off).
The top row is before the download, using the firstbeat metrics etc. on the watch.
The top row is likely correct. This was a relatively easy run, at no time did I exceed lactate threshold so no anaerobic effort.
The bottom row is after the HRM-TRI download using the menu on the watch after it processes the data.
There is no way, in heck, that I use 2.0 effort anaerobic. That would be a tempo/workout level effort.
You can see it shifted around some seconds in the zones, nothing dramatic. 2.0 anaerobic would require MINUTES in Z5
So this has to be a bug in how it looks at the watch zone settings and the firstbeat metrics.
