Open MCT
The Constellation Forecast plugin shows workflow forecasts inside Open MCT: a Constellation Forecast folder with an overview, one view per workflow (summary tiles, charts per template, swaps to decide, results and the ledger per pass), and each workflow's passes as an Open MCT Plan you can put in a Time Strip beside your own telemetry.
It reads forecasts from one of two sources:
| Source | Reads | Needs |
|---|---|---|
api | The workflow results feed, straight from the Constellation API, as the connection openmct | A live key with only the results:read scope |
yamcs (the default) | What the Yamcs bridge writes, through the Yamcs your Open MCT already uses | The Yamcs connector; no Constellation key and no new connection |
With the Yamcs source, the /ConstellationForecast/* parameters also appear in openmct-yamcs's tree like any other telemetry, with or without the plugin.
Install
-
Download
constellation-openmct.jsfrom Downloads and copy it next to your Open MCTindex.html. -
Load it and install it, with no rebuild:
<script src="constellation-openmct.js"></script><script>openmct.install(ConstellationForecast({ source: 'api', token: '<key>' }));</script>Or, with Yamcs and its bridge already in place, read from Yamcs instead and keep the key out of the browser:
openmct.install(ConstellationForecast({ yamcsUrl: location.origin + '/yamcs-proxy/' }));yamcsUrlis required: the base your Open MCT page reaches Yamcs's HTTP API through, such as the/yamcs-proxy/openmct-yamcs serves. The plugin sends no credentials. Stock Yamcs does not answer a page on another origin, so either pointyamcsUrlat a proxy on the page's own origin, as above, or let Yamcs answer your Open MCT inetc/yamcs.yaml:services:- class: org.yamcs.http.HttpServerargs:cors:allowOrigin: "https://<your Open MCT>"allowCredentials: falseThe plugin installs Open MCT's Plan and Time Strip plugins if they are not installed already.
-
Reload Open MCT. Constellation Forecast appears at the top of the tree. Forecast passes are in the future: set the time conductor's end offset ahead (for example +24 hours) to see them in a Time Strip.
For the api source, create a live key with only results:read. It reads the results feed (GET /predictions/feed) and nothing else, so the page can hold it. The plugin sends it as x-api-key, never with cookies, reads only the newest run of each workflow, 20 runs a page, and backs off on its own when the API answers 429. After a 401 or 403 it stops asking and says how to fix the key. apiUrl sets an enterprise API (default https://api.constellation.space), and consumer another connection name (default openmct); a workflow's mission control output names it.
Tested with Open MCT 4.3.1.
How it fails
- openmct-yamcs from
masterdoes not build. It needs Node 24 and Open MCT's development build. Use its v4.0.0 release with Open MCT 4.0.0 on Node 20, installed withnpm install(it ships no lockfile). 403 insufficient_scopein the browser console. The key lacksresults:read. Create a live key with that scope.- The tree is empty. openmct-yamcs's example is written for an instance called
myprojectatlocalhost:9000. Change its instance, folder and proxy addresses together.