Skip to main content

Module public_predictions

Module public_predictions 

Source
Expand description

Predictions merged before their errors: the public real flights that join the seven of crate::real_flight, each flown from its record alone (M2.3d3, decisions ADR-328 §1a and ADR-334).

A flight here has a design, a motor, a mass, a site, a rail and its air (the day’s weather, or a stored simulation’s standard atmosphere and wind), each from a named record, and a rule for the apogee its log is read at. It has no measured apogee: nothing in this module parses a flight log, and neither PredictionRow nor PredictionsReport has a field for a measured height or an error. The log’s bytes are hashed, so the report pins the file the rule is applied to, and never read as numbers. The comparison is crate::predicted_first’s, in the real-flights report (the errors): it prints each prediction here beside its log’s apogee and its error, and a prediction that changes is revised beside its merged number, never edited (REVISIONS).

What is flown is what crate::real_flight flies for the seven: the design under validation/designs/ built from the example’s inputs, on the example’s own thrust file with its burn time, from the example’s rail and site, in the ERA5 air of the launch hour, on HPR Sim’s own aerodynamics. The three EuRoC 2022 flights’ weather file is netCDF-4, which hpr_io::netcdf refuses; validation/oracles/netcdf/euroc_2022.py converts it as the guide says and checks the result, and CONVERSION_RECORD holds both files’ SHA-256 and the levels RocketPy read at each flight’s site and hour. The converted file is flown only if its SHA-256 is the committed one and HPR Sim reads those levels from it. Each prediction is held to the apogee first merged (MERGED), or to its revision’s (REVISIONS).

The predicted apogee is read as the log’s altimeter would read it (Barometer: the standard atmosphere’s altitude of the flown air’s pressure at the apogee, less the pad’s), because that is what it is compared with; the height climbed is kept beside it.

Two more flights have no example notebook (the Macie XL predictions, decision ADR-337): DESIGN_FILE_FLIGHTS, both of one OpenRocket design saved in a pinned public repository (ROCKETRY_FILES). Each is flown from that file alone, read as OpenRocket 24.12 saved it: the motor configuration, rod, wind and air of the stored simulation the repository names for the flight, on the bundled curve the file’s digest names. With them all five predictions are here (MERGED).

Structs§

CatalogCurve
A second prediction shown beside a flight’s counted one and never counted: the design flown as committed, on its own bundled catalog curve.
CatalogCurveRow
The catalog curve’s prediction, as the report keeps it.
DesignFileFlight
One flight predicted from a design file in a pinned public repository, before its log is compared.
DesignFilePredictionRow
One design-file flight’s prediction, as the report keeps it. Like PredictionRow, it has no field for a measured apogee or an error, on purpose.
MergedPrediction
A prediction as it was first merged, in the digits its page prints.
PinnedRepository
A public repository pinned in validation/refs.lock.toml, which a design-file flight’s design and log are read from.
PredictedFlight
One flight predicted before its log is compared.
PredictionRow
One flight’s prediction, as the report keeps it. It has no field for a measured apogee or an error, on purpose.
PredictionsReport
The predictions.
Reference
The apogee a flight’s log is read at: the rule, never the value.
Revision
A merged prediction that had to change: the number HPR Sim flies now, kept beside the merged one, with the reason (twelve public flights, predictions first, §1b).
WeatherConversion
The weather file’s conversion, as CONVERSION_RECORD holds it.

Constants§

CONVERSION_RECORD
The record of the EuRoC 2022 weather file’s conversion: the source’s and the converted file’s path and SHA-256, and the levels RocketPy read at each flight’s site and hour, written by validation/oracles/netcdf/euroc_2022.py.
DESIGN_FILE_FLIGHTS
The flights read from a design file, in the order the page lists them: Macie XL’s two.
DESIGN_FILE_TRACED_RULE
What “traced” means for a flight in DESIGN_FILE_FLIGHTS, as the page says it.
MERGED
The predictions as first merged (the EuRoC 2022 predictions, then the Macie XL predictions), which PredictionsReport::check_consistent holds every report to, the committed one in CI and a flown one before it is written: each flight’s apogee as a reading and as a height, and Andromeda’s on the catalog curve. The order is NEW_FLIGHTS’, then DESIGN_FILE_FLIGHTS’.
NEW_FLIGHTS
The flights, in the order the page lists them: EuRoC 2022’s three.
PREDICTIONS_JSON
The predictions, as data.
PREDICTIONS_MD
The predictions, as a page.
REVISIONS
The revisions: one. Erebus 11’s apogee rose 46.0 m with the base drag behind a boattail that ADR-362 relieved; the other eleven fly as they were merged.
ROCKETRY_FILES
The repository both Macie XL flights are read from: its design file and the two logs, as they stand at its pinned commit of 27 June 2026. No file of it is committed here: only SHA-256 hashes and numbers read from it.
TRACED_RULE
What “traced” means in PredictedFlight::untraced, as the page says it.

Functions§

corrected_apogees
Each predicted flight’s apogee with correction flown, by its id: every motor’s impulse and the drag scaled (Correction), the rest as run flies it, each flight’s result on its own (a flight that fails to fly fails alone). Each is the predicted apogee as the log’s altimeter would read it, m.
predict
Predicts one flight: flies it from its record and reads its apogee as its log’s altimeter would. The log is hashed, never parsed.
predict_design_file
Predicts one design-file flight: flies the stored simulation the repository names for it, from the design file as saved, and reads its apogee as its log’s altimeter would. The log is hashed, never parsed.
run
Predicts every flight in NEW_FLIGHTS, then every one in DESIGN_FILE_FLIGHTS.
varied_apogees
Each predicted flight flown as variant, by its id, as corrected_apogees flies a correction: its predicted apogee as the log’s altimeter would read it, m, and whether its design has two guides at different stations. With Variant::GUIDED each is the prediction run makes.

Type Aliases§

CorrectedApogee
One predicted flight’s id and its corrected apogee, m, or why it didn’t fly.
VariedApogee
One predicted flight’s id and its flight as a Variant, or why it didn’t fly.