Orbital Mechanics
A simulation environment for orbits, escape, gravity assists, force laws, and conceptual gravity models.
The Gravity Lab focuses on systems governed by attraction and motion. Classical presets include circular and elliptical orbits, escape trajectories, Earth-Moon motion, binary stars, gravity assists, Roche limits, and modified force laws. It also includes clearly labeled pedagogical quantum-gravity models.
Real-world jobs
- Teach circular orbit, eccentricity, escape, and energy.
- Build intuition before using a mission-analysis package.
- Compare a numerical simulation with a known analytic result.
- Explain gravity assists or Roche limits to a non-specialist audience.
- Explore how changing a model assumption changes the observed system.
Environment contract
| Layer | Example |
|---|---|
| User | Aerospace student, instructor, researcher, or science communicator |
| Inputs | Primary body, altitude, initial state, tracer count, force exponent, and time rate |
| Controls | Scenario preset, parameters, pause/reset, view, trails, and potential display |
| Output | Radius, velocity, eccentricity, energy, orbit class, period, and particle history |
| Verification | Compare with a circular-orbit period, energy relation, or another analytic benchmark |
| Boundary | Conceptual and educational analysis, not operational trajectory design |
Example workflow: validate a low Earth orbit
Question: Does the simulated period of a 400 km circular orbit agree with the analytic expectation?
- Select the low Earth orbit preset and set altitude to 400 km.
- Keep the inverse-square exponent at 2.
- Record radius, velocity, eccentricity, and simulated period.
- Compare the period with the displayed analytic expectation.
- Move the force exponent away from 2 and observe which orbital properties fail.
Definition of done: the baseline discrepancy is recorded, the modified-law case is clearly separated from physical gravity, and another user can reproduce both runs.
Separate physical models from teaching toys
When an environment includes speculative or simplified models, label them at the point of use. Preserve the governing equation and assumptions with the output. Do not let a polished visualization imply that a conceptual model is a validated theory or operational prediction.
Ways to extend it
- Add a worksheet that asks learners to predict results before running a case.
- Export a compact state vector and comparison table for review.
- Add a mission-story mode that explains the role of each maneuver.
- Compare integrators or step sizes against the same analytic case.
- Track error growth across longer runs.
The general lesson is powerful: every simulation environment should include at least one case where the expected answer is known before exploration begins.