No, I hadn't. I'd kind of hoped he'd chime in here. It wasn't that big of a deal to me and didn't want to specifically bug him over this. I assumed it was just a quirk, some data somewhere threw the equation way out of whack.
Sorry for being slow to this thread. Thank you OneBadHawk for bringing my attention to it. I'm instantly reachable at
[email protected], but unless you use certain keywords here or an exact product spelling, I might not see it, or at least not for a while.
Some of these answers are correct, or pretty close.
1. Speed is by accelerometer. Orientation doesn't matter. During boost this is a great method for max speed. Baro is not a good method at all, except for gross average speeds over a time period with no venting issues at play (like from ground to ejection, but that average speed is only so meaningful, since there's coast in there, too).
2. The crazy result is simply a software bug. Ouch.
It's a bug that I don't recall seeing or at least not often enough to come to my attention (thanks for doing so). The acceleration readings are supposed to be capped at 23G (23G being rocket relative accleration to the earth, 1G is just gravity; save your breath if you feel a physics argument coming on). At 23G and 4 second burn, it should be good to about 4000 MPH if I'm doing math in my head right.
It's easier to diagnose a bug like this with AltimeterThree, because there's data to study in the spreadsheet. With AltimeterTwo, there's no other data to really dig into. But let me know if it reoccurs, please?