News for hackers. Stuff that matters.

dard

Sorry, I know some of the ways measurements are taken for satellite orbits, but not who actually does them or how that information makes its way to JPL.
SPICE itself is a C package with a number of wrappers in other languages. JPL use it, along with numerical integrator and orbit determination code to generate SPICE "kernels", IE: binary files. The Horizons API allow you to use their numerical integrators to calculate the position of asteroids and comets. This works great for single objects, or a handful, but struggles when you want to look at the entire solar system at a time. This is where my code comes in, it enables similar calculations to what Horizon's provides, but you can do them locally on all known asteroids/comets.

The C SPICE library is available online, but it dates back decades, and was not really built with multi-core support in mind. My code enables reading of SPICE kernel files with native multi-core support. Though I would argue the bigger benefit that my code provides is the numerical integrator which can be used on the entire asteroid belt at once.

JPL Horizons API is open to anyone, if you hammer it enough they may rate limit you, but I don't believe they have limits. As far as I am aware they don't have any API keys or usernames. See: https://ssd-api.jpl.nasa.gov/doc/horizons.html

Im a developer for the upcoming space telescope NEO Surveyor (Near Earth Object Surveyor). I actually work quite a bit with a number of people on the team up at JPL, Horizons is the canonical source for ephemeris information. Another vital part of the chain is the Minor Planet Center (MPC), which is where all observations of asteroids and comets are sent by the community. The MPC is the international authority for these observations, which JPL ingests and computes orbits for (though the MPC also has to compute orbits as a part of their work).

As a part of my work I have written a rust/python package[1] to compute the position of asteroids accurately using the ephemeris data provided by these two excellent sources. For the people who use SPICE kernels (a rather old binary format for storing orbital ephemeris), I have also written a custom implementation of spice kernel reading which is natively parallel.

[1] https://github.com/Caltech-IPAC/kete

Here is a simulation I did in response to your comment, this is ~6 million impactors and their on sky velocity as they approach Earth. Dotted black line is our expected detectability limit, anything to the right of that is detectable. On sky velocity is measured in degrees / day.

https://www.dardahlen.com/6m_impactor_vel.png

I work on the NEO Surveyor space telescope, doing orbit simulations of asteroids/comets and predicting expected observations of objects like these.

If you look: https://www.minorplanetcenter.net/db_search/show_object?utf8...

You will see this was actually spotted back in 2014, but only seen for a few days. When an object is only observed for a few days we generally cannot compute an orbit for it, there is just not enough data to pin it down. However during this current pass of it (the last time it will come by for at least a few centuries), we have enough observations to pin its orbit down. Note that a lot of this is automated nowadays, with automatic observation and "interesting" objects being flagged automatically. There are a lot of small rocks up there (sub 100m).

I work on NEO Surveyor, I replied to the parent comment largely agreeing with you, however I wanted to mention that we do rely on apparent motion for determining if a source is moving (asteroid/comet). However IR is ideal for spotting asteroids for a few different reasons, a big one is that asteroids have a wide range of surface brightness. Think bright concrete to black coal, so in the visible spectrum a 100m light stony asteroid can be just as bright as a 500m coal colored one. It is very difficult to determine size from the brightness alone. However in IR everything is approximately the same temperature (largely proportional to the distance from the sun), so these things all glow in the IR directly proportional to their diameter.
I actually work on NEO Surveyor telescope (surveying for dangerous asteroids), writing the simulation code use to track expected performance. So simulating +20 million asteroids and what will be visible during the mission. Motion is how we determine if there is an asteroid or just some static sky source (IE: star).

However your comment is not correct, everything moves, even in the days leading up to a potential impact things are constantly in motion. The only asteroids which appear stationary actually tend to be quite far away and just happen to be moving at just the right speed.

Things which are close to us, even impactors tend to have large angular velocities, very VERY few things come directly radially in. A part of this is that the Earth is rotating, if you are familiar with the parallax effect then the Earths rotation causes parallactic motion of the asteroids when close. IE, take a photo, wait 4 hours, and you, an observer on Earth, has now moved. The geometry has to be just right for close objects to be stationary, and a different observing position on Earth (or space) will see the object moving even if you see it stationary.

Really exciting to see the pictures. I helped write code for a paper predicting the size of Dinkinesh a few weeks before the flyby. It's so small we had to overlay multiple images in order to even see it in IR. We did not expect a binary!

https://arxiv.org/pdf/2309.13158.pdf