Research report

Satellite constellations for disaster response

Built and validated against simulation. No orbit has been flown.

Code on GitHub (opens in a new tab)

The question

Can a learned model stand in for hours-long orbit simulations, and find orbits that revisit disaster areas sooner?

43.9%

shorter mean revisit gap than a 48-hour standard benchmark, best simulated orbits across eight regions

The best simulated orbits cut the mean revisit gap by 43.9% against a 48-hour standard benchmark.

012243648
  • Standard benchmark
  • Simulator-backed data
  • Includes generated rows

Tap a region

Best simulated gap in each region's data, in hours, against a fixed 48-hour figure for one satellite on a standard sun-synchronous orbit. The benchmark is a textbook number written into the validation script, not a simulation. Mean of the eight regions: 26.9 h. Regions marked as including generated rows have a best gap that may come from a generated row.

Gaps as a table
RegionBest simulated gap (h)Shorter than benchmark
Standard benchmark48-
Mean of eight regions26.943.9%
United Kingdom14.470.0%
Amazon17.264.2%
Caribbean19.958.5%
California22.852.5%
Sahel26.744.4%
Bay of Bengal3527.1%
Australia38.719.4%
Pacific Northwest40.715.2%

Why it matters

After a disaster, the gap between satellite passes sets how soon responders can see what changed. Searching orbits with a simulator is too slow to explore widely.

Method

  • A hybrid surrogate model is trained on 7,000 high-fidelity STK simulations to predict the average gap between observations over a region.
  • A multi-objective search (NSGA-II) looks for orbits against the surrogate, with a confidence bound on each prediction.
  • As a check, 500 orbits are compared against the simulator and against an independent analytical tool.

Data

  • 11,200 rows over eight disaster regions: 7,000 from the simulator and 4,200 generated for the Sahel, Bay of Bengal and Pacific Northwest.
  • Held-out accuracy of the surrogate is R² 0.892 with a mean error of 13.65 hours; 98.7% of results pass the physics checks.

Results

A separate comparison: four satellites on optimised orbits against four on sun-synchronous orbits, about 43.6% shorter, the same factor in every region.

A four-satellite constellation on optimised orbits revisits every region 1.77× sooner than on sun-synchronous orbits.

05101520
  • Sun-synchronous
  • Optimised

Tap a region

Average gap between observations, in hours, for four satellites, from the project's constellation comparison. The factor is identical in every region, which the file does not explain; treat it as a property of the comparison, not of each region.

Constellation as a table
RegionSun-synchronous (h)Optimised (h)Factor
Amazon Rainforest9.25.21.772
Caribbean9.85.51.772
Australia (NSW)20.111.41.772
California11.36.41.772
United Kingdom7.141.772

The surrogate predicts shorter gaps in seven of eight regions, by up to about 32%, and a slightly longer one in the Sahel.

The surrogate predicts shorter revisit gaps in seven of eight regions, and a longer one in the Sahel.

-10%0%10%20%30%40%
  • Simulator-backed data
  • Includes generated rows

Tap a region

Improvement = (best simulated gap in that region's data - model-predicted gap at the optimised orbit) / best simulated gap. These are model predictions from the optimiser, not simulator runs of the optimised orbits, and the model reports LOW confidence in every region.

Regions as a table
RegionBest simulated gap (h)Model-predicted gap (h)ImprovementSurrogate R²Upper bound (h)Confidence
California22.815.6+31.7%0.713490.8LOW
Caribbean19.913.6+31.5%0.840199.4LOW
Amazon17.212.1+30.0%0.841466.6LOW
United Kingdom14.411.4+20.8%0.707107.8LOW
Australia38.735.4+8.7%0.850291.1LOW
Pacific Northwest40.737.5+7.9%0.933879.2LOW
Bay of Bengal3534+2.8%0.946173.5LOW
Sahel26.727.9−4.2%0.965228.1LOW

On 500 orbits the model tracks the simulator closely; the independent analytical tool agrees with it far less.

The model tracks the simulator closely (correlation 0.988); an independent analytical tool does not (0.45).

050100150200250300350050100150200250300350Simulator gap (h)Model gap (h)050100150200250300350050100150200250300350Simulator gap (h)Analytical gap (h)

Tap a panel for its summary

500 orbits, 100 in each of 5 regions: gap in hours from the simulator (x) against the model and against the independent analytical tool (y). The dashed line is perfect agreement. The sample was drawn from the full dataset, so some orbits may also have been used in training.

Per-region summary as a table
RegionOrbitsModel correlationAnalytical correlation
Caribbean1000.9910.503
Amazon1000.9960.337
Australia1000.9840.299
United Kingdom1000.9850.624
California1000.9800.377

Where the training rows come from: five regions are simulator-backed, three include generated rows.

7,000 rows come from the orbit simulator and 4,200 are generated.

01,0002,000
  • Simulator rows
  • Generated rows

Tap a region

11,200 rows in all. Rows for the Sahel, Bay of Bengal and Pacific Northwest are generated, so results there describe the model, not the simulator.

Rows as a table
RegionRowsSource
Australia2,500Simulator
Amazon2,000Simulator
California1,500Simulator
Sahel1,400Generated
Bay of Bengal1,400Generated
Pacific Northwest1,400Generated
Caribbean500Simulator
United Kingdom500Simulator

The honest limits

  • The 48-hour benchmark is a fixed figure for one satellite on a standard orbit, written into the validation script. It was not simulated here, and the best gaps for the Sahel, Bay of Bengal and Pacific Northwest may come from generated rows.
  • The per-region improvements are the model's predictions at the orbits it chose, not simulator runs of those orbits.
  • The model reports low confidence in every region. Its upper bound on the predicted gap is far above the prediction (for California, 90.8 hours against 15.6).
  • Three regions are trained partly on generated rows, so results there describe the model more than the simulator.
  • The 500-orbit check was drawn from the full dataset, so some orbits may also have been in training.
  • The four-satellite factor is identical in every region (1.772), which the results file does not explain.
  • No orbit has been flown. The surrogate is validated against simulation output, not on-orbit measurements.

What is next

  • Run the optimised orbits back through the simulator, to turn predictions into measurements.
  • Replace the generated rows for the three regions with simulated ones.
Next reportGlass Societies