@HoboBob:
I think this is another case of bad data sneaking in. As I wrote in that post (
https://forum.hptuners.com/showthrea...1#post567086):
Since we can't assume perfection in hardware, the software -- RR -- should correct for this. It would be a whole lot easier than having the user open a spreadsheet each time a straight line appears as the path of travel, searching for bad data, and adjusting it. I mean, that kind of task is exactly the kind of work computers are good for.
This is still my opinion. That is, since a GoPro device is acquiring this data in real time, it's almost impossible (barring some tricky internal buffering calculations) for GoPro to catch any of its own mistakes. OTOH, RR can have a look at ALL the data as it imports it, and with some simple programming can figure out that some rows of data are way out of whack. At that point, if I were doing the programming -- and I'm a retired geek -- I would emit a dialog box, saying something like, "A few rows of data appear to be in error. OK to average out those rows, with the data appearing before and after?"
Do you know whether anyone on staff has considered such defensive analysis and programming, or am I talking to a wall here?