Package Overview#
OrbitalPV is a workspace rather than one large Python module. Each package has one primary responsibility.
Scientific packages#
space-pv-coreStable domain contracts and physical constants.
space-pv-orbitOrbit propagation adapters, attitude transforms, Sun geometry, incidence angle, and eclipse calculations.
space-pv-pvmodelSpace-specific PV modelling adapters. It reuses validated pvlib equations where appropriate without assuming a terrestrial PV system model is a spacecraft model.
space-pv-space-envAM0 irradiance and the evolving space-environment/radiation layer.
space-pv-connectorsExternal data adapters for orbital elements, mission ephemerides, space weather, and open spacecraft telemetry.
space-pv-analyticsSigned expected-versus-actual loss breakdowns, evidence-labelled categories, gap-aware energy accounting, performance normalization, degradation, persistent-loss, residual, and health analytics.
Platform packages#
space-pv-storageDuckDB analytics and PostgreSQL/PostGIS application persistence.
space-pv-orchestrationCelery task orchestration. Scientific packages do not depend on Celery.
Applications#
space-pv-cliCommand-line workflows and reproducible experiment entry points.
space-pv-apiFastAPI boundary for jobs, data products, and map-serving endpoints.
space-pv-webReact/Cesium frontend. This application is intentionally outside the Python workspace.
Design principles#
Physics before machine learning where a physical model is available.
Coordinate frame, time scale, unit, and source provenance are first-class.
Raw source data and derived scientific products remain separate.
Long-running orchestration stays outside scientific packages.
Flight-data analytics should compare measured power with expected physical power rather than relying on raw power thresholds alone.