I recorded another Taser flight with a B4-4 engine. Similar performance to the previous flight, but without the missing 200ms of data at launch:

The acceleration data shows a much more believable trace:

Note that the burnout didn't occur until nearly 0.8s, and there is no longer a discontinuity in the accel or altitude data. There is a bit of wiggle in the acceleration data prior to launch. This caused the app to generate erroneous values for the Flight Stats. The algorithm now resets if the acceleration drops below g=1.0, and uses g > 1.3g to establish true launch event. All of the Flight Stats are now based upon the "true launch event time" rather than the launch detection threshold set by the Settings.

This should yield a better correlation between actual data and the simulation results from OpenRocket.