Skip to main content

Module catalog_update

Module catalog_update 

Source
Expand description

The solid motors and data files ThrustCurve.org lists that the bundled catalog lacks (M5.7d, hpr motors update; ADR-288 §4).

hpr_motor compiles in ThrustCurve.org’s whole solid catalog as of one snapshot (hpr_motor::Catalog::bundled). update asks ThrustCurve’s search for every motor at once, keeps the solid ones (single-use and reload), and compares them with the bundle (Bundle). A motor is looked at more closely when its id isn’t in the bundle, when its record lists another number of data files than the bundle holds for it, or when its record was updated on or after the snapshot’s day. For each, it downloads the RASP and the RockSim files, and every file whose id the bundle doesn’t hold is newer than it. Each answer goes through the Client, so it lands in the cache: the downloads are the ones crate::on_demand::find reads, so a caller that then finds each newer motor by name has it offline too.

How far to trust it. It finds what ThrustCurve’s records say changed. A file replaced by another under the same motor, with the record’s file count and update day unchanged, isn’t found: no answer short of downloading every motor’s files shows it. A motor the bundle holds keeps flying its bundled file; a newer file of it is only cached. Tested on ThrustCurve’s answers recorded on 2026-10-29, which list nothing newer than the bundle, and on the same answers against a bundle with one motor and one file taken out, which finds exactly those.

Structs§

Bundle
What a bundled catalog holds, as update compares it: its snapshot’s day and, for each motor’s ThrustCurve id, the ids of the data files the snapshot listed for it, indexed or left out.
Newer
A solid motor ThrustCurve lists with something the bundle lacks.
Update
What update found.

Functions§

update
Compares ThrustCurve’s solid catalog with bundle, as the module describes, and returns what it lists that the bundle lacks.