Reports and Visualization¶
ASTROLAB report and graph workflows consume structured analysis payloads. The goal is to avoid hard-coded report logic and allow each analysis family to expose its own templates and plotting helpers.
Result Flow¶
flowchart TD
A["Analysis Service"] --> P["Payload"]
A --> S["Summary"]
P --> H["Helper functions"]
S --> T["Report templates"]
H --> G["Graphs"]
T --> R["Formatted report"]
G --> E["Exported figures"]
Report Principles¶
| Principle | Description |
|---|---|
| Structured inputs | Reports should read from payload and summary, not recompute analysis. |
| Clear alignment | Tables should align labels and values consistently. |
| Analysis-specific context | Coverage, link, power, and lifetime reports need different sections. |
| Export-ready plots | Light and dark plot themes should be selectable depending on UI or document export. |
Plot Themes¶
ASTROLAB has a centralized plot theme module with dark and light themes. The dark theme is suited for the desktop UI. The light theme is better for export to PDF, Word, or external documents.
Typical Outputs by Analysis¶
| Analysis | Typical plots |
|---|---|
| Coverage | Heat map, access duration by point, points with/without coverage. |
| Link | Contact intervals, range, elevation, off-boresight, link margin. |
| Power | Solar power, load power, net power, SOC, deficit, eclipse state. |
| Lifetime | Altitude, perigee/apogee, SMA, eccentricity, inclination, density, F10.7, re-entry markers. |
| Path | Active strands, hop counts, route availability. |
Best Practices¶
- Keep raw numerical results in payloads.
- Keep report formatting in templates.
- Keep plot data extraction in helpers.
- Use light theme for exported documentation and dark theme for the UI.
- Include assumptions and units in every report section.