Skip to content

First Campaign Run

This walkthrough plans a six-spacecraft deployment from direct insertion into a two-plane target constellation. It introduces campaign validation, execution, and result review before the broader delivery-strategy trade in EX19.

It uses the packaged resources copied in the first core run:

astraeus-resources/examples/user/deployment-campaign.yaml

1. Understand The Question

The request asks how six spacecraft acquire three evenly spaced slots in each of two 550 km, 53-degree planes. It defines:

  • two direct-insertion assets, one for each plane
  • two groups of three identical electric-propulsion spacecraft
  • six explicit spacecraft-to-slot assignments
  • a bounded slot-acquisition policy with a 2 km stationkeeping handoff
  • campaign duration and event limits
flowchart LR REQUEST["Deployment request"] --> VALIDATE["Validate inputs"] VALIDATE --> PLAN["Plan six missions"] PLAN --> ACQUIRE["Acquire assigned slots"] ACQUIRE --> RESULT["Review readiness and burden"]

2. Validate The Request

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

Validation checks the request and prints its resolved path. Execution begins only with the run subcommand.

3. Run The Campaign

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

The request's campaign_id determines the default result path:

runs/campaign/deployment-comparison-dedicated/campaign_plan_result.json

The result includes the resolved input under request_snapshot.

4. Review The Result

The packaged request reaches all six target positions. The reference execution calculated 131.8 m/s total spacecraft delta-v, 1.21 kg propellant, and 120.6 hours to final assigned-slot readiness. Read these sections first:

Section Review question
status and campaign_summary.status_class Did the campaign achieve its objective?
summary How many spacecraft were assigned, how long did readiness take, and was the target achieved?
campaign_summary.target_summary Which target positions were achieved and are any residual constraints reported?
campaign_summary.mission_burden_summary What fleet delta-v, propellant, and mission duration were calculated?
assignments Which asset, plane, and slot was selected for each spacecraft?
events How was the campaign sequenced?
missions What burden was calculated for each spacecraft?

Generate a readable deterministic review:

astraeus review campaign \
  --result runs/campaign/deployment-comparison-dedicated/campaign_plan_result.json

Add --output campaign-review.md to save it.

5. Optional Mission Artifacts

The default summary detail keeps the result compact. Rerun with full mission artifact persistence when spacecraft-level run bundles are needed:

astraeus campaign-plan run \
  --input astraeus-resources/examples/user/deployment-campaign.yaml \
  --mission-artifact-detail full

The main campaign result remains the primary artifact in either mode.

Troubleshooting

Symptom Check
The request cannot be found Confirm the packaged resources were copied and use the path shown above.
The result reports a residual target Inspect target_summary, mission burden, and event reasons before changing the request.
The output is in a different directory Check campaign.campaign_id, or use --output to choose an explicit result path.
Mission side bundles are absent Use --mission-artifact-detail full; the default is summary-only.

Next Steps