Console And Visualization

The Astraeus Console is the packaged local interface for configuring supported constellation studies, validating and launching runs, and exploring completed artifacts in synchronized 2D, 3D, and engineering views.

Launch it with:

astraeus console

The command starts the local Console service, opens a browser, and serves the web application and API together. By default it binds to 127.0.0.1:8765 and uses .astraeus_console/ as its editable workspace.

Where The Console Fits

CLI and RunSpec remain the complete user interfaces. The Console provides a broad, deliberately bounded subset for visual configuration and review:

Workflow	Console support
Configure a constellation	Walker, Streets of Coverage, and explicit layouts; orbit, ground sites, and supported module controls
Import a RunSpec	imports and preserves a RunSpec; supported fields are editable through controls
Validate and launch	local validation, execution, status, and logs
Open completed runs	read-only browsing within configured run roots
Geometry review	synchronized 2D ground track, 3D orbit, access, sites, regions, and timeline
Spacecraft review	attitude/platform 3D and power results when artifacts exist
Analysis	ground access, coverage, and ISL-access views when artifacts exist

Advanced service, observation, routed transport, beam-hopping, grouped-study, and campaign authoring remain CLI/RunSpec workflows. Their completed core-run artifacts may still expose supported geometry or spacecraft views. Advanced result tables and configuration fields remain in the CLI and saved artifacts.

Configure And Launch

The normal Console workflow is:

1. load a curated Console example, import a RunSpec, or create a design;
2. edit the supported configuration fields;
3. validate and review the RunSpec preview;
4. launch the local run;
5. follow status and logs in the Console drawer;
6. inspect the panes enabled by the resulting artifacts.

Configuration, RunSpec preview, validation, and launch stay in one local workspace. A successful launch loads the available result panes automatically.

Module controls cover propagation plus supported attitude, power, ground access, coverage, and ISL-access configuration. Controls appear only when their module is enabled. Imported fields outside the polished form surface remain in the RunSpec but should be edited through the normal text-based RunSpec workflow.

Open A Completed Run

Expose one or more run roots when launching the Console:

astraeus console --runs-root runs

Repeat --runs-root to expose another approved location. In the Console, select Open existing run, choose a configured location and completed run, then select Open run.

The Console opens completed bundles read-only from the locations selected at startup and leaves their artifacts in place.

The run needs a current completed-run contract and at least one result supported by the Console. Missing pane buttons normally mean that the run did not produce the required artifact family or that the feature has no Console view yet. Compatibility of saved runs and Console workspace state across supplied releases follows Compatibility And Upgrades.

Resume After A Console Interruption

Restart the Console with the same --workspace-root. At startup it reconciles Console-launched jobs that were still pending or running. When a job-owned directory contains one complete terminal run artifact, the Console restores the matching succeeded or failed result and preserves its RunSpec, log, and artifacts. Other nonterminal jobs close as failed with an interruption reason. A job closed because no terminal artifact existed remains eligible for another check on a later Console startup, in case its external process finishes after the first restart.

This recovery is deliberately conservative. Check the Run Monitor and the host process state before rerunning work, because Console startup records durable artifact state rather than taking control of a calculation that may still be running outside the restarted Console process.

Explore The Shared Timeline

All scene-backed views share satellite/site selection and a common time position. Use play, pause, step, scrub, playback-rate, and loop controls to relate geometry and subsystem results at the same sample.

The 2D view combines ground tracks, current satellite positions, ground sites, regions, and available access overlays.

Pane	What it shows
2D	ground tracks, sites, regions, access overlays, and current state
3D	Earth, orbital trajectories, current satellites, sites, and links
Access	ground-access, coverage, or ISL-access evidence available in the bundle
Platform 3D	spacecraft attitude and platform geometry
Coverage	artifact-backed coverage summaries and spatial results

The 3D and 2D views use the same propagated state source and timeline, keeping selection and playback consistent.

Console, Monitor, Review, Or Report?

Need	Use
configure or visually inspect one supported local run	astraeus console
watch active core, sweep, or batch progress	astraeus monitor serve
produce a compact deterministic markdown assessment	astraeus review
produce a decision-level scenario report and curated plot pack	astraeus report scenario
author or execute the complete feature set	CLI and RunSpec

The Console and Monitor are read-only with respect to completed run artifacts. Review and report commands create derivative files while leaving the underlying result bundle unchanged.

Launch Options

astraeus console \
  --host 127.0.0.1 \
  --port 8765 \
  --workspace-root .astraeus_console \
  --runs-root runs

Use --no-browser when opening the URL yourself. The Console is designed as a local single-user tool; keep its run roots and bind address limited to locations and networks appropriate for the data being reviewed.

Current Limits

• RunSpec authoring and advanced configuration remain CLI/file-based workflows.
• Playback uses loaded samples rather than interpolating high-rate state.
• Scene payloads are bounded and may be decimated for larger runs.
• ISL visualization covers access/topology; detailed routed-service analysis remains artifact/report driven.
• Campaign execution and results use the dedicated campaign workflow, outside the Console.
• This local Console covers single-user execution and artifact review; distributed queues and multi-user ownership require separate infrastructure.

For the durable result structure behind every view, see Understanding Outputs.