Skip to main content

OrbitalPV

ASVA Consulting

Created by ASVA Consulting
asvaconsulting.com
contacto@asvaconsulting.com

Created by ASVA Consulting, OrbitalPV is an 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.

AI-assisted development and literature basis

A substantial part of the code, documentation, examples, tests, and repository scaffolding in OrbitalPV is generated or drafted with AI assistance.

The scientific direction is not intended to come from unsourced model invention. Repository developers choose the specific papers, standards, datasets, technical reports, and other literature used to define the physical assumptions, reference values, methods, examples, and research roadmap. AI is then used to accelerate implementation, synthesis, documentation, testing, and iteration around that selected evidence base.

In practice:

  • source literature and technical references are selected by the repository developers;
  • model assumptions and numerical baselines should be traceable to cited literature, public datasets, or explicitly documented engineering assumptions;
  • AI-generated code and text are reviewed and tested where practical, but validation is still evolving and is not yet deep or comprehensive across all models and examples;
  • as with any AI-assisted work, generated code, explanations, parameter choices, or literature interpretations may contain mistakes and should be checked against the cited sources;
  • generated outputs should be treated as research and engineering work in progress rather than independently validated scientific truth;
  • for research, qualification, or mission-critical use, users should independently verify the underlying references, assumptions, numerical results, and validation evidence.

The curated evidence base is maintained in docs/literature/ and in the references attached to individual methods and examples.

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.

Creator and contact

OrbitalPV is created and maintained by ASVA Consulting.

Metadata

Release files for orbital-pv 0.4.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for orbital-pv 0.4.1
File Size Uploaded Provenance Actions
orbital_pv-0.4.1.tar.gz 42.8 kB Without provenance Details for orbital_pv-0.4.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for orbital-pv 0.4.1
File Interpreter ABI Platform Actions
orbital_pv-0.4.1-py3-none-any.whl Python 3 none any Details for orbital_pv-0.4.1-py3-none-any.whl

Total release size: 89.8 kB

Release files / orbital_pv-0.4.1.tar.gz

Download URL orbital_pv-0.4.1.tar.gz
Size 42.8 kB
Tags Source
SHA-256 checksum
How to use checksums
ce9e61cdf1f7922473ceb3f77021038b2acc4c78cca98521a688266fc3d45488
BLAKE2b-256 checksum
How to use checksums
5b083456ac3d3461ed899c9515e781160fec578154a42290eea9bad930023ad6
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.4.1-py3-none-any.whl

Download URL orbital_pv-0.4.1-py3-none-any.whl
Size 47.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7f8f2f6d4cb4c14acb1e9c2f4ea8d9850c9a09645c62998bb25267b7d0df67ec
BLAKE2b-256 checksum
How to use checksums
32e05d2106972e5ab71b31c38578017ec5a39f0494385e0104d3754f6d4532c4
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.4.1

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page