Dyson Swarm Calculator
A physics based simulator for Type II Kardashev Civilizational Engineering.
Introduction
This engine models the physical and logistical requirements for constructing a Dyson Swarm (a megastructure of a lot of solar collectors) around a G-type star (Like Sol: G2V). It turns astrophysical concepts into easily-readable engineering data, for example: construction timelines, planetary consumption, and orbital info.
Core Physics
The simulator evaluates the swarm's possibility by solving four primary variables:
1. Thermal Equilibrium (The "Goldilocks" Radius)
Using the Stefan-Boltzmann Law, we calculate the distance where a satellite maintains a specific operating temperature. This prevents the swarm from melting or freezing.
2. Orbital Dynamics
Utilizing Kepler's Third Law, the engine determines the orbital period and the necessary Delta-V to reach the swarm's destination from a 1 AU (An Around Earth) starting point.
The simulator evaluates the swarm's possibility by solving four primary variables:
3. The Statite Limit (Radiation Pressure)
A critical feature of this engine is the calculation of the Area-to-Mass (A/m) Ratio. This determines if a satellite is "Heavy" (gravity dominated) or a "Light Sail" (radiation pressure dominated).
4. Exponential Growth using Sigmoid functions
Unlike linear construction models, this simulator accounts for Positive Feedback Loops. It models self-replicating robots that use the energy from active satellites to accelerate the production of new ones.
Core Contacts
While building this engine. I have run into bottlenecks. For example, Point Source vs Finite disk, whether to use a variable or constant for the growth rate, etc...
So I tried to get professional outreach to help me.
1. Jonas Seiler (ESA, Advanced Concepts Team).
Explained that my 10^14 a high and optimistic number for satellites per year. Told me that SpaceX launches 2 rockets per week optimistically.
Explained to me that the growth of the production capacity would probably look like a sigmoid function.
2. Jeanette Heiligers (TU Delft, Faculty of Aerospace Engineering)
Explained a better methodology to work on the project.
Explained why "Attitude-Control" was easier/quicker.
Explained in detail why active station-keeping would always be a necessity.
Explained that in reality there will always be a deviation from the theoretical model.