Time is such a pain, I write code for simulating orbits of asteroids/stuff in the solar system, and time and time conversions play a major roll in it. I often need accuracy at the mega-year to giga-year scales, but also sometimes micro-second relative.
I saw on this page that you at least mention TAI time, how are you handling time scales in general? Like would it be hard to add some other timescales like UT1?
Right now I have to do all of this manually and I have been using chrono as just a convenience wrapper so that my users can convert ISO time strings into my internal representation.
Edit: Oh no! I just found out chrono is being semi-deprecated, looks like I'm going to be switching...
Jiff only supports the Unix time scale. It sounds like you probably want `hifitime` instead! I believe it was designed with your use case in mind. See: https://docs.rs/hifitime/
Ah yeah hifitime, I tried it out but its internal representation doesn't work well for my long term simulations, the integer representation ends up increasing the numerical noise in my simulations when I do really sensitive long term ones.
If you turn on the 'Stars' in that, you'll see that its currently in the interesting direction of the sky - 'twards the center of the Milky Way where we've got other telescopes looking. I wonder if we would have detected it if it was 180° further in its orbit.
> Another factor that kept ED138 hidden is that it is on the same plane as our galaxy. “For the last 20 years, the object has kind of been looping its way across the Milky Way, from our point of view,” Holman explained. “People don’t typically search for things in the Milky Way, because there’s so many stars that it’s really hard to find moving objects.” [1]
This thing was actually found despite its location, not because of it. If it had been in the opposite part of the sky we almost certainly would have spotted it sooner, given that it's one of the brightest TNOs we've discovered.
We're finding it now because Vera Rubin (the instrument that found it) just came online and is exceptionally good at finding these kinds of objects specifically, even when they're hiding amidst a dense population of stationary background stars.
> ED138 joins the rapidly growing sample of solar system objects discovered by Rubin since it began collecting early data in preparation for the Legacy Survey of Space and Time (LSST), which began in June 2026. In April, before LSST formally began, the Rubin solar system team announced observations of over 11,000 new asteroids, which included roughly 380 new TNOs. At the time, the team called this large submission “the tip of the iceberg” and expressed their excitement for the discoveries to come once LSST began. With the discovery of ED138, those hopes are coming to fruition.
My point was that the LSST survey was looking in those areas as part of its "mapping the Milky Way"
Pluto has a 248 year orbit... which is close to the 282 years for ED138. 100 years ago, maybe Tombaugh would have found ED138 that if he was looking in that part of the sky.
I've always only ever seen diagrams of the Jupiter Trojans from a top down perspective so I never realized how much they stretched beyond the orbital plane of the solar system.
Do you know why they stretch so up and down relative to Jupiter? Is that sort 3d distribution shape typical for L4 and L5 Lagrangian points, and it's just amplified by the size of Jupiter or is there something else at play there?
The Lagrange points are more like "regions" than points in reality. There is some complicated math you can do to work it out, but typically numerical stuff is a bit more reliable once you start to include the rest of the planets, the analytic theory gets pretty complicated the more bodies you include.
The trojans that you see there sort of do a little dance when you plot them in the rotating frame of Jupiter (more technical term is librate). The size of the region has to do with the mass of the parent body, since jupiter is so big, the capturing region is pretty large. Technically there are other trojans around some other planets, but most of them are not long term stable like jupiter is, mainly because jupiter is just big.
Yeah I knew they were regions more than points, I just sort of envisioned them as something more in the same of a tapered tail than something so tall compared the diameter of Jupiter.
I'd like to take the time to tell you that I really appreciate your contributions to this site. I'm always excited when there's a post about asteroids or something similarly sized in the solar system because I know that you'll post about it more often than not.
I've taken a course on the geology of the solar system and a course on exoplanet detection but I definitely consider myself a layman in this field. I've always had a particular fascination with these small tumbling rocks in our solar system so it's always a pleasure to see you talk about them and your work.
This guy had a close encounter with saturn in 2018 and his orbit dramatically changed. At the time he was likely a very cold object that had frozen volatile material (usually water and CO/CO2), The PANSTARRS telescope found him in 2023 after he started giving off material and becoming a comet.
Because he came so close to saturn, it is likely that the estimate of the orbit before this is not super precise, as orbital mechanics is a chaotic thing and small changes of initial conditions become huge changes later.
It looks like its orbit is actually within the orbit of Pluto at one point, and at times, the two bodies could come within a very small distance of each other. Wouldn't this disrupt one or the other, possibly throwing them off of their orbits?
Part of why Pluto was demoted is it's so small it doesn't effectively clear it's own orbit. Orbits can look close here but with how small Pluto is it's gravity would barely affect this dwarf planet. It's also possible they've only been at their closest approach a handful of times in their entire life.
it's interesting the further the planets are the more off level their orbit is, is that because most of the planet creation chaos was happening near the sun?
It requires less delta-V to create a large change in inclination when the object is far from the Sun, because the orbital speed in a more or less circular orbit varies as (orbital radius)^(-1/2).
Yes, imagine a highly elliptical orbit and you've just reached the furthest point , like the roller coaster at the top of the hill, almost stationary. At that point you could pretty much boost the object in any direction you wanted, and it would then assume that orbit.
Yes. In that situation, where the perihelion is at the minimum tolerable distance from the Sun, the speed at apohelion is proportional to 1/(distance to sun) (this follows from conservation of angular momentum).
It is made of water-ice, however it cannot be forming clouds using the same formation process that happens on Earth. The typical cloud formation process that happens on Earth has water forming around bits of dust, but on mars the atmosphere is too thin to have dust particles at that altitude. So something else is causing the cloud formation.
At least that is my read of it.
I think there was a recent paper about this, I seem to recall seeing a discussion of the process somewhere.
Could surely be warm humid and dusty gas emitting from the volcano right there, which as it cools allows the water to condense out onto the particles..?
I mean, I am kinda a genius its true but surely they also have some clever people on the staff who would have thought of that..?
How are you sourcing the spacecraft positions from JPL? Are you just grabbing a huge list of state vectors?
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/
Hi, I wrote orbit propagation code that is used to compute asteroids and comet positions for several of the NASA space telescopes.
I refit the orbit and yeah this is not a dangerous object. Given its (currently poorly constrained) orbit it is likely a comet, it came the closest it will ever come to Earth last month at about half an AU from us. (IE: half the distance from the earth to the sun).
It is at about a 110 degree inclination, meaning it is basically perpendicular to the solar system plane and already passed perihelion.
MOID, or Minimum Orbital Intersection Distance, is a basic geometric measurement that says how close the geometric ellipses of two orbits get together. It doesnt mean that the objects will actually be that close ever. For example the MOID of the jupiter trojan asteroids is basically 0 since the orbits are the same, but they dont get close to jupiter. It's really handy to use it to rule out dangerous stuff though, non-zero MOID usually means there is no way it could ever be dangerous.
Basically it is a full professional grade telescope processing pipeline in your browser. It does 2 queries to some custom databases to identify known asteroids and stars, but all image processing and calculations are done in the browser. This means the backend is pretty tiny. That said it is running on an old box in my closet, so queries may take a while if it gets hammered.
I built it since I have worked with quite a few astronomers over the past 4 years and I keep watching them do the same steps, purely built to make my friends lives easier. I wrote it all in rust and managed to compile it into wasm. With some help from fable as I am not a frontend guy at all, I built it into a small website.
Some of the code is public, the orbital mechanics code I wrote while I worked at Caltech. Which is being used on SphereX, NEO Surveyor, and the Roman telescopes to identify known asteroids.
https://github.com/dahlend/kete
The writing style has significantly improved, however the token burn rate for tasks I have been working on seems to have skyrocketed. It definitely appears more capable (though I am unclear how much of that is just me liking the English it writes now vs actually more performant). I was using Fable 5 for some mathematical analysis assistance and redoing a part of it with 5.1 burned 60% of my session at a much faster rate.
This. It seems to light my usage of my max plan on fire. I’ve gone back to opus because I run out of usage in my five hour window so much more quickly.
reply