Examples¶

Astraeus includes 20 editable engineering examples covering propagation, coverage, communications, routed service, attitude, power, propulsion, grouped studies, and deployment campaigns. They use the same RunSpec and artifact contracts as your own studies.

Every example has a stable reference from EX01 through EX20 and a guide organized as purpose → setup → RunSpec focus → results → interpretation. Use the reference when discussing a case or recording a derived study.

Each guide also identifies the primary saved artifacts behind its conclusions. Tables, maps, and plots on the richer examples are recreated from those artifacts and illustrate the result you should expect to reproduce in the Console, a scenario report, or your own analysis notebook.

flowchart LR COPY["Copy the packaged resources"] --> CHOOSE["Choose the closest engineering question"] CHOOSE --> PLAN["Validate or plan the input"] PLAN --> RUN["Run and monitor"] RUN --> REVIEW["Inspect artifacts, plots, and Console views"] REVIEW --> ADAPT["Change one assumption and compare"]

Start From An Editable Copy¶

List the installed resources and copy them into a workspace:

astraeus resources list
astraeus resources copy astraeus-resources

The example inputs are under astraeus-resources/examples/user/. Reusable component, communications, and geography profiles are included in the same resource copy, so relative imports remain portable when the workspace moves.

For a first core run:

astraeus run \
  astraeus-resources/examples/user/first-orbit.yaml \
  --run-id first-orbit

Follow it in another terminal and then open the completed evidence:

astraeus monitor serve --runs-root runs
astraeus console --runs-root runs

Choose A Learning Route¶

Goal	Recommended route	Next page
Learn the core workflow	Orbit → ground access → regional coverage	EX01 · First Orbit
Study communications	Service downlink → multibeam steering → ISL routing → beam hopping	EX05 · Service Downlink
Couple spacecraft models	Finite slew → power balance → observation delivery → finite propulsion	EX10 · Finite-Slew Attitude
Interpret one coupled system	Run the 48-satellite regional service case from input through power results	EX16 · Integrated Study
Compare architectures	Use a sweep for parameterized variants or a batch for explicit cases	Complete catalog
Compare network topology	Hold the network inputs fixed and remove cross-plane links	EX20 · Polar Mesh Topology Trade
Compare deployment strategies	Hold the target fixed and change the delivery orbit	EX19 · Deployment Strategy Comparison
Exercise large constellations	Run the two 1,584-satellite qualified workloads on a suitable server	Large-scale showcases

The complete catalog represents every packaged example once and links to all 20 guides. It also summarizes workflow type, scale, runtime tier, main evidence, and useful review surfaces.

Commands By Workflow¶

RunSpec examples use the core command:

astraeus run astraeus-resources/examples/user/regional-coverage.yaml

Grouped and campaign examples use their matching interface:

astraeus sweep plan astraeus-resources/examples/user/altitude-trade-sweep.yaml
astraeus sweep run astraeus-resources/examples/user/altitude-trade-sweep.yaml --workers 2

astraeus batch plan astraeus-resources/examples/user/architecture-comparison-batch.yaml
astraeus batch run astraeus-resources/examples/user/architecture-comparison-batch.yaml --workers 2

astraeus campaign-plan validate \
  --input astraeus-resources/examples/user/deployment-campaign.yaml
astraeus campaign-plan run \
  --input astraeus-resources/examples/user/deployment-campaign.yaml

Use astraeus run ... --dry-run for an individual RunSpec. Planning a sweep or batch materializes its cases before execution, which is useful when reviewing imports, output locations, and worker counts.

Runtime Tiers¶

The catalog uses relative tiers to help choose a suitable first case:

Tier	Reference expectation
Quick	Normally within about 15 seconds on a qualified local system
Standard	Normally within about 90 seconds
Extended	Richer or grouped studies, normally within about 5 minutes
Showcase-scale	Qualified server workloads of 10 minutes or more

Runtime varies with platform, storage, worker count, and requested output detail. The two showcase cases also write more than a gigabyte of evidence; review their measured resource envelopes before execution.

Turn An Example Into A Study¶

Keep the original copied input, create a named variant, and change one engineering assumption at a time. Give every execution a meaningful run ID and retain its manifest alongside any derivative review:

astraeus review run \
  --run-dir runs/core/my-run \
  --output runs/core/my-run/run-review.md

astraeus report scenario \
  --run-dir runs/core/my-run \
  --output runs/core/my-run/scenario-report.md

The RunSpec reference defines the configurable fields, while Understanding Outputs explains the saved evidence. Using AI Skills shows how the packaged assistants can help select, adapt, execute, and interpret an example.