I mailed it on there
Go Custom > Add field > give it a name > then in FIT file field put lap.max_power
> save > ok > close > actions > reprocess
Though as I say above I fear this might be the max of the last lap rather than the global max
That gave a value of 870 which is neither the max power of the last âworkâ lap or that last lap (recovery)
aha, sorry, learnings to be done
When I put Lap.Max_Power it shows the same for both Max and Lap.
A different activity to the one I shared before, and the max power wasnât the last lap either.
amâŚ
something after happening
Max is now 977
Yes currently the last one found is kept. Average pedal smoothness will likely require custom streams.
The max watts value from the power stream (record messages from the fit file) is 962w. Intervals.icu uses the power stream to calculate these things so it can support editing of power data and so on. I donât know why the session record has 977w.
You can download the streams CSV and open in a spreadsheet to check these things:
I could see 977 on the Wahoo during the activity
Maybe Wahoo is storing the power data with some smoothing applied?
Iâve no idea tbh
Itâs now showing 977 on intervals.icu. It just changed all of a sudden
I have a file from last week which still shows 999 on intervals and 996 on TP and Wahoo.
So just to be sure, I edited the max power from activity banner at top of activity to 1000 watts, then reprocessed original file and it went back to 977 watts.
Iâm trying to understand the terminology here
I checked the file from last week where max power was 999 but reported 996 on intervals.
Are these records on fitfileviewer not record messages from the fit file ?
Whatâs the âpower streamâ? Is it not just records from the fit file? And if so, why is intervals picking a max of 996 but TP and Wahoo picking a value of 999 (as seen in the fit file records)
On the fit file you have:
-
Stream records: a bunch of records, generally one per second, from the start to the end of your session, with all the data your device saves each moment (again, usually it is one record per second). This data is used to generate the graphs and plots you see on the activity page on intervals.icu. From here, intervals.icu extracts your maximum power. In your fit file, in this section, your maximum value of all the records is 996.
-
Laps records: one record per lap registered on the device. Here you have some averages and totals by lap. In your fit file, you have 999 as max power in one lap.
-
Session record: just one record for the activity. Final averages, totals and maximums per session. You can check if your device also saves here your max power of the session.
My guess: your device checks the power every fraction of a second (could be 0.1 seconds, 0.5s or any other), then saves one record per second on the fit file, so it averages the power on each one. However, it still has the absolute max power you have reached in the betweens of a second, so it saves it on the laps section (and maybe on the session as well).
Solution: If you have max power on the session section of your fit file, just create a custom activity field for it. If not, you need from @david to get the greatest value of the max power from the laps.
Thank you very much
So, yes, the absolute max power is recorded in the session records of the fit file as seen below in the screenshot.
But the custom activity field still pulls the 996.
Have I that field filled correctly? session.max_power
Have you reprocessed the original FIT file?
I have. What I havenât done is delete and reupload which I might do now actually
Yup. That worked. Deleted the file and after re uploading it has changed the session max to 999
I have made that custom activity field public and added a link to your post above describing the fit file records. Thanks for your help here. Much appreciated.
One thing I notice though, on all past files, is that in order for that max value to appear, the file needs to be deleted and re-uploaded. Reprocessing does not produce the value
Edit - Appears to work on some files and not others. Might be something to do with intervals editing being locked or something. Doesnât matter anyway. First world problems.