EX12 — Power Sizing¶
Tags: power · sizing variants · frozen driver
Input: power-sizing.yaml · Runtime tier: standard · Recommended views: Power, Analysis
Purpose¶
Compare solar-array and battery changes against the same frozen power driver so generation and storage trades remain directly comparable.
Setup¶
A single satellite runs for 24 hours with a deliberately undersized baseline. Three variants change array area, battery capacity, or both.
astraeus run astraeus-resources/examples/user/power-sizing.yaml
RunSpec Focus¶
Sizing variants are local overrides on one baseline. This preserves the orbit, attitude, load, initial state, and cadence across every comparison.
power:
sizing:
enabled: true
variants:
- id: larger-array
overrides: {power: {panel_area_m2: 0.5}}
- id: larger-battery
overrides: {power: {battery: {capacity_wh: 900}}}
- id: larger-array-and-battery
overrides:
power: {panel_area_m2: 0.35, battery: {capacity_wh: 900}}
Results¶
The reference run completed successfully in 0.42 seconds and evaluated all three variants. The baseline was infeasible. The larger battery still fell below the 25% minimum (21.26%); the larger array reached the 100% upper boundary. The combined variant remained between 64.70% and 72.23% and was feasible.
Artifacts To Inspect¶
| Artifact | What it shows |
|---|---|
power/sizing/sizing_summary.json |
Variant status and the location of each result bundle |
power/power_summary.json |
Baseline state-of-charge range and infeasibility |
power/sizing/<variant>/power_summary.json |
Comparable feasibility and energy rollups for each variant |
power/sizing/<variant>/timeline_power.parquet |
Variant-specific generation, load, and state-of-charge timeline |
Interpretation¶
More generation and more storage solve different problems. Array-only sizing can trade energy deficit for excess generation, while storage-only sizing cannot fix a persistent generation shortfall. The balanced variant closes both sides of this particular energy cycle.