Yeah, I wouldn’t expect perfect speed or accel data out of it. The max speed during that flight changes from 1.9M to 1.5M though & Gs drop by an order of magnitude.
Is a filter on/off checkbox on the configure graph tab doable without much pain? Maybe that’s a good way to do it. > On Sep 18, 2017, at 9:51 PM, Keith Packard <[email protected]> wrote: > > Bryan Duke <[email protected]> writes: > >> Just as I got done testing this in 1.8.1, 1.8.2 came out — so, I retested >> and still have a bug report. >> >> I flew another flight on my 29mm min-diameter rocket this weekend & >> the data views in AltosUI looked incorrect. The graphs & flight stats >> in AltosUI v1.6.8 looked correct, but both 1.8.1 and 1.8.2 look like >> at least the max speed & acceleration are wrong. > > With a baro-only altimeter, you're not going to get very good speed and > acceleration data no matter what you do. The baro is noisy enough that I > end up smoothing it a ton before differentiating, which is why the speed > and accel data look like they do. I played with a bunch of different > smoothing amounts, and maybe ended up doing too much. Hrm. I could > probably provide a knob in the 'configure graph' window for how much > smoothing the filtered results got; that might be fun to see. > > The altitude data is coming directly from the baro sensor, so it's > solid, I'm afraid. No filtering at all. > > -- > -keith _______________________________________________ altusmetrum mailing list [email protected] http://lists.gag.com/mailman/listinfo/altusmetrum
