OrbitsEdit on GitHubSource: docs/AGENCY-ORBIT-VALIDATION.md

Force-model validation by ephemeris fitting — methodology & validated residuals

Kshana's full-force engine (src/precise_od.rs) fit to real agency precise-orbit products, with honest, citable, commit-hash-stamped residuals. This is the validation record for roadmap milestone P4 ("Precise astrodynamics: high-order gravity, SRP (solar-radiation pressure), validation vs agency datasets").

What a validated residual means here#

A residual is reported only when all of the following hold (design docs/design/2026-06-09-precise-astrodynamics-design.md):

  1. Force model includes every perturbation that matters at the target accuracy: EGM2008 (Earth Gravitational Model 2008) high-degree geopotential (truncated at a stated degree/order, d/o), solid + ocean + atmospheric tides (src/tides.rs, IERS (International Earth Rotation and Reference Systems Service) Conventions 2010 Ch. 6), Sun/Moon third body, cannonball SRP with conical shadow + estimated C_R, drag (LEO (low Earth orbit) only), Schwarzschild + Lense–Thirring general relativity (GR) terms (src/forces.rs).
  2. Estimator is a real Gauss–Newton batch least squares with a variational state-transition matrix (cross-checked against whole-arc finite difference to < 1e-6), 1/σ² observation weighting, and n-sigma outlier editing.
  3. Frames/time use real IERS finals2000A Earth-orientation parameters (EOP) (UT1 (Universal Time 1, Earth-rotation time)−UTC (Coordinated Universal Time), polar motion; src/eop.rs) through the validated IAU (International Astronomical Union) 2006/2000A CIO (Celestial Intermediate Origin) chain (src/cio.rs). SP3 (Standard Product 3, the precise-orbit format) GPS (Global Positioning System) time → TT (Terrestrial Time) via the fixed 51.184 s offset (timescales::gps_to_tt).
  4. Residuals are reported in RTN (radial/along/cross-track) and 3-D, with and without empirical accelerations, alongside the raw (no-fit) overlap.
  5. Every number is reproducible (open-data CI (continuous integration) gate) and citable (commit hash + dataset reference + fixture SHA-256 (SHA: Secure Hash Algorithm)).

Method, per dataset#

  1. Parse the SP3 precise orbit; for the chosen satellite, take each ITRF (International Terrestrial Reference Frame) position fix.
  2. Convert the SP3 GPS epoch → TT; resolve (UT1, xₚ, yₚ) from finals2000A at that epoch.
  3. Rotate each ITRF fix into GCRS (Geocentric Celestial Reference System) through the CIO chain with those EOP — the inertial position observations. The dynamics use the same EOP for the geopotential's Earth-fixed rotation, so observations and forces share one frame.
  4. Seed the epoch state (position = first fix; velocity = 2nd-order finite difference) and batch-fit [r, v, C_R] (Tier 1), then additionally the 9 RTN cycle-per-revolution (CPR) empirical accelerations (Tier 2, a-priori constrained).
  5. Report post-fit RTN + 3-D RMS (root mean square) for both tiers and the raw overlap.

Results#

Galileo medium Earth orbit — GREEN (< 5 m bar)#

  • Dataset: ESA/ESOC (ESA: European Space Agency; ESOC: European Space Operations Centre) final multi-GNSS (GNSS: global navigation satellite system) orbit ESA0MGNFIN, ITRF, 5-min sampling, satellite E11 (GSAT0101, Galileo In-Orbit Validation (IOV), nominal MEO (medium Earth orbit)), 2022-01-01.
  • Open source (no login): ESA Navigation Office mirror, navigation-office.esa.int/products/gnss-products/2190/. EOP: IERS datacenter.iers.org/data/9/finals2000A.all.
  • Validation commit: 66da3ff (tests/agency_galileo.rs).
  • Fixtures (SHA-256): SP3 e7297f4c…d3a24a3; EOP 6b781d36…cb2ed00f (tests/fixtures/agency/NOTICE.md).
Run Arc d/o n_obs 3-D RMS RTN (R, T, N) C_R Notes
CI fixture, Tier 1 (force + C_R) 8 h 12 97 0.133 m 0.105, 0.067, 0.047 m 1.174 raw overlap 78.7 km
CI fixture, Tier 2 (+ empirical CPR) 8 h 12 97 0.070 m 0.048, 0.044, 0.027 m — halves the residual
Full-arc dispatch, Tier 1 (pre-fix†) 24 h 12 289 0.611 m 0.276, 0.381, 0.390 m 1.244 workflow_dispatch

The CI-fixture numbers above were re-recorded in 0.36 after the S2 air-tide fix (xval/s2-air-tide-fix/): Galileo Tier 1 moved 0.132 → 0.133 m (C_R 1.1744 → 1.1743), Swarm-A N components by 1–2 mm; the full-arc dispatch figures were not re-run. † Pre-fix: the full-arc dispatch figure was recorded before the 0.36 S2 air-tide fix and has not been re-run on the fixed code (the full-day products are fetched by the dispatch workflow, not available in the session that made the fix). On the CI fixtures the fix moved the Galileo 3-D RMS by under 1 mm and the Swarm-A components by 1–2 mm, so a change of the same order is expected; the next workflow_dispatch run re-records it.

