Fast spin

If my maths is correct, this planet rotates at a little under 10,000 km/h at the equator.

OYULECK.jpg


I didn't notice until after the fact that it also orbits its parent star in 7 hours. I'm not too far away - next session I might just head back and see if I can see just how close it is and how fast it's moving.
 
Well, the closeup view proved to be... disappointing. You can just about see the planet moving if you look long enough, but only because it slowly eclipses stars as it moves in front of them.

Best estimate is that it is between 1.6 and 1.8 ls from the parent star. What's the closest hot jupiter currently on record?
 
What's the closest hot jupiter currently on record?

That's a good question. I was about to try pulling some numbers from my Hot Jupiters spreadsheet, but some of the numbers are ridiculously tiny for orbital parameters. Like, impossibly low (0.0000000000668 lightseconds, for instance). This is probably being thrown off by binary planets in the data, etc. However some of these numbers are stupidly low for that as well.
 
Orbital velocity is dependent on proximity to the thing being orbited, but also on the mass of that thing being orbited. Your gas giant orbits a low-mass brown dwarf, so even a very close orbit isn't going to move super-fast. A similarly close planet orbiting a much heavier star will move much faster.

Here's a Class V giant I spotted back in December 3302 (2016), closely orbiting an M-class star which was in turn closely co-orbiting orbiting a K-class primary star - this was, literally, the view from the arrival point. The planet was visibly moving (though perhaps the perceived motion was a combination of the planet's orbit and the secondary star's orbit). It wasn't "Mitterand Hollow fast", but it definitely, noticeably moved. Here's the EDSM page for it.

jP1sfZk.jpg


gC9RU4J.png
 
That's a good question. I was about to try pulling some numbers from my Hot Jupiters spreadsheet, but some of the numbers are ridiculously tiny for orbital parameters. Like, impossibly low (0.0000000000668 lightseconds, for instance). This is probably being thrown off by binary planets in the data, etc. However some of these numbers are stupidly low for that as well.
I've seen that too for many charateristics. I visited some and saw that it was just wrong in the EDSM data. In the end I was iunsatisified that I excluded almost all "low records" from my journey.
So unfortunately not much of a datamining opportunity here.
 
I added some code to filter out the binary planets, and it removed about 11k of them from an initial list of 66k (now down to 55k). But the list still contains some absurdly low numbers for semi-major axis. If we look instead at the orbital period (which of course depends on the mass of the parent), some orbit quite quickly. The lowest period still in the list is 0.000456019 days (39 seconds), which uhm.. is still hard to believe. :D

That last one is Synuefai AH-E b31-1 A 1
 
As it's less than 1000 LY from the Bubble (where I happened to be), I visited there. Turns out it's a co-orbiting planet, with a co-orbital period of 39 days, not 39 seconds.

So, another example of bad data entering EDSM. As I'm running EDD, the data in EDSM for this system is now corrected.

There is a lot if bad data in some of the databases from when the data was entered manually. I spent a while some time ago correcting radius sizes of bodies that were out by a factor of 10 or even 100. For instance it would say radius 42klm and it would be 420km, or 200km and it would be 2000km, there is some that can't be corrected due to the systems being "already discovered" so you can't scan the bodies, oh well.
 
Back
Top Bottom