How did you get these?
The acceleration is higher than the recorded acceleration on the flight computer and Jl2. The velocity and altitude are smaller than Jl2 data but are larger than the flight computer's data.
The AccX are from your data. The V & alt are integrating your Acc X data.
I did add back in the 9.8m/s/s to the 27nov flights.
Flight 2 and 3 had air brakes deployed. Flight 1 had the air brakes in the stowed position but they still hung out as shown in the video.
That explains the Cd slope differences, 0.0022 for 19Nov then 0.0034 & 0.0046 for 27Nov.
For flight 1 and 2 I tried to reduce air turbulence by covering large holes and only leaving small vent holes. Should I try adding more vent holes?
The Baro altitude from the 19Nov flight looks ok, at least the shape. I'd take the vents back to how they were then.
I have not been able to cone up with an explanation of why the the Baro Alt data has that shape. The internal pressure drops too quickly upon launch then increases (or decreases too slow) sometime after burnout.
If you use tape to cover holes and the tape come partly off this could cause air flow into the sensor bay.
Search this forum for Dual Deploy Ebays and how the vent holes are done. There is a ton of posts about this.
I guess the JL Alt2 is also inside this payload bay. It also needs vent holes that do not affect the bays pressure due to air speed. If the venting to the JL Alt2 is bad then its Baro data is garbage.
My current plan to fix the flight computer's low acceleration is to add or multiply the values by a constant during the burn to get them to match Jl2 data. This had some obvious drawbacks, does anyone have another idea?
Not sure if I would trust the JLAlt2's Max accel value since I do not know how it gets it. Ideally, it should only use Accel data until burn-out to report max acceleration of the rocket. However, it could report the Acceleration due to the ejection charge. This is clear in your Acc data as a large spike at 3-4 second after launch. This can easily be greater than the motor acceleration.
Have you done an accelerometer calibration (at least a check) by getting reading with Accelerometer Not moving and on all three axis on both directions (6 measurements)? Each should give a value of + or - 9.81m/s/s.
I know the MPU6050 Accel chip does not and needs both an offset and gain calibration to get good values. Remember you are integrating the acc data so each tiny error adds up.
I ordered (should be here today) a couple of LSM6DSOX breakout boards from Adafruit. After getting code to setup and read these First thing is check values against Earth's Gravity.
If your code is one file then post as a .txt file will work. If more then put the files into a .ZIP and post.
I can post to you the Python code I use to calibrate the raw data I log.