Exporting smoothed power data.
Posted: Mon Jan 29, 2018 1:25 am
I can't seem to find this topic on Newton 6 and anomalous power spikes.
I find that with one bike, my preferred Look 695 SR, that every ride I find very high power spikes. On some occasions over 1200W when 600-700W is expected. When the data is smoothed to 5", the power trace
appears to correlate to the data described in the detail box on the left. I suspect these fields in the box use 5" smoothed data for display.
When I export the ride file, these spikes are exported as well, as one would expect. Of course these show up in Golden Cheetah and WKO4 as true data points. Since GC and WKO4 don't smooth data for analytics, which Isaac seems to do, this skews the data resulting in incorrect power profiles.
Is there a way to identify and remove these spikes in the raw data before or at export? Is there a simple way to remove these anomalies in Isaac? Is there a way to determine why this happens with one bike and more than the other? Is it the out-front mount? I thought there was a low pass filter added in one of the FW updates, perhaps this was for road surfaces only and these spikes are something outside that algorithm.
I realize I can edit the file, File>Combine/Split>Delete Selection, but that can be a) tedious and b) occasionally I trim more than I need.
In GC, I can edit the ride, but again tedious, but much less so than in Isaac.
This does not happen to the same extent, still spikes, but less dramatic, when my N6 is used with my winter/gravel bike.
The N6 is mounted to a out-front mount on the Look, and the std handlebar mount of the Brodie.
I have been thinking of getting a PowerPod, and I understand that the PP is a Newton 6 in a different body (I read that in some post on this site) which I would
assume means that all the enhancements, improvements and updates made to the N6 would be embodied in the PP. But that would also imply that any issues, such as these spikes,
would also be present in the PP.
I have supplied a ibr file to illustrate the spikes, and a screenshot of how these spikes are nullifying the overall performance charts.
Thanks.
Thanks
I find that with one bike, my preferred Look 695 SR, that every ride I find very high power spikes. On some occasions over 1200W when 600-700W is expected. When the data is smoothed to 5", the power trace
appears to correlate to the data described in the detail box on the left. I suspect these fields in the box use 5" smoothed data for display.
When I export the ride file, these spikes are exported as well, as one would expect. Of course these show up in Golden Cheetah and WKO4 as true data points. Since GC and WKO4 don't smooth data for analytics, which Isaac seems to do, this skews the data resulting in incorrect power profiles.
Is there a way to identify and remove these spikes in the raw data before or at export? Is there a simple way to remove these anomalies in Isaac? Is there a way to determine why this happens with one bike and more than the other? Is it the out-front mount? I thought there was a low pass filter added in one of the FW updates, perhaps this was for road surfaces only and these spikes are something outside that algorithm.
I realize I can edit the file, File>Combine/Split>Delete Selection, but that can be a) tedious and b) occasionally I trim more than I need.
In GC, I can edit the ride, but again tedious, but much less so than in Isaac.
This does not happen to the same extent, still spikes, but less dramatic, when my N6 is used with my winter/gravel bike.
The N6 is mounted to a out-front mount on the Look, and the std handlebar mount of the Brodie.
I have been thinking of getting a PowerPod, and I understand that the PP is a Newton 6 in a different body (I read that in some post on this site) which I would
assume means that all the enhancements, improvements and updates made to the N6 would be embodied in the PP. But that would also imply that any issues, such as these spikes,
would also be present in the PP.
I have supplied a ibr file to illustrate the spikes, and a screenshot of how these spikes are nullifying the overall performance charts.
Thanks.
Thanks