订阅以下载
JPL catalog - Potentially Hazardous Asteroids

2024 YR4 is not in the list of potentially hazardous asteroids from JPL, probably because is rather small. Eventually it will somehow placed into an addon somewhere

Hello, can you create an asteroid? Number 2024 YR4, thank you! (Mainly, I don't know how to create trouble for you)

Is 2024 pt5 possible to be added?
2024 PT5 can be added as well, the reason for it not being included on the PHA database looks like the same as 2024 YR4. It has/had a peculiar orbit, though. All SpaceEngine can do currently is to show simple Keplerian elements orbit, unperturbed by gravitational pulls of other bodies. So if you want to see how its orbit was changed in the past by passing near Earth, I'm afraid you won't be able to with SE right now. With a bit of work it could probably be possible to create a path in a scenario script file. Actually it's one of many things I tested in the past, just couldn't dedicate more time to it. I know there are people using that for their video needs, I definitely have to go back to it.

Got it, super neat!

Usually it doesn't take much for those computations to be available in the database Especially for asteroids in the Apolo group, they're basically calculated every day or so. If you want to see exactly when, you can check the page for the object, here: https://ssd.jpl.nasa.gov/tools/sbdb_lookup.html#/?sstr=2024%20YR4

Interesting, I didn't know that's how these systems work, very fascinating that it use is real-world parameters to update it's stuff! Also given the accuracy is still at 3.1% it could be possible that they just don't have the official data for it, possibly withdrawn for further study given it's significance?

Is 2024 pt5 possible to be added?

I'll probably add it manually in the next update of this group.
But here's a thing that I find interesting with JPL definition of potentially hazardous asteroids (PHA): 2024 YR4 is certainly hazardous, but it's not included in this database group by JPL because its absolute magnitude is fainter than 22, which roughly translates in a diameter of less than 140 m. I guess they go with a stricter definition considering potential damages if Earth is hit.
Just to be clear in case you wonder, I'm not picking asteroids by hand and checking their orbits manually, I have software basically processing the database when I launch a few commands.
Now, The fact that 2024 YR4 is not included in that list seems a bit weird, isn't it?
That's why, instead of adding a specific exception for the asteroid, which is not the best way to go with programming, I'll probably expand the program to use custom filters instead of being stuck by JPL's definitions.

Could you add the 2024 YRA Asteroid on its current path? Need to run a few simulations 👀

oh ok, thank you so much again :D