Closed ChristopherRabotin closed 11 months ago
Visit the preview URL for this PR (updated for commit c5bd169):
https://nyx-rustdoc--pr261-hotfix-tracking-sche-2qbe6whg.web.app
(expires Sat, 30 Dec 2023 08:31:30 GMT)
🔥 via Firebase Hosting GitHub Action 🌎
Sign: d8e2a55934352d850c15d11866c39eb2d2e029be
Effects
Includes breaking changes for the TrkConfig.
There was an attempt at building a tracking schedule while the measurements were generated. This led to a few unrealistic set ups, including the fact that the sampling rate could be wrong because of some attempt at being clever would fail.
This PR changes how TrkConfig is set up. There no longer is a start and end time per se. Instead, there's a scheduler, which will always schedule on visibility (defined as elevation > 0, regardless of the elevation mask of the ground station), and a cadence (either Continuous or Intermittent with an on/off tracking). From the scheduler, a set of "tracking strands" are built: these correspond to start/stop times during which the vehicle is over the horizon (in the SEZ frame of the ground station). Then, there is a "hand off" strategy that determines how to handle the case where several ground stations can see the vehicle.
Fixes #260
Measurement plots
The following plots used this configuration:
No type specified
Shows all tracking strands:
Ranging data
Fuzzy matching on column name:
plot_measurements(msr_df, "range")
Doppler data
Fuzzy matching on column name:
plot_measurements(msr_df, "dop")
TODO
P.S.: This PR likely includes quite a bit more work.