Orbit and Sun Geometry#
Spacecraft PV performance begins with geometry. OrbitalPV keeps propagation, reference frames, Sun position, eclipse state, and panel incidence separate so that each step can be validated independently.
Propagation engines#
For public Earth-orbit catalog objects, the default path is Skyfield with the Vallado SGP4 implementation. New catalog ingestion should prefer CCSDS OMM records where available.
For missions that publish SPICE kernels, SpiceyPy provides the higher-fidelity path for ephemeris, frames, clocks, and attitude products.
Sun geometry#
The core geometry state is the spacecraft-to-Sun vector:
The incidence factor for a panel normal \(\\mathbf{n}\) is initially represented by:
Eclipse#
OrbitalPV includes an Earth-disc/Sun-disc occultation calculation that returns a continuous illumination fraction between 0 and 1. This supports sunlight, penumbra, and umbra rather than reducing eclipse to a Boolean too early.
Frame discipline#
Do not store an inertial vector as longitude/latitude geometry. Scientific states must retain their frame and epoch. Earth-fixed GIS products are derived later for visualization and spatial queries.
Visualization examples#
The Example Gallery includes several offline orbit visualizations:
Representative Earth orbit families compares representative LEO, polar/SSO-like, MEO, and GEO circular orbits around Earth.
Molniya-style highly elliptical orbit shows a representative highly elliptical Molniya-style orbit.
Earth-fixed ground track transforms an inclined inertial orbit into an Earth-fixed ground track and handles the antimeridian discontinuity.
These examples use deterministic geometry for documentation. Operational analysis should use traceable orbital elements or mission ephemerides.
Constellation examples#
The Imaging and space-computing constellations guide links published mission geometry to viewing conditions, eclipses and illustrative power budgets. The gallery includes:
GEO weather imagers: surface-irradiance coverage and spacecraft solar power compares selected GOES, Meteosat and Himawari viewing geometry and eclipse seasons.
Sentinel-2 polar imaging and solar-power geometry shows the nominal Sentinel-2B/2C pair, ground tracks and illumination.
Space data centers: orbit, eclipse seasons, and power balance compares Suncatcher- and ASCEND-motivated orbital scenarios with seasonal shadow, finite-Sun penumbra and a declared load/storage budget.
Compact orbital compute clusters and distributed power distinguishes compact-cluster eclipses from staggered eclipses in a hypothetical ring and keeps local power deficits separate from fleet sums.
Starlink Gen1 shell solar generation models the FCC-authorized 1,584-spacecraft, 550 km, 53° Starlink Gen1 shell and computes fleet illumination and illustrative solar generation over one orbit.
The Starlink orbital geometry follows the public FCC authorization. Electrical power assumptions in all examples are explicitly illustrative.