Forecasts: the models, and what changes if something does
Forecasts is three panes side by side. The list on the left switches between Models and Scenarios (?list=scenarios), each with its count; the middle pane shows the one you choose, and the right pane its details.
Models
Models lists every model family the catalog holds, one row each: a dot (green when it is served), its name, and what it forecasts in a few words. The title row counts them, such as "4 served". A family not served yet reads Coming.
Choose one (?model=<family>) and the middle pane shows its card: its name and what it forecasts in a few words.
The right pane, Model, opens with what the model forecasts and how to read it, starting "Link SNR forecasts a link's median SNR in dB at the time you name.", then its facts as label and value:
| Label | Shows |
|---|---|
| Status | Served or Coming |
| Forecasts | What it predicts, in words, with units |
| Horizon | How far ahead it forecasts |
| Reads | What it is fed |
| Workflow lane | Served, or Not served here when workflows on this deployment cannot price with it |
| Release | The release id your newest run priced it with; without one, Version, the catalog's version |
Model docs opens the model's page. The cards are also under Models and their tiers.
Scenarios
A scenario answers what happens if something changes: a ground station goes down, heavy rain comes, or you add an antenna or a satellite. It is priced with the same workflow as live, over the same window, and shown as the difference it makes. Nothing a scenario prices is ever delivered.
Scenarios lists yours, newest first: each one's name and the day it was made, and its changes in words under it. Past 20, a search box narrows them. With none chosen, the middle pane says how to start one. + New scenario at the foot of the list makes another.
The view's title row holds the context: Workflow picks the workflow that prices the comparison (pass-yield by default), Scope narrows the figures to a ground station, antenna or satellite, and Window is the next 12, 24, 48 or 72 hours. Share copies the link or the API call behind the view.
Make a scenario
+ New scenario opens a form, filled with the likeliest what-if: the busiest ground station in the window taken down, and named for its changes, so Save and price is one click.
| Part | What it changes |
|---|---|
| Name | Follows the changes until you type one |
| Ground stations down | Every antenna at each ticked station is out |
| Weather, Heavy rain | The 1-in-10 wet case at every ground station (weather_quantile: p90 in the API) |
| New antennas | Add an antenna, then pick its Ground station: the antenna takes that station's band, minimum elevation, dish, receive range and G/T, and the next free id (troll-2), all of which you can change. It joins the name once it has a ground station |
| New satellites | Add a satellite: its Satellite id, its orbit from a NORAD id or Two TLE lines, Band, Carrier in GHz, Bandwidth in MHz and EIRP |
Compare with live
Choose a scenario (?scenario=<id>) and the middle pane compares it with live. When a run is missing it says which and offers to run it: Run this scenario over the next 48 hours, or Price live over the same window (a test run of live). Both deliver nothing.
| Card | Shows |
|---|---|
| Expected | The scenario's expected GB over the window, and the change against live |
| Passes | The passes expected to deliver in the scenario, and how many are lost and gained: live's count, less those lost, plus those gained |
| Could fail | Passes whose low case is 0 GB in the scenario, and the change against live |
Under the cards, Lost and gained passes is a timeline with a row per ground station and a lane each for lost and gained; List shows them as rows instead. A pass is lost when it is in live and gone, or expected to deliver nothing, in the scenario.
The right pane, Scenario, opens with one sentence on what the scenario changes and what that does against live ("Awarua down costs 3.1 GB against live: 4 passes lost, 1 gained."; before both runs are read, that it is not priced over the window yet). Under it, what the scenario changes as label and value (Ground station down, Rain, New antenna, Extra fade), when it was made, the workflow it is priced with and the window. Under it, Lost and Gained list each pass with its time and expected GB, and Ground stations each station's passes and expected GB with the change against live. Escape or the close button clears the choice.
When it is refused
| On screen | Why | Do this |
|---|---|---|
| This workflow cannot price a changed network yet | The workflow asks a served model for a lane that cannot price a changed network | Pick a physics-only workflow in Workflow |
| A ground station or antenna the config does not hold, or an id it already has | The network config changed since the scenario was made (422 unknown_stations, antennas_exist or satellites_exist) | Make a new scenario |
403 plan_required | On Explore, a run covers at most 2 satellites, scenario runs included | Price the window on Passes first, or upgrade |
In the API
| On screen | Call |
|---|---|
| Models | GET /catalog/models |
| Scenarios, Save and price | GET and POST /topology/scenarios |
| A scenario run | POST /predictions with scenario_id; it never delivers |
| Live over the same window | POST /predictions with "deliver": false |
| The comparison | GET /predictions?workflow=<slug>&scenario_id=<id> against GET /predictions?workflow=<slug> |