EX18 — Architecture Comparison Batch¶
Tags: batch · architecture comparison · Arctic coverage
Input: architecture-comparison-batch.yaml · Runtime tier: extended · Interface: CLI
Purpose¶
Compare three structurally different constellation architectures over the Arctic without forcing them into a single parameterized template.
Setup¶
The batch names explicit polar Walker, Streets of Coverage, and Molniya child RunSpecs. Every case runs for 24 hours and emits the same coverage KPIs.
astraeus batch run \
astraeus-resources/examples/user/architecture-comparison-batch.yaml
RunSpec Focus¶
A batch is appropriate because constellation kind, orbital regime, satellite count, and layout all differ. The common summary contract creates a comparable table while preserving each case's complete input.
batch:
cases:
- label: polar-walker
runspec: cases/architecture-polar-walker.yaml
- label: streets-of-coverage
runspec: cases/architecture-streets-of-coverage.yaml
- label: molniya
runspec: cases/architecture-molniya.yaml
Results¶
All three reference cases succeeded in 16.39 seconds. Area-weighted Arctic coverage was 71.03% for the 24-satellite polar Walker, 98.34% for the 66-satellite Streets of Coverage design, and effectively 100% for the six-satellite Molniya design over the sampled day.
Artifacts To Inspect¶
| Artifact | What it shows |
|---|---|
batch_plan.json |
The three independent child RunSpecs and stable case identifiers |
batch_summary.json / .csv |
Architecture label, satellite count, coverage, runtime, and status |
batch_results.json |
Completion and failure state plus child-run locations |
cases/.../runspec.json |
Fully resolved input for each structurally different design |
Interpretation¶
The batch demonstrates architectural comparison, not an optimization ranking: the cases use different satellite counts and orbit types. Molniya's high- latitude dwell is visible immediately, while launch, radiation, latency, and spacecraft complexity remain separate decision dimensions.