I placed 1024 Starlink satellites in an orbital simulation, and made them 10000x bigger, to see what would happen if one of them exploded.
Colors: orange for orbiting objects, blue for near-terminal velocity objects in atmoshpere, white flashes show fragmentation after collision.
Here are some info about the simulation:
- Fourth order symplectic integrator (not Runge-Kutta) in cartesian coordinates
- J2 perturbation to simulate dispersion along the LAN element
- Simple velocity-squared drag calculation
- Constant temperature barometric model for atmospheric density
- Spatial partitioning for collision detection
- Each debris/satellite is a solid Aluminium sphere
- For drag calculation the real cross sectional area was used
- For collision detection diameter was increased 10000-fold (cross sectional area 10^8-fold).
- After collision, debris/satellites explode into 30-30 equal-mass fragments at least 5 cm diameter with a normally distributed velocity change. Total kinetic energy change is 10% of the "collision energy".
- Anything below a diameter of 5 cm disappears, or gets absorbed in a perfectly inelastic collision
- Anything at sea level or below disappears
- CPU, single thread
- Delta time: 1 sec, simulation time per frame: 50 sec
- Simulation speed: 6 seconds / frame at 250k peak debris count (not shown)
So why do collision-rate slow down?
Because below 5cm no fragmentation occur, and inelastic collisions (or absorptions) are not displayed. This is to reduce the number of computations.
Негізгі бет What if a Starlink Sat Exploded in Orbit? - Kessler Syndrome Simulation
Пікірлер: 10