Skip to main content

The workflow template catalog

A template is a workflow Constellation maintains. Open one in the builder or save its graph under a slug of your own, and the copy is your workflow to change. The API serves six, listed with GET /predictions/workflows?templates=true (reference).

TemplateThe question it answersLanesWhat it outputsAvailability
Pass yield, pass-yieldHow many GB will each pass deliver?snr, weatherExpected GB per pass, with its range and ledger, best passes firstEvery plan
Antenna capacity, antenna-capacityHow many minutes and GB can each antenna sell each day?snr, weatherPer antenna per UTC day: passes, sellable minutes and summed expected GBNetwork plan
MODCOD plan, modcod-planWhich MODCOD should each pass use, and when should it change?snr, weatherExpected GB and the number of MODCOD changes per pass, with a time-tagged MODCOD scheduleEvery plan
Rain-fade swap, rain-fade-swapWhich passes will rain cost, and what should be booked instead?snr, weatherOnly the passes at risk, each with a recommendation to swap to a backup pass before the cancel deadlineEvery plan
Audit ledger, audit-ledgerWhat did each past pass deliver against what it could have?snr, weather, and your pass logPer pass: GB possible, GB delivered and the outcome; totals per ground stationEvery plan; Explore has a free 48-hour audit
RFI watch, rfi-watchWhich links is interference about to cost lock?snr, rfiPer link: the worst interference in dB and the lock-loss risk, with a recommendation to rerouteOperator and above

How they price a pass​

The first five share one pricing chain and differ only after it. Every 60 seconds of each pass, snr gives the clear-sky link and weather the fade; sinr takes one from the other, capacity turns SINR into GB, success gives the chance the pass happens, and expected_gb multiplies the two. Then:

  • antenna-capacity adds sum_by, one row per antenna per day.
  • modcod-plan adds modcod_schedule, then keeps only the passes it could schedule.
  • rain-fade-swap adds swap: a pass is at risk when the weather lane, at its p50 (the median), costs it more than 30% of the GB it would carry in clear sky. The backup is the later pass of the same satellite on another antenna, within 6 hours, whose low case (p10) beats the pass's by the most. The deadline is 15 minutes before the pass starts, when most providers stop taking cancellations; a pass whose deadline has already gone is not offered. A pass at risk with no backup is still listed, with the note "No backup pass in the window" and nothing to approve.
  • audit-ledger adds ledger, which sets each pass against the contacts in your pass log.

RFI watch reads links rather than passes, sampled every 60 seconds over the next hour, and flags a link when interference at its p90 may take more than about 1 dB off it (the ITU-R I/N of -6 dB criterion). Every block is described in the node reference.

Where results go​

Every template has two outputs: the API (GET /predictions?workflow=<slug>) and a mission control output for Yamcs on the connection yamcs-bridge, with that template's event wording and Forecast page. Point it at another mission control system (MCS) or add a destination on your copy; see Results out.

Availability and plans​

  • Every template can be copied and run, except that a copy of antenna-capacity needs the Network plan to save. Where a deployment does not serve a lane a template reads, the API refuses its run with 422 lanes_not_served, naming the lane.
  • Explore runs templates as test runs over at most 2 satellites, on every served model. Operator adds runs that deliver and calibration.
  • antenna-capacity needs the Network plan to save its graph and to run it, test runs included. During a 30-day trial every template is open.

The full plan table is in Workflows: Plans and limits.

Next: open a template in the builder, or load the demo fleet to test one on six satellites.