fix bad data

[wormscoffer]

Hello all

I have a ride file from yesterday with some strange power and incline readings at the start. As it was downhill I know the power was zero and the incline was between 6-11%. Is it possible to fix this?

I'm sure this will have been asked before but I can't find anything with a search so any assistance appreciated.

26-09-2011 12-45-39.png (33.62 KiB) Viewed 6264 times

If you're having a laugh at my performance then it was slightly better on the 1st climb. I didn't feel up to a third one which was most frustrating!

Thanks

Andrew

[Velocomp]

Please post your ride file

[wormscoffer]

Voila - the complete file was 5.45Mb and won't upload so I've compressed it.

Same mountain, same day, two different routes. I drove the car from the bottom to the top after the first climb and descent so I wouldn't be doing the last descent fatigued in the cold, wet and dark. Just wondering if maybe that's what confused the iBike?

[wormscoffer]

bump!

I've uploaded the file.

Can you fix it for me please?

Probably more important, can you tell me why it happened and what steps to take to prevent a re-occurance?

Thanks

Andrew

[TriBike]

Hello,
I tweaked your file a bit. It looks like your friction #'s were way off. Tell me if this looks a bit more reasonable...

[travispape]

Probably more important, can you tell me why it happened and what steps to take to prevent a re-occurance?

I looked at your ride file--the whole file including the portion before your screenshot above--and something very odd happened at the 45 km mark. The altimeter (elevation) reading jumped from 240 m to 1800 m. And as far as I can tell, it looks like you really moved the bike from low elevation to high elevation without recording that portion of the ride in the file. (I don't know if you rode back up to the top or took a car ride to the top.) Anyway, that is what caused the data to go crazy. The iBike has a feature to make sure the slope it measures corresponds to the elevation profile. 99.9% of the time, this helps you get better data; however, in your case with the unrecorded gap of the ride, the jump in the elevation data caused this algorithm to go crazy for about 8 minutes or so. After that time it settled down and started giving you good data again.

To avoid this in the future, simply make sure you record the whole ride if you are actually riding back up to the top. If you take a car ride to the top, be sure to reset the ride file before you start riding again by holding down the center button until you see "trip reset" and then push the center button again to confirm.

Can you fix it for me please?

Here's how you can fix the ride file:

* Click on the graph just after the huge elevation jump.
* Right-click and choose "Split file at cursor"
* Open the last part of the ride and select "Tools -> Repair Ride for Bad Tilt Cal"

Travis

[wormscoffer]

Travis

Thanks for that. I followed your instructions and I have a good file now. I have it into WKO+ now with reasonable TSS and IF numbers which is what I'm after. I did explain what I did in my second post and your supposition was correct. I'll reset next time but it's not often I cart my bike up a mountain half way through a ride!

Tribike. I'm not sure where the friction numbers come in and how you tweak them. I'll have to go through the documentation and re-read it. I appreciate your taking a look.

I'm so pleased with my iAero, the software and the service that goes with it.

Andrew

[Jfala]

I am having a similar issue from a ride today. Have two significant power spikes when descending. I was recording the entire ride without stopping and I had just downloaded the new firmware and performed a tilt calc prior to the ride.

Any help is appreciated.

iDash_2011_09_30_0701_12_mi.csv

(1.06 MiB) Downloaded 391 times