EX13 — Observation To Delivery¶
Tags: observation · finite slew · store-and-forward · power
Input: observation-to-delivery.yaml · Runtime tier: standard · Recommended views: 3D, Attitude, Power, Analysis
Purpose¶
Trace data from regional collection opportunity through achievable pointing, onboard activity, store-and-forward transport, ground delivery, and spacecraft power.
Setup¶
Six satellites observe three targets and downlink through three ground sites over 12 hours at a two-minute cadence.
astraeus run astraeus-resources/examples/user/observation-to-delivery.yaml
RunSpec Focus¶
Several requested stages form one evidence chain. Store-and-forward is enabled so captured products may wait for a later gateway opportunity.
execution:
stages: [mission, transport, power]
mission:
kind: observe
transport:
allow_store_forward: true
power:
activity_coupling:
component_profile: power_activity_coupling.customer_observation_activity
Results¶
The reference run completed successfully in 2.15 seconds. The observation stage created 180 MB across three targets; transport delivered 164 MB (91.11%), with 16 MB remaining at the end of the run. Fleet state of charge stayed between 68.92% and 74.62%, with no power infeasibility.
Artifacts To Inspect¶
| Artifact | What it shows |
|---|---|
mission/observation_summary.json |
Target count, capture duration, and total product volume |
mission/observation_capture_events.parquet |
Time, spacecraft, target, and product for each capture |
transport/transport_delivery_events.parquet |
Product delivery, partial delivery, and expiration events |
transport/transport_backlog_timeline.parquet |
Undelivered product volume and age through the run |
power/timeline_power.parquet |
Electrical response to capture, processing, and downlink activity |
Interpretation¶
Collection success and delivery success are separate outcomes. The residual 16 MB shows that a product can be captured yet miss a suitable delivery opportunity within the study horizon. Extend the horizon or alter gateway geometry before interpreting residual backlog as lost data.