Lactate threshold missing / wrong data

vpier said:

Did you have by any chance time to look at the previous GC app versions for LT?

I do not need to look at previous versions, since it works all right for me. I meant I would look into in, if I were in your place, and had such problems. 

So you see the current LT along with Power, Power/Kg, Pace and HR?

Very interesting as all users should see the same view irrespectively of underlying os and watch.

By the way it seems impossible to test previous versions of an app in iOS.

No, I do not see power (and I do not remember ever seeing it), but I do see Pace & HR.

vpier said:

I keep track of the power and not pace or hr, as these are influenced by external factors, such as wind, humidity, etc..

Frankly told, power is influenced by it too, and since the power algorithm uses just the wind data from the closes airport for the calculation, it rarely matches the true local wind conditions, which are usually very variable during a run. Besides that, I mostly run trail / off road, and the impact of terrain (except of the general slope) is not applied in the power calculation, hence for myself, power is a relatively useless metrics, and I do not care about it much.

However, I understand that you (and others) want to see the threshold power. All I can recommend, apart of downgrading to an older app version, is contacting Garmin, and asking to bring it back. Either through https://support.garmin.com, or at Share Ideas | Garmin

Agree. What I mean though is that with power I can train on a threshold activity by focusing on power metric, which is influenced when I am going uphills and not based on pace, as pace on an uphill won't be a good indication of effort put in, while power is. The same way power works for cycling. 

The Firstbeat algorithms Garmin uses, accounts for slope grade if in acceptable range, and suppresses the calculation when the reliability of the data is not sufficient (such as steep hills). It means the LT pace is actually always taken at comparable conditions. On my mind it is more reliable than the power, which by my experience is far too depending on uncontrollable factors, and I do not trust it much.

So if I want to do a Threshold training and I have a lot of hills in my route (with normal grade) I should be working on a 4:37 pace (which is my LT pace)? I don't think that this will go well :) With power I can make sure that I keep the work I am putting in where I need it.

Maybe I seeing it wrongly, and maybe I am influenced by my on cycling power, which I know is far more reliable. 

If you want to measure your LT, then I recommend using the Guided LT Test, or doing a run with a mixture of paces, and certainly preferably on a flat terrain. LT does not change all the time, so it is sufficient doing it just couple of times per season, and choosing optimal conditions for it. If you do a run with a constant pace, the watch is unlikely to detect the LT, even if the pace is close to your LT.

I did that, as I've mentioned above, got a LT detected, that means Pace, HR and Power. I can see the Pace and HR in GC, but missing the power. I am using power, hence the complaint about this, as well as the issue of values that don't make any sense because:

a. I never did a run during the date that those values got registered

b. or are very low, like BPM of 30!