Add yaw rate data to .csv output file

[gplracerx]

This would make it a lot easier to compare accelerometer data to GPS acceleration data in a spreadsheet as lateral acceleration is yaw rate in radians/s (deg/s times pi/180) times velocity in m/s (kph/3.6) divided by 9.81. Or is that how you calculate the yaw rate? In that case, never mind. Vertical velocity and acceleration would be nice too, but it's much less important and vertical velocity probably isn't accurate enough with most GPS data. I can refine the accelerometer calibration angles by comparing accelerometer measured vs GPS calculated acceleration. But if you're using lateral acceleration rather than GPS heading change rate for the yaw rate, that won't help.

[Harry]

Yaw rate is calculated as the change in driving direction per time unit (degree per second). So you can calculate it from the difference in direction and difference in fix time between two consecutive GPS fixes. Both are included in all exports.

- Harry

[gplracerx]

Yes, but then I have to smooth it and fix the transition at 359 and 0 degrees and catch bad readings. Being inherently lazy, I was hoping that since it's already been calculated, it wouldn't be too hard to add another column to the output file. Obviously, it's not a high priority.

[Harry]

Yes, I understand the point. Yaw rate requires indeed a smoothing (including a dependency to GPS update rate). Problem is LapTimer does not store this value but calculates it on the fly while drawing the graph. I keep that point, maybe that area will change at some time.

- Harry