The MEO field is gravity-converged by degree 8 (the 8 h Tier-1 result is identical at d/o 8, 10, and 12 to the millimetre), so the CI fixture's d/o-12 truncation is negligible; the dispatch job runs the full d/o-70. The 8 h fit reaches 13 cm pure-force and 7 cm with the empirical tier; the full 24 h arc (more SRP/eclipse stress, longer dynamic span) is 61 cm — all far inside the 5 m bar.

Swarm-A LEO — GREEN (< 5 m bar)#

  • Dataset: ESA Swarm Level-2 reduced-dynamic precise science orbit SW_OPER_SP3ACOM_2_ (RDOD_AR, GPS-derived, ITRF / IGb14, ~2 cm, Delft University of Technology processing), satellite Swarm-A (SP3 id L47, ~430 km LEO), 2022-01-01.
  • Open source (no login): ESA Swarm dissemination server https://swarm-diss.eo.esa.int/ → Level2daily/Latest_baselines/POD/RD/Sat_A/ (open under the ESA Data Policy). EOP: the same IERS finals2000A 2022-001 series.
  • Validation commit: ceea70a (tests/agency_swarm.rs).
  • Fixture (SHA-256): SP3 6cd84b78…acb733e (tests/fixtures/agency/NOTICE.md).

A LEO arc adds atmospheric drag to the force model. Because the density model is a static piecewise-exponential, the orbit is fit in two tiers: a dynamic tier (estimate the epoch state only; C_R held at 1, since at LEO drag dominates and SRP is poorly separable over a short arc), and a reduced-dynamic tier that adds the empirical cycle-per-revolution accelerations carrying the un-modelled drag — the operationally meaningful LEO orbit.

Run Arc d/o n_obs 3-D RMS RTN (R, T, N) Notes
CI fixture, dynamic (C_R=1) 3 h 70 181 2.687 m 0.925, 2.522, 0.045 m residual ≈ pure along-track (drag)
CI fixture, reduced-dynamic (+empirical) 3 h 70 181 0.098 m 0.026, 0.092, 0.025 m empirical absorbs the drag

The dynamic fit clears the 5 m bar with the residual almost entirely along-track — the textbook drag signature at ~430 km. The empirical tier absorbs that along-track error (2.52 → 0.09 m), giving a ~10 cm reduced-dynamic fit against ESA's own ~2 cm orbit. The full-day, full-degree run is the ignored swarm_full_arc_dispatch (the dissemination server serves the product through its file-browser session, so the founder downloads the day's SP3 and points KSHANA_SWARM_SP3 at it). NRLMSISE-00 (NRLMSISE: Naval Research Laboratory Mass Spectrometer and Incoherent Scatter Radar Extended atmosphere model) with space-weather drivers is the noted upgrade that would tighten the dynamic tier further.

LRO lunar — validated, above the 5 m bar (honest) (P4 W4b)#

  • Dataset: the real NASA/JPL (NASA: National Aeronautics and Space Administration; JPL: Jet Propulsion Laboratory) Lunar Reconnaissance Orbiter (LRO; NAIF (Navigation and Ancillary Information Facility) −85) reconstructed trajectory from JPL Horizons, geometric Moon-centred state vectors in the ICRF (International Celestial Reference Frame), 2022-01-01, ~98 km altitude, 1-minute sampling (241 epochs, 4 h, ~2 revolutions). Using Horizons text vectors needs no SPK/SPICE (SPK: planetary ephemeris kernel; SPICE: Spacecraft, Planet, Instrument, C-matrix, Events) reader.
  • Gravity: the GRAIL (Gravity Recovery and Interior Laboratory) GRGM660PRIM field (NASA Goddard Space Flight Center, degree 660), truncated to d/o 150 and fitted at d/o 100, evaluated in the lunar body-fixed principal-axis frame.
  • Open source (no login): Horizons API (application programming interface) ssd.jpl.nasa.gov/api/horizons.api; gravity via ICGEM (International Centre for Global Earth Models) icgem.gfz-potsdam.de.
  • Validation commit: 4fb82bb (tests/agency_lro.rs).
  • Fixtures (SHA-256): LRO 574e3518…d100f0; GRGM 0ff04184…f029977ae (tests/fixtures/agency/NOTICE.md).

This is Moon-centred dynamics — a distinct force model (src/lunar_od.rs): the GRGM field in the lunar body-fixed frame (the IAU 2015 mean-Earth orientation src/lunar_frame.rs composed with the fixed DE421 (Development Ephemeris 421) mean-Earth → principal-axis (ME→PA) offset), plus the Earth (the dominant lunar-orbit perturbation) and Sun third bodies, fitted through the same generic precise Gauss–Newton estimator the Earth datasets use (the precise_od::ForceModel trait).

Run Arc d/o n_obs 3-D RMS RTN (R, T, N) Notes
CI fixture, dynamic (state only) 4 h 100 241 12.05 m 2.91, 10.11, 5.88 m raw overlap 39.9 m
CI fixture, reduced-dynamic (+empirical 1+2/rev) 4 h 100 241 6.67 m 3.41, 4.58, 3.44 m 1- and 2-per-rev empirical absorb the along-track

0.36 correction: until 0.36 the DE421 ME→PA offset was applied in the wrong direction (and with the wrong Euler order), which put the analytic PA frame about 208″ from PA instead of on it. It is now transcribed as SPICE defines it (checked against pxform('MOON_ME','MOON_PA') to 2.6e-16 rad, tests/lunar_me_pa_offset_spice_oracle.rs; docs/design/evidence/fut05b-me-pa-offset-sign/). The figures above are after the fix; before it they were 53.8 m raw, 12.6 m dynamic (3.07, 10.19, 6.81 m) and 6.65 m reduced-dynamic (3.49, 4.56, 3.35 m).

These residuals are above the 5 m bar Galileo (0.13 m) and Swarm-A (0.10 m) clear, and are reported honestly.

What actually sets the floor — a DE-grade cross-validation (and a correction)

We hypothesised that the limiting factor was the fidelity of the analytic lunar orientation and ephemeris (the IAU libration series, accurate to tens of arc-seconds vs the JPL DE (Development Ephemeris) numerically-integrated MOON_PA, and the Montenbruck–Gill Earth/Sun ephemeris, ~0.3° vs a DE/SPICE kernel). To test that directly, the workspace-excluded cross-validation crate xval/anise-lunar-od swaps only those two inputs for DE-grade ones — the DE440 (Development Ephemeris 440) lunar principal-axis orientation (moon_pa_de440_200625.bpc) and the DE440 ephemeris (de440s.bsp), read through ANISE (Attitude, Navigation, Instrument, Spacecraft, Ephemeris — a pure-Rust SPICE-kernel reader) — and re-runs the same estimator (commit ae96a29, kernel SHA-256 c1c7fee… / 60cd55a…):

Tier analytic DE-grade
raw overlap 53.8 m 41.5 m
dynamic 12.6 m 12.0 m
reduced-dynamic (1+2/rev) 6.65 m 6.67 m

0.36 note: most of the dynamic-tier gain below was the offset error, not the DE-grade inputs. With the ME→PA offset corrected, the analytic stack gives 39.9 m raw, 12.05 m dynamic and 6.67 m reduced-dynamic, against the DE-grade 41.5, 12.0 and 6.67 m: the analytic and DE-grade fits now agree on every tier. The 0.30 reading of the table below follows, kept as it was written.

The hypothesis is only half right, and the headline claim needed correcting. DE-grade orientation and ephemeris do improve the raw overlap (53.8 → 41.5 m) and the dynamic fit (12.6 → 12.0 m) — so the analytic orientation/ephemeris error is real and does limit those tiers. But they leave the reduced-dynamic residual essentially unchanged (6.65 → 6.67 m): the 1+2-per-rev empirical tier was already absorbing the orientation/ephemeris error, so the operational ~6.6 m floor is set by something else — a residual the cycle-per-rev basis cannot absorb and DE-grade frames do not remove. The most consistent explanation is unmodelled LRO non-gravitational dynamics (thermal re-radiation, outgassing) over the short 4 h arc; field degree is excluded (identical at d/o 100 and 150) and integrator tolerance is excluded (identical at atol 1e-6 vs 1e-9). The constructive corollary: Kshana's lean, kernel-free analytic lunar stack already matches DE-grade fidelity for the reduced-dynamic (operational) lunar orbit — the pure-coefficient default leaves nothing on the table there. Crossing 5 m would require modelling the LRO non-gravitational forces (a spacecraft-specific box-wing/thermal model and a longer, multi-arc fit), not better frames.

Honesty contract#

  • The < 5 m "green" bar is met for Galileo MEO (0.13 m dynamic) and Swarm-A LEO (2.69 m dynamic / 0.10 m reduced-dynamic). LRO lunar is published as-is at 12.05 m dynamic / 6.67 m reduced-dynamic (1+2-per-rev empirical) — above the bar (0.36, after the ME→PA offset fix; 12.6 / 6.65 m before it). A DE-grade cross-validation (above) tested and corrected the limiting-factor claim: the reduced-dynamic floor is not the analytic orientation/ephemeris (DE440 kernels leave it unchanged at 6.67 m), so it is not closed by better frames but by modelling the LRO non-gravitational dynamics — the honest, updated path to metre level.
  • For LEO, the dynamic (state-only, static density) and reduced-dynamic (with empirical accelerations) tiers are always reported separately, so the reader sees what the empirical terms absorb; the reduced-dynamic tier is the operational orbit. The same separation holds for the MEO empirical/pure-force tiers.
  • Every residual carries its commit hash, dataset reference, and fixture checksum above.
  • Datasets validated against real agency truth: 3 of 3 (Galileo MEO, Swarm-A LEO, LRO lunar). Meeting the < 5 m bar: 2 of 3 (Galileo ✓, Swarm-A ✓; LRO at 6.67 m, honestly above it).