104 comments
Data: CelesTrak TLEs (SGP4), asteroids and comets from JPL SBDB, spacecraft positions from JPL Horizons. Updated daily.
Rendering is WebGL2, orbit propagation runs in web workers. The asteroid set (~30 MB) loads in the background.
The time slider runs forwards and backwards; satellites appear and disappear by launch date.
My old day job was to compute asteroid positions for NASA telescopes, if you are interested in orbit prop you may be interested in: https://github.com/dahlend/kete
I made an asteroid only version of yours earlier this year, where it does full orbit propagation in workers: https://dahlend.github.io/ketev/
I figured the experts here would care to express an opinion.
Links:
https://science.nasa.gov/mission/neo-surveyor/
>satellites appear and disappear by launch date
This uses the modern TLE propagated backwards in time (vs using historical TLEs), correct?That aside, it is just astounding that even a moderate laptop just plows through this as thought it is nothing.
I remember doing orbital calculations on a 486DX with about 30 objects at just barely 30fps thanks to the FPU. That was pretty good for me. Without the FPU you would get maybe 2FPS. Now, you can just throw a half million around at 60fps+ in a web browser. Crazy!
Read the full thread on Hacker News →
Related stories
- Hacker News · 1 points · 10 days ago
- Hacker News · 3 points · 3 days ago
- Lobsters · 3 points · over 7 years ago
- Hacker News · 17 points · 10 days ago
- DEV Community · 9 points · 5 days ago
- Hacker News · 1 points · 7 days ago