Skip to content

Release Notes

This page defines the release note format for ASTROLAB. It should be updated at each internal milestone so users can understand which capabilities are available, which behaviours changed, and which limitations remain.

Current Beta Capability Snapshot

Area Status Notes
Spacecraft assets Active Orekit-backed state queries, propagation configuration, attitude handling, mesh metadata, constraints, and visualization support.
Facilities and targets Active Static geodetic assets with ENU attitude and frame-aware position queries.
Sensors Active Conical and rectangular FoV definitions with footprint support.
Antennas Active Mounted RF antennas with radiation pattern models and gain sampling utilities.
Transmitters and receivers Active Schema-driven RF parameters, unit conversion, antenna linkage, and link budget integration.
Solar arrays Active Mounted panel geometry, optional Sun tracking, incidence angle, and generated power estimation.
Batteries Active Capacity, SOC limits, charge/discharge efficiencies, voltage limits, and power limits.
Coverage analysis Active Grid generation, access computation, coverage intervals, scalar fields, and heat-map-ready outputs.
Link analysis Active Pairwise access intervals, optional geometry generation, and RF link budget integration.
Power analysis Active Solar generation, loads, eclipse state, net power, battery SOC, and deficit tracking.
Lifetime analysis Active DSST-based long-term decay workflow, atmosphere models, solar activity scenarios, and lifetime plots.
Path analysis Early Configuration model exists for graph-style connectivity and optimal strand analysis.
Reporting and plots Active Template-driven reports and analysis-specific plot helpers.

Release Note Template

Use the following structure for future releases:

## ASTROLAB x.y.z

### New Capabilities

- Added ...

### Improvements

- Improved ...

### Fixes

- Fixed ...

### Known Limitations

- ...

### Migration Notes

- ...

Known Beta Limitations

  • Some advanced analysis workflows are still evolving and may change data schemas.
  • Lifetime analysis should be interpreted as an engineering estimate rather than a certified re-entry prediction.
  • RF link budgets use first-order engineering models and depend strongly on correct antenna, transmitter, and receiver configuration.
  • Documentation navigation may need to be updated in mkdocs.yml when new pages are added.