Skip to main content

Connect Yamcs, COSMOS or Lattice to forecasts

Operators already have a screen they trust. A forecast that lives in another tab gets ignored, so Constellation puts its results inside the mission control system you run: as events, timeline items, parameters, packets or map layers, labelled as forecasts.

What appears where​

SystemWhat operators seePlan
YamcsEvents per pass, timeline bands, parameters with alarms, and a Constellation Forecast pageOperator
Open MCTA Constellation Forecast folder with a view per workflow, and passes as Plans for Time StripsOperator
OpenC3 COSMOSA CONSTELLATION target for Limits Monitor and Grapher, and a Constellation Forecast toolEnterprise
Anduril LatticeForecast services that decide ReservePass tasks, forecast passes along their ground tracks, and rain-fade alertsEnterprise
Your own systemWhatever your system holds: you write one function, the template does the restOperator

How it works​

  1. A workflow gets a mission control output naming a connection, such as yamcs-bridge.
  2. When a run finishes, its results for that connection go on your account's workflow results.
  3. The bridge for that connection, running in your network, pulls its workflow results outbound over HTTPS and writes the results into your system.
  4. The bridge reports what it wrote, and the workflow builder shows the connection as live.

The rules every connector keeps​

  • Pull, never push. Nothing connects into your mission control. The bridge holds your system's credentials, which Constellation never sees, and an API key that reads results and checks in (predictions:read; Lattice also config:read for your antennas).
  • Propose, never schedule. A forecast pass is never written as a scheduled contact, and a rain-fade swap is advice for an operator.
  • Never over your data. Forecasts go into objects of their own, such as Yamcs parameters under /ConstellationForecast/ or a CONSTELLATION target in COSMOS.
  • Reruns update in place. Results are keyed by pass, so a new run updates what it wrote instead of adding a copy.

Full detail, install steps and versions are in Connectors, and the wire format in the results protocol.

Common questions​

Does a connector need inbound access to my network?

No. The bridge runs in your network and calls Constellation outbound over HTTPS. Nothing connects into your mission control system.

Will forecasts overwrite my schedule or telemetry?

No. Connectors write forecasts, labelled as forecasts, into objects of their own. They stop updating a forecast once an operator has scheduled or otherwise taken it over.

Which versions of Yamcs, COSMOS and Open MCT are tested?

Yamcs 5.14.0 and 5.13.7, and Open MCT 4.3.1, each in CI against a stub Constellation API. The COSMOS plugin is built and its bridge unit tested but not installed into a COSMOS, and the Lattice bridge runs against a stub of the Lattice routes it calls. The connectors repository's README lists each release under Compatibility.

Are the connectors open source?

Yes, under the Apache License 2.0. Yamcs, OpenC3 COSMOS, Open MCT and Anduril Lattice are their owners' products, under their own licenses.

Next: test a workflow on the demo fleet to see the results a bridge would write, before you install one.