OrbitalPV
Open-source full-stack lab for spacecraft photovoltaic performance analytics: PV physics, orbit/Sun geometry, real spacecraft data connectors, degradation/anomaly analytics, reproducible research labs, and a web application platform.
The structure follows a modular separation-of-concerns approach: domain models, physics engines, connectors and analytics are independent workspace packages with consistent quality tooling.
Install from PyPI
python -m pip install orbital-pv
Use the public API as:
import orbitalpv as opv
positions_m = opv.circular_orbit_positions_m(
altitude_m=550_000.0,
inclination_deg=51.6,
)
g_am0 = opv.am0_irradiance(opv.ASTRONOMICAL_UNIT_M)
Optional extras:
python -m pip install "orbital-pv[examples]"
python -m pip install "orbital-pv[orbit]"
python -m pip install "orbital-pv[full]"
Foundation stack
- pvlib — tested PV equations and I-V/single-diode reference models behind a space-specific adapter.
- Skyfield + python-sgp4 — Earth-orbit catalog propagation from CCSDS OMM/TLE.
- Astropy — time, units, frames and baseline solar-system coordinates.
- SpiceyPy / NASA SPICE — mission-grade ephemeris, attitude, clocks and frame transforms.
- SpacePy / later radiation engines — radiation/environment workstream.
- HTTP connectors — CelesTrak, Space-Track, NASA SSCWeb, NAIF, CDAWeb/HAPI, NOAA SWPC, SatNOGS DB and BIRDS EPS.
poliastro is intentionally not a core dependency because its upstream repository is archived.
Repository map
orbital-pv/
├── src/orbitalpv/ # public PyPI API
├── apps/
│ ├── space-pv-cli/
│ ├── space-pv-api/
│ └── space-pv-web/
├── packages/
│ ├── space-pv-core/
│ ├── space-pv-orbit/
│ ├── space-pv-pvmodel/
│ ├── space-pv-space-env/
│ ├── space-pv-connectors/
│ ├── space-pv-analytics/
│ ├── space-pv-storage/
│ └── space-pv-orchestration/
├── examples/
├── labs/
├── data/{raw,bronze,silver,gold}/
├── docs/
└── tests/
The space_pv_* packages remain available as lower-level implementation modules for contributors and advanced use, while orbitalpv is the stable user-facing import.
Documentation
https://julianascencio.github.io/orbital-pv/
The documentation uses Sphinx, PyData Sphinx Theme, and Sphinx-Gallery. Gallery examples execute during the documentation build and use the same orbitalpv API installed from PyPI.
Build locally:
make docs
Development
uv sync --all-packages --group dev --group lab --group orbit --group pv --group space --group app
uv run pytest
uv run ruff check .
uv run ty check
Science pipeline
real orbit/telemetry/environment data
|
v
canonical time + frames
|
+---------+----------+
| |
orbit + Sun PV telemetry
| |
v |
eclipse + AOI + AM0 |
| |
+----------+---------+
v
expected PV performance
|
v
residual / degradation
|
v
anomaly + EOL analytics
See docs/foundation_stack.md, docs/connectors/catalog.md, docs/architecture.md and docs/state_of_art.md.
Application platform
The web/application layer is intentionally separated from the scientific packages:
- React + TypeScript + Vite — frontend application.
- FastAPI — API and job submission boundary.
- PostgreSQL — durable multi-user/transactional application state and job metadata.
- DuckDB — local analytics, parquet-backed research datasets and fast time-series exploration.
- Celery + Redis — long-running ingestion, orbit, PV and analytics jobs.
- Flower — local Celery worker/task observability.
Start the development stack with:
docker compose up --build
Then open React on http://localhost:5173, FastAPI docs on http://localhost:8000/docs, and Flower on http://localhost:5555.
Space GIS and dynamic visualization
The platform separates scientific orbital reference-frame state from Earth-fixed GIS render products. PostGIS serves hot satellite positions, ground tracks, stations and footprints; DuckDB/Parquet retain analytical history and chart rollups; CesiumJS renders time-dynamic 3D orbital scenes. See docs/space_gis_and_visualization.md.
Literature library
A curated, source-tagged literature library is maintained in docs/literature/. It covers the 2026 state of the art in space-PV cells and arrays, mission-aware performance modelling, radiation/degradation, digital twins, telemetry/AI, and open flight datasets/APIs.
Roadmap evidence
docs/literature/09_ieso_2026_workshop_roadmap.md— 2026 IESO workshop targets translated into repository features and R&D priorities.docs/product_feature_roadmap.md— prioritized product epics derived from the literature and 2026 IESO workshop.
Metadata
Release files for orbital-pv 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| orbital_pv-0.3.0.tar.gz | 35.2 kB | Without provenance | Details for orbital_pv-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| orbital_pv-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for orbital_pv-0.3.0-py3-none-any.whl |
Total release size: 75.9 kB
Release files / orbital_pv-0.3.0.tar.gz
| Download URL | orbital_pv-0.3.0.tar.gz |
|---|---|
| Size | 35.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f0f4e82679722560b001cb85913c6ea5cc5e3f90397926c2710ca3960425d15d
|
|
BLAKE2b-256 checksum How to use checksums |
2765acd1b7bf22c4da942ddce498b1ea903c55eb37d8af20f6891fa9686c7810
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / orbital_pv-0.3.0-py3-none-any.whl
| Download URL | orbital_pv-0.3.0-py3-none-any.whl |
|---|---|
| Size | 40.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
05292ad57a51cc8d56bd3cef8ad1c81030c8000562de67d915ea30d34df60a01
|
|
BLAKE2b-256 checksum How to use checksums |
d2d019085af0b0ed03563921ade41778ea893b5a5c6542c0ede089871e198306
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for orbital-pv 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.