You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should be able to feed previous flights (in the standard format) as mock IMU inputs. This will let us make sure the state machine will work on launch day, and ideally can be an automated test to make sure we never break anything.
The standard format:
data stored in blocks corresponding to the polling rate of each block (i.e. the number of rows for each block)
H1: Name of Rocket: brief description
H2: Rocket Parameters Names. Ordered: Mass, Length, CG, CP, ...
H3: Rocket Parameter Values
H4: Data File Parameters Names. Ordered: #Blocks, [#_row_block_1, #_col_block_1, #_row_block_2, #_col_block_2, ... for each block] ,...
H5: Data File Parameters Values
H6: Auxiliary information about data (info about IMU orientation... stuff like that)
H7:
H8:
H9:
H10: Names of Data Fields
Block Column Order:
Col_1 is always a Timestamp
- then in order of the following priority
- (all raw data) before (all estimated/calculated data)
- within those groups
pressure/altitude, accelleration, gyroscope(angular rate), orientation, GPS stuff
Standard names:
time
pressure
altitude
accel_x
accel_y
accel_z
gyro_x
gyro_y
gyro_z
pitch
yaw
roll
quat_0
quat_1
quat_2
quat_3
Standard Units: SI (metric)
The text was updated successfully, but these errors were encountered:
We should be able to feed previous flights (in the standard format) as mock IMU inputs. This will let us make sure the state machine will work on launch day, and ideally can be an automated test to make sure we never break anything.
The standard format:
The text was updated successfully, but these errors were encountered: