Solar-System Observatory
An interactive celestial environment for education, event exploration, and scientific communication.
The Solar-System Observatory turns orbital ephemerides into a world a user can navigate. It provides planets, dwarf planets, moons, a comet, a controllable clock, and shortcuts to known events such as Halley's perihelion, the great conjunction, and the Apollo 11 landing.
Real-world jobs
- Prepare an astronomy lesson around an eclipse, conjunction, or historical date.
- Explain the difference between orbital period, position, and apparent motion.
- Build an interactive exhibit for a classroom, museum, or public science event.
- Review the sequence of a historical space event before writing or presenting it.
- Create screenshots or recordings that communicate a celestial configuration.
Environment contract
| Layer | Example |
|---|---|
| User | Student, instructor, science communicator, or curious researcher |
| Inputs | Date, time rate, selected body, known event, and viewing perspective |
| Controls | Pause, reverse, change simulation speed, jump to now or a known date, inspect bodies |
| Output | A reproducible view or recording of the selected celestial state |
| Verification | The date, selected objects, source model, and simulation rate remain visible |
| Boundary | Explanatory and exploratory use, not operational spacecraft navigation |
Example workflow
Question: Why is Halley's Comet visible only during widely separated periods?
- Jump to the 1986 perihelion and inspect the comet's position.
- Advance time at one month or one year per second.
- Compare the comet's long orbit with the much shorter planetary orbits.
- Jump to the 2061 perihelion and repeat the observation.
- Capture the two states with the date and time rate visible.
Definition of done: the learner can identify both perihelion dates, describe the relationship between orbital period and recurrence, and reproduce the views.
What makes this an environment
A static diagram shows one answer. The environment exposes time and viewpoint as controlled variables, while the model and body catalog provide a stable source of truth. The user can form a question, change one variable, observe the state, and keep evidence of the result.
Ways to extend it
- Add a guided lesson with questions and checkpoints.
- Let users compare predicted and observed positions from a supplied dataset.
- Add a “story mode” for a mission or historical event.
- Record selected dates and views as a shareable investigation.
- Require citations for model assumptions and data sources in exported material.
The same pattern works for any time-dependent system: supply-chain events, financial scenarios, incident timelines, biological cycles, or project plans.