Looks like RD etc. data is good but the elevation graph seems quite jumpy and near end of the run looks like you jumped off a cliff or something... Looking at the map you ran 10k and you turned back after 5k, so the elevation graph should be a mirror image of itself after half point.
I'd first check that the barometric altimeter on the watch is working correctly since it's used as a part of the power calculation. Then contact support to change the watch if faulty.
Thanks for the input, you are correct about this run, 5K out then return along the same track. The middle bit of the run is on a trail through some fairly tall trees and it ts also reasonably hilly, and quite rough under foot. I noticed the sudden drop in elevation and have no idea what caused it, but the majority of my runs have been fine, I have seem similar drops with my previous watch, which was just using GPS for elevation.
I bought a Fenix 5 just before Christmas because I wanted to see what power was all about, but it is very difficult to make any sense out of the power graph when one minute it is showing 700 watts then seconds later it is showing 200 watts, I Guess I am used to seeing things like Heart Rate which are fairly linear, and I have never seen any other power graph apart from the one DC Rainmaker showed on his review of the Garmin Running Power, which does look a lot more steady than the stuff I am seeing.
Why doesn't lap average power, when reviewing later on Connect, show properly?
I set up a workout with the steps for a 3/9 FTP test from the 'Running With Power" book. During the 3 minute interval the values in the graph range between 385 and 404 while the 9 minute interval ranged between 356 and 375. The average power in the splits show 290 and 260 respectively.
The workout was done with Auto Lap turned off so both intervals are a single "lap" and all other stats show proper lap averages.
Now that you mention it I recall reading that somewhere before but one of the Running Power data fields is specifically called Last Lap Running Power and that stat is also one of the fields in the Combo app. I was actually using both of those during the run and Last Lap stayed null the whole time although on the few runs I've done so far with the Combo screen it has shown a value. Maybe CIQ can only see AutoLaps or maybe even manual laps but not workout steps? <shrug>
Anyway based on that I figured what might be displaying for the average power in the splits screen after step 2 is actually a rolling average but that doesn't work out either. The avg for the first workout step was 271, which matches, roughly, what I was seeing on the watch, and the avg shown for the second step is 290 which doesn't work if you consider (271*x)/2=290 would leave you with x=309 which doesn't work since the lowest point in the graph for that step is 368.
I guess I'll go hit the comments on the App Store and see if this has been brought up before.
R_Tellis if you have rest between the first and second work steps where your power is 0 or close to it, that's being calculated as part of the average and bringing it down. During a workout, I would expect any lap values calculated by a CIQ app to actually be cumulative averages for the entire activity, at the point in time the lap data was written to the file (at the end of the lap). Regardless of what the FIT file says, that app thought you were on lap 1 the whole time. The way it works is that apps do not have access to any lap average data, they have to calculate it themselves, so they need the watch to notify them when a lap occurs.
The function onTimerLap() is called during an activity when lap button is pressed. While using a workout file as guide, the onTimerLap() function is not called neither on automatic laps nor lap button is pressed.
If you want to see your real lap splits for running power after a workout, you would have to find some third party service that will display developer fields and that can also calculate arbitrary splits that you specify, rather than just displaying the laps from the file.
Thanks. That clears that all up for me. So it would seem that with the Last Lap Power datafield and the last lap power quadrant of the Combo Power datafield they are calculating, but not saving, lap average power. But only if it receives a TimerLap() signal, which it won't get from a workout step change, which would explain why those fields stayed zeroed out the whole time.
Sounds like in order for me to get the results from that test that I want I'll have to do manual laps.
Yes this has been the reality for some time now for people running with power. Even more frustrating is that you can get lap averages for custom workouts from any non-IQ data fields.
Manual laps is ok for simple interval goals and you learn to live with the limitation. If you want more complex workout structure, you may just give up unless you have a very good memory and concentration...
What I was actually thinking is to wear my 735 on the other wrist and have it doing the workout and hitting manual laps on the 645. Inelegant but workable.
Maybe, hopefully, this is something they'll fix with CIQ 3. As it is what Garmin is providing is the "first hit is free" for running power but setting it up for their competitors to profit if the addiction takes hold because the tools aren't there to do programs designed for training by power.
Regarding the issue where lap running power data is wrong for programmed workouts, I posted this elsewhere, but I thought it might be helpful to also post it in the sticky Running Power topic.
If you want to see correct Lap Running Power numbers for a programmed workout, after the fact, you can use the free iOS app ConnectStats. It downloads your activities from Garmin Connect, does some additional analysis and displays some additional information. It independently calculates Lap Running Power for any activities which have Running Power data, so you don't have to worry about whether the data recorded by Garmin is correct or not. https://itunes.apple.com/us/app/conn...581697248?mt=8
