I am using Issac 1.08 and I did a number of coast downs today. Unfortunately, the first attempt at a coast down was on a slightly downhill stretch of road so deceleration wasn't happening. I pushed the middle button in an attempt to abort the coast down and then did 5 more in the other direction. When I got home and looked at the data I see the first coast down data still there and with an abnormal CdA contribution. I try to 'remove' this in the analysis venue in Issac, but it does not seem to affect the internal storage in the Newton and thus does not remove or mitigate its skewing of the data in the calc of CDA.
Can I remove this from the analysis IN the Newton?
Am I missing something in the UI in Issac?
Can a coast down be deleted from data in Newton?
Re: Can a coast down be deleted from data in Newton?
Upon closer inspection of the values stored for each of the coast downs and playing around with averaging these values, it appears that the values are not merely averaged. The net effect is that the spurious 1st coast down value does not appear to have much effect on the Aero value used to calc CdA.
List of values:
Start Time Aero Fric
12/9/2012 2:39 PM 1.684 5.90
12/9/2012 2:40 PM 0.284 5.90
12/9/2012 2:41 PM 0.284 5.90
12/9/2012 2:42 PM 0.311 5.90
12/9/2012 2:43 PM 0.267 5.90
12/9/2012 2:45 PM 0.303 5.90
Calc'd Values:
Aero: 0.289 Wind Scaling: 0.844 CdA: 0.342
Fric: 5.898
From this data it is hard to infer the algorithm for handling multiple coast down data set, but it is clear that there is some trap for a 'spurious' data point like the first value <1.684>.
Pushing the center button did not abort capturing of that data point, but somehow the firmware is 'catching' the fact that it is wildly out from the rest of the data set and, it appears, largely negating its contribution to the calc'd Aero value.
Looks Good!
List of values:
Start Time Aero Fric
12/9/2012 2:39 PM 1.684 5.90
12/9/2012 2:40 PM 0.284 5.90
12/9/2012 2:41 PM 0.284 5.90
12/9/2012 2:42 PM 0.311 5.90
12/9/2012 2:43 PM 0.267 5.90
12/9/2012 2:45 PM 0.303 5.90
Calc'd Values:
Aero: 0.289 Wind Scaling: 0.844 CdA: 0.342
Fric: 5.898
From this data it is hard to infer the algorithm for handling multiple coast down data set, but it is clear that there is some trap for a 'spurious' data point like the first value <1.684>.
Pushing the center button did not abort capturing of that data point, but somehow the firmware is 'catching' the fact that it is wildly out from the rest of the data set and, it appears, largely negating its contribution to the calc'd Aero value.
Looks Good!