Skip to main content

Module fwsummary

Module fwsummary 

Source
Expand description

Featherweight’s summary files, as the Featherweight UI app exports a Blue Raven’s or a GPS tracker’s flight beside its data: the figures the logger worked out about the flight, one a row, and no samples.

The Blue Raven “records three sets of data for each flight”: “flight summary data such as maximum altitude and speed”, a low-rate set and a high-rate set, and the app downloads the summary first “so that the flight performance is immediately available for review” (Featherweight, Blue Raven User’s Guide, updated May 12 2026, p18). The app exports the summary as a file of its own, and a GPS tracker’s flight gets one too. Each row is a figure’s name, then its value, the unit written after the number:

Rocket Name,Club demo
Max Altitude,2500.25 feet
Max velocity,500.50 feet/sec
Thrust tilt efficiency,98.50%
Direction of 1st motion,-1.0000,0.0000,0.0000

A file is a summary when its first line that isn’t blank names Rocket Name, and a line among its first 200 names Max Altitude or Launch time UTC, figures only a summary states. A name is matched without regard to case or repeated spaces, and kept as written. A tracker’s summary is told from a Blue Raven’s by its Launch time UTC.

Figures. Every row becomes a Figure in Stated::figures, in the file’s order: its name and value as written, and the value in SI where the reader knows the figure. The unit is the one the file writes after the number, read only when it is one the figure’s name allows, as a header’s unit is read for a column. Every length takes feet or ft, every speed feet/sec or ft/sec; the table gives the words the sample files write:

FiguresQuantityUnit as written
Max Altitude, Main chute deploy altitudeQuantity::AltitudeAboveGroundfeet, × 0.3048 m
Inertial navigation max altQuantity::InertialAltitudefeet
Pad altitude ASL (a Blue Raven’s), Pad altitude (a tracker’s)Quantity::AltitudeMsl, Quantity::GnssAltitudefeet, ft
Distance at launch, … at apogee, … at landingQuantity::Distanceft
Max velocity, Drogue descent rate, a tracker’s Max vertical velocity and the other velocitiesQuantity::Speedfeet/sec, ft/sec, × 0.3048 m/s
Max motor burn acceleration, Peak drag deceleration, Apo channel max accel and the other outputs’, Max landing accelQuantity::AccelerationGs, × 9.806 65 m/s² (standard gravity)
Temperature on pad, Max Temperature, Min TemperatureQuantity::TemperatureF, degrees Fahrenheit
Battery voltage on pad, Min Battery voltage, Battery voltage at landingQuantity::VoltageV
Time to first burnout, Time to Apo channel fire and the other outputs’, Time to gyro overloadQuantity::Durationsec
Launch rod angle, Tilt angle at burnoutQuantity::Angledeg
Roll rate at burnoutQuantity::AngularRatedeg/sec
Pad gyro rates (deg/sec)Quantity::AngularRate, one value an axisits name’s deg/sec
Pad Latitude, Pad Longtitude (sic)Quantity::Latitude, Quantity::Longitudedeg
Thrust tilt efficiencyQuantity::Number, a fraction%, ÷ 100
Flight number, Number of ascent rollsQuantity::Numbernone
Direction of 1st motion, Gravity direction on padQuantity::Number, one value an axisnone: a direction of unit length
Pad Low-G Accel, Pad Hi-G accel, Low-G accel pad offset, Hi-G accel pad offsetQuantity::Unrecognized, as written, one value an axisnone written (below)
Rocket Name, Firmware, Serial number, Launch date, Launch time, Landing Time, Build date, Build time, Launch time UTC, Launch time local time zonetext, None

The manual’s description of the same summary as the logger’s USB port prints it (p31–33) names its fields’ units, and their words agree with the app’s (the USB form scales some, such as accelerations in g × 10, which isn’t compared): the maximum altitude and the pad’s altitude in feet, the horizontal velocity at apogee, the drogue’s velocity and the maximum velocity in feet a second, the motor’s, drag’s, deployments’ and landing’s accelerations in g, the tilt at burnout in degrees and the tilt efficiency in percent. Two figures the app writes are kept as written instead:

  • Main chute descent rate, whose value the app writes in feet, a length, where the manual gives the USB summary’s average descent under the main in “feet/second x 10”. A figure whose unit isn’t one its name allows is kept as written, Quantity::Unrecognized, with a note, and isn’t guessed into a speed.
  • The four pad accelerations and offsets, each three numbers with no unit. The manual gives the USB summary’s in “units of Gs x 10,000”; the app’s are not scaled so, and no source states what they are in.

A name the reader doesn’t know is kept as written too: as numbers, Quantity::Unrecognized, if every cell is one, else as text. Each figure kept as written has a note, such as `Main chute descent rate` kept as written, in a unit that isn't a speed: the file writes `-18.0 feet`; for a name the reader doesn’t know, a figure HPR Sim doesn't know kept as written: …, the name after the colon, as the survey’s public report counts each note by the words before it. A temperature below absolute zero, and a latitude or longitude past its range, is kept as written too.

What the summary states. The record’s Stated::apogee_m is Max Altitude in SI: the barometer’s altitude above the pad for a Blue Raven, and for a tracker its receiver’s altitude above the Pad altitude it states. Stated::ground_elevation_msl_m is Pad altitude ASL, a Blue Raven’s barometric altitude of the pad (“based on the barometric pressure”, p33), or a tracker’s Pad altitude, its receiver’s. The serial number and firmware are the rows’ text as written, and the flight number Flight number where it is a whole number. HPR Sim’s cross-check of these against the file beside each summary is in cargo xtask logs’ report.

No samples. The record’s clock, altitude track and channels are empty, as a GPS log’s barometric track is, with a note saying so: the samples are in the file exported beside it, the Blue Raven’s low-rate CSV (crate::blueraven) or the tracker’s CSV (crate::fwgps).

Cells and rows. Cells are separated by commas and trimmed of spaces; empty cells at a row’s end are dropped, as some files pad every row to four cells. Blank lines are skipped; lines may end in CR, LF or both; a byte-order mark is dropped. A row whose name is empty or a number is refused, as is a name stated twice and a value too large for its unit’s conversion. A row of nothing but commas, padding, is skipped as a blank line is. A figure’s value as written is the row’s text after the name, padding dropped from its end. A known figure whose cells aren’t the numbers it needs, such as a direction with two components, is kept as written, with a note.

Where this comes from. The layout, from the files themselves and the manual as cited; the summary’s names, and the Main chute descent rate kept out of the speeds, agree with Debrief’s reader (lib/parsers/deviceSummary.ts, MIT, the project owner’s own; see THIRD-PARTY-NOTICES.md). Where this reader departs from Debrief’s: it keeps every row, where Debrief keeps the few it compares; it keeps a stated zero, where Debrief drops it as “no measurement”: the file’s zero is what it says, and what a zero means is a reading, milestone M7.2’s; it keeps each sign as written, where Debrief takes the descent rates’ and the deployments’ magnitudes; it reads only the unit words the sample files write, where Debrief resolves any unit it knows, as the app “can be set to metric”, so a metric summary’s figures are kept as written here, with notes, until a sample of one is seen; and it recognizes a summary by its Rocket Name first and a figure only a summary states, where Debrief also counts its rows of names and values.

Functions§

read
Reads a Featherweight summary.