Passes: the unit every forecast is about
A pass is one satellite in view of one ground antenna, from acquisition of signal (AOS) to loss of signal (LOS). Constellation forecasts what each pass will deliver and why, and every recommendation is about a pass. A pass you book, track and log is a contact.
Where passes come from
Constellation computes your passes; it does not import them. Each comes from:
- the satellite's orbit: its element set from the orbit catalog, found by
norad_id, or thetleyou give in your network config; - the antenna's elevation mask,
min_elevation_deg, the lowest elevation it can track at; - a time step,
step_son a workflow's input (60 seconds in the templates), at which the satellite's position is sampled.
GET /topology/passes lists the passes in a window. A pass keeps its pass_id across windows, so tomorrow's run prices the same pass under the same id. A pass already in view when a window opens starts at the window's start. A link that never sets (a geostationary satellite) is cut at each UTC midnight into day-long passes; each full day keeps its pass_id across runs, and the part of a day at either end of the window is its own shorter pass.
Passes booked with a ground station service provider are not imported yet; your passes are the ones your orbits and antenna masks give.
A pass in a result
| On screen | In the API |
|---|---|
| The pass | An item whose entity.type is pass, with its pass_id as entity.id |
| Its start and end | target_at (AOS) and until (LOS) |
| Satellite, ground station and antenna | entity.satellite_id, entity.ground_station_id, entity.antenna_id, and entity.link_id (<antenna>:<satellite>) |
| Expected GB and its range | value.p50, and value.p10 to value.p90 |
| Breakdown | explain: each step's value, unit and source |
| Recommendation | action, when a step suggests a change to the pass |
See Items for every field, and Reading a result for what the range and versions mean.
What decides what a pass delivers
A workflow such as pass-yield prices each pass step by step: the link's SNR along the pass, the weather fade on it, then the capacity of the link and the chance the pass succeeds, multiplied into expected GB. A pass whose low case is 0 GB, or that a step could not price, shows why under Upcoming on Passes, and opening it shows each step's value in its breakdown. Predict pass data volume walks through the chain.
Related
- AOS and LOS and Pass and contact in the glossary
- LEO contact scheduling
- Audit your passes: what past passes delivered against what they could have