Use Cases · Stellar Control

Each use case is a configuration repository that runs as it is: catalogues, a topology, every target simulated, procedures validated in stellar.lock, run requests. Explore it in your browser, run it in a trial environment of your own, or clone it and run it on your machine.

Use case	For	In five minutes
Payload integration	Subsystem integrator	From the supplier's ICD to a catalogue, a simulation and a driver; first light of the simulated camera
Satellite integration	System engineer, AIT manager	One topology for a 6U CubeSat over CSP; the same functional acceptance in SIM, on the flatsat and on the flight model
Test bench automation	Test engineer, test facilities	A TVAC cycle unattended; a vacuum leak, the chamber made safe, the report

The three tell one story: the camera integrated in the first is the payload of the CubeSat of the second, and the unit under test in the chamber of the third.

Three ways in#

In your browser, no account: the playground of the online trial opens the configuration of a use case, checks it as you type, and writes the simulation of a platform from its catalogue. See Playground.
A trial environment of your own: control.stellar-systems.eu, on a use case with #/new?usecase=<id>: a cell of Stellar Control with the configuration of the use case, its simulated equipment running, the web console and its editor, for a week. Its Getting started lists the next steps.

On your machine: install the CLI, clone the repository of the use case, then check it and run its demonstration on ephemeral simulated targets, with no server:

Shell

curl -fsSL https://get.stellar-systems.eu/install.sh | sh
git clone https://github.com/stellar-systems-eu/control-usecase-payload-integration
cd control-usecase-payload-integration
stellar check . --locked
stellar run --dry runs/first-light.yaml --repository . --report report.html

A dry run needs nats-server on your PATH (or --nats-server): see Dry runs.

What a use-case repository holds#

text

packages/<platform>/catalogue.yaml   what the equipment is: components, measures, telecommands, alarms
packages/<library>/                  steps and procedures, validated in stellar.lock
topology.yaml                        environments (SIM, then the real ones), targets, links
simulations/*.yaml                   every simulated target, realistic: ramps, transitions, faults
runs/*.yaml                          run requests: the demonstration, the same on the real targets
template.yaml                        what the online trial shows and runs first
icd/                                 the interface documents the catalogues come from
scripts/rebuild.sh                   checks, regenerates what follows the catalogues, validates

Each repository is published by tag; the online trial starts its environments from the tag the catalog of Stellar Systems pins (see Cells).