Expand description
Rocketry Ltd’s flight logs as CSV, as a flight page on altimetercloud.com hands them back: a Nano V1’s, or a Mercury’s.
Rocketry Ltd’s altimeters, the Nano V1, the Mercury V1 and Mercury Plus, and the Jupiter, upload their flights to AltimeterCloud, which shows each on a flight page and gives back its log as a CSV file. Every one has a Bosch BMP581 barometer, and the Nano V1 and Mercury V1 a ±32 g accelerometer and a ±2,000 °/s gyroscope (Altimeters, https://www.altimetercloud.com/altimeters/, read 2026-10-13). Two layouts are in the project’s sample logs. A Nano V1’s opens with a flight summary of keys and values, then a blank line, then its header; its columns are those of the Nano V1 manual’s page CSV Flight log format (https://www.altimetercloud.com/support/nano-v1/flight-log-format/, read 2026-10-13):
Apogee meters,120.50,,Landing meters,-0.40,Burnout time (ms),900,
Apogee time,5.120,,Landing time,30.000,Burnout velocity (m/s),40.000,
…
Time(ms),Altitude(m),Velocity(m/s),acceleration_x(mG),…,Board temp(C),pitch,roll,yaw,tilt
-2000,0.010,0.00,0,0,0,-1000.0,0,0,0,,0.00,0.00,0.00,0.00,A Mercury’s opens straight on its header, in lower case, with the channels the Mercury V1 manual says it logs, “temperature, pressure, air density, predicted apogee and air brake output” beside the Nano’s (Mercury V1 manual, https://www.altimetercloud.com/support/mercuryv1/, read 2026-10-13):
time(ms),altitude(m),velocity_pressure(m/s),acceleration_x(mG),…,bmp_temp(x100),pitch,roll,
yaw,tilt,mt1_temp,apogee_prediction,air_brake_percent,target_alt,air_density,The logger is named from the header: a Rocketry Ltd Mercury if it has a column only the
Mercury’s layout has (velocity_pressure(m/s), bmp_temp(x100), mt1_temp,
apogee_prediction, air_brake_percent, target_alt or air_density), else a Rocketry Ltd
Nano V1, whose manual describes the other layout; a note on the record says which.
Recognition. Within the file’s first 65 lines, a header whose first name is Time(ms), in
any case, and which names acceleration_total(mG) and tilt too: following Debrief’s reader
(lib/parsers/altimeterCloud.ts, MIT, the project owner’s own; see THIRD-PARTY-NOTICES.md),
those two beside a millisecond clock are this logger’s own names, and no other layout among
the project’s sample logs has them. The lines above the header are the summary.
Columns. Every column is a channel; a column the reader doesn’t know is kept as written,
Quantity::Unrecognized, with a note. Each column holds only the rows that write it: the Nano
writes its board temperature on every 50th row and leaves it blank between (Nano manual), and
the Mercury’s slower columns are as sparse, so a channel’s clock is the times of its own rows.
The primary track’s temperature is on the track’s clock, a gap where the row has none.
| Column | Read as | From |
|---|---|---|
Time(ms), time(ms) | the clock: milliseconds from lift-off, before it negative | the header; Nano manual (“time from lift-off, with lift-off as zero”) |
Altitude(m), altitude(m) | Quantity::AltitudeAboveGround, m: the primary track | the header; Nano manual: the height above the pad after the logger’s TrueFuse and TruePath processing |
Velocity(m/s), velocity_pressure(m/s) | Quantity::Speed, m/s, up positive: the primary track’s vertical speed | the header; Nano manual: the vertical speed of the processed altitude; the Mercury’s, by its name, the barometer’s |
acceleration_x(mG), _y, _z | Quantity::Acceleration, thousandths of standard gravity, 9.806 65 m/s² | the header; Nano manual: along each of the board’s axes |
acceleration_total(mG) | Quantity::Acceleration, as the axes, but the acceleration’s magnitude less 1 g, −1 g in free fall, along no axis; the record has no quantity for that, and a note says what it is | the header; Nano manual (“with the 1 g of gravity taken out, so it sits near zero at rest”) |
gyro_x, gyro_y, gyro_z | Quantity::AngularRate, °/s | the Nano manual; a note says so |
Board temp(C) | Quantity::Temperature, °C | the header; Nano manual |
bmp_temp(x100) | Quantity::Temperature, hundredths of a °C, when the values bear it out (below) | the name; Debrief’s reader; a note says how |
pitch, roll, yaw, tilt | Quantity::Angle, degrees | the Nano manual (attitude angles from their zero on the pad, and the tilt from vertical); a note says so |
Pressure(hPa) | Quantity::Pressure, hPa × 100 Pa | the header; Nano manual |
Raw altitude(m) | Quantity::AltitudeAboveGround, m: the barometer’s altitude before processing | the header; Nano manual |
air_brake_percent | Quantity::Number, the percentage as written | the name; Mercury manual (“air brake output”); a note says so |
mt1_temp, apogee_prediction, target_alt, air_density | Quantity::Unrecognized, as written | no source states their units; a prediction and a setting aren’t readings, and the record has no quantity for a density; a note each |
The Mercury’s manual describes none of its columns, so where they share the Nano’s names, the Nano’s manual is taken for them too, and the notes say so.
The centi-degree temperature. bmp_temp(x100) holds the BMP581’s temperature times 100, as
its name says and Debrief’s reader takes it: 2150 for 21.50 °C, a whole number in every one of
the 4 Mercury files among the project’s sample logs as of 2026-10-13. It is read so if every
reading is a whole number, every one divided by 100 lies within the −40 to +85 °C the BMP581
measures, and at least one as written lies beyond it, so that the column can’t be in degrees
(Bosch Sensortec, BMP581 data sheet, BST-BMP581-DS004-13, revision 1.13, April 2025, table 2,
p. 10: the temperature measurement range, −40 to 85 °C). Otherwise it is kept as written,
Quantity::Unrecognized, with a note.
Placeholders. Two kinds of cell, as of 2026-10-13 in every one of the 11 files among the project’s sample logs, hold a number that isn’t a reading; each is a gap, counted in a note:
- The accelerometer before it reads. The first rows, all before lift-off, write 0 on all three axes (and −1000 mG for the total, a magnitude of zero less 1 g), where an accelerometer at rest reads 1 g. On the leading rows with a negative time whose three axes are all exactly 0, the axes and the total are gaps. A row at or after lift-off is kept as written: in free fall an accelerometer does read about zero.
- The temperature after it stops. The last readings of the board temperature are exactly 0, where the reading before was 27 to 44 °C. A run of exactly 0 that ends the column is a gap if the reading before it lies more than 5 °C from 0: a board can’t cool that far between two readings and then hold at exactly 0.00 °C. On a day near freezing the zeros are kept.
The yaw is kept as written, but a note counts the rows where it reaches ±327.67°: as of 2026-10-13, in no sample log does the yaw pass ±327.68°, ±32,768 hundredths of a degree, the range of a signed 16-bit number, though in all 11 it comes within 0.2° of it and jumps by more than 300° between two rows 22 to 121 times, so a yaw beyond that range isn’t written as it was: it is clipped, or wrapped to the other end.
The summary. The lines above the header are keys each followed by its value, groups of them
parted by an empty cell, as Apogee meters,120.50,,Landing meters,-0.40,…; a key with no value
is followed by an empty cell. The reader keeps:
-
Apogee metersas the stated apogee (Stated::apogee_m), m, as the key says; -
Serial numberandFirmware; -
Burnout time (ms)andEjection time (ms)as events,BurnoutandEjection; -
Apogee timeas an event,Apogee, in seconds if the altitude bears it out: if the highest altitude’s time lies within 0.5 s of it read in seconds. The key states no unit; as of 2026-10-13, in the 7 files among the project’s sample logs with a summary, it lies within 0.01 s of the highest altitude’s time read in seconds, and a thousand times off read in milliseconds; -
Landing timeas an event,Landing, in seconds if the altitude bears it out: if, read in seconds, it comes after the highest altitude and the altitude there (on the line between the rows either side, if no row is at that time) lies within 0.01 m of the summary’sLanding meters, and read in milliseconds it doesn’t do both. The Nano manual’s page Flight info page (https://www.altimetercloud.com/support/nano-v1/flight-info-page/, read 2026-10-13) gives the landing as “when it landed, and the height it came to rest at”, but no unit for either. Both are written to the millimeter, and the margin is ten times that; as of 2026-10-13, in the 7 files among the project’s sample logs with a summary, the altitude at the landing time read in seconds lies within 0.001 m of the landing height, and read in milliseconds, on the climb, more than a meter from it. Without a landing height to check, the landing time is left out.A note says how each time was read, or why it was left out;
-
Adjusted log: a value other thannogets a note, as AltimeterCloud can hand back a log recalculated after the flight with another pressure or temperature (Nano manual: the key “reads ‘no’ for an original flight”).
The events are in time order, as a summary has no order of its own. The other entries, such as the settings the logger flew with, are counted in a note and left out.
Rows. Every data row ends in a comma (Nano manual), so a row holds one more cell than the header names, an empty one; the Mercury’s header ends in a comma too, its last name empty, and that name is dropped. A row as wide as the header, or one wider with the last cell empty, is read cell for cell; a row of another width, a cell that isn’t a number, a row with no time or a time that doesn’t increase is refused, naming its line. Blank lines are skipped. Lines may end in CR, LF or both, and a byte-order mark is dropped. As every row must be as wide as the header, a short file can’t make the reader store more cells than it writes.
Where this comes from. The recognition and the centi-degree temperature follow Debrief’s reader; the columns’ units, the clock’s zero and the placeholders’ rules are the Nano manual’s and the files’; the summary’s times are read as the altitude bears them out. Where this reader departs from Debrief’s: it keeps every column, where Debrief leaves the gyroscope, the attitude angles and the Mercury’s prediction and air-brake columns out; it keeps the summary’s apogee, serial number and events; and it refuses what Debrief passes over.
Functions§
- read
- Reads a Rocketry Ltd log as AltimeterCloud’s CSV writes it, from its text.