Hunt for trojans

You really don't need to apologize for your code! As I wrote above: it looks good and it is tidy and once you pointed me to where I have to look I understood it at once :)
In another file I've even seen one thing where I thought: "Well, that's a nice way of doing it".

I'm not a programmer by trade (even though i spend a lot (if not most) of my time doing it). So I don't really know what it means to program "pythonic". The only thing I do is that I try to be rather explicit when I intend to publish code since I always have the less experienced coder in mind that maybe want's to learn.
Yes, that means I write (much) more than is necessary, but python is not a speedy-langauge anyway :)
 
I certainly wasn't apologising :) Python has some very clever ways of doing things that aren't obvious to people who work with other languages. Pythonic code uses these little syntactic tricks.
 
L3: According to the Wikipedia page this orbit should not be stable. But if you happen to find one, their orbital stats should be the same, they should be on the opposite side of the star and the distance between the two should be twice the arrival distance.
OK, so I think I found one of these.

I have a planet where the first 2 moons have the same orbit.

q4uhWep.png


Both have the same orbital period of 2.2 days. Here are images of the 2 moons' stats.
whBCeca.png

4Sc6TT1.png

As you can see, their eccentricity and inclination are different. So their orbits aren't 100% in line, and if you zoom in close you get this:
hQxoDuR.png

BUT they always maintain the same distance opposite the planet after several months and dozens of revolutions around the planet.
 
Last edited:
In terms of the physics, they're temporarily stable. It doesn't take much for them to drift out of this configuration. A spacecraft could use L3 to stay in position with a minuscule amount of fuel for station-keeping, but it would need to make those small corrections to remain there.

I suspect that the StellarForge allowed it because it functions almost like a snapshot in time. With its perfect Kepler orbits, we'll never see it drift out (as long as the orbital parameters actually do match to the last included decimal place), but even the StellarForge would probably have disrupted it if it had one more time-tick in the algorithm. ;)

Anyway, just speculating a bit here.
 
Wow! I thought such L3 configurations are supposed to be really unstable.

There are a lot of unrealistic things in Stellar Forge that are way more commonplace. Close binary moons and planets that should have torn themselves apart with tides, rings existing beyond roche limits, earthlike planets around stars that are too young to have them etc.
 
There are a lot of unrealistic things in Stellar Forge that are way more commonplace. Close binary moons and planets that should have torn themselves apart with tides, rings existing beyond roche limits, earthlike planets around stars that are too young to have them etc.
Water worlds with no atmosphere.
 
I suspect that the StellarForge allowed it because it functions almost like a snapshot in time
Yep. Just like those colliding planets -- they are absolutely possible one time event, which, because of the Galaxy being frozen, continue to repeat according to schedule :)
 
I read this article earlier today, and the commented on the EDCD Discord, thinking that the Frontier had done the right thing with not having such planet-scale trojans. Then others enlightened me and a link to this thread was posted. So I figure this is a good place to drop a link to this article:


TL;DR - Recent research shows that, for any large enough 'minor' body, an L4/L5 point orbit with respect to a larger body will not be stable due to tidal effects.
 
Is this the sort of thing you're looking for? Not exactly the same orbit (one has a slight eccentricity) but pretty damn close.

6qBPTpO.jpg
 
I managed to get a better orrery view. They aren't on the same orbit. Very close, but not quite the same. Here's the data anyway.

HyxI7LF.jpg

T590icM.jpg
 
Funnily enough, a Trojan configuration where one (or both) of them is in an elliptical orbit is still considered "stable" and would qualify as a Trojan. The elliptical partner of the pair would, from the point of view of the other partner, seem to be slowly orbiting around the Trojan point, rather than hanging in the sky motionless like a "true Trojan".

However, these two moons aren't Trojans, or any other Lagrange Point orbit, mainly because the angle is wrong - for Trojans, you're looking for a sixty-degree angle (so that the two moons and the planet they're orbiting form a perfect equilateral triangle). An L3 pairing would be precisely a full 180 degrees apart, meaning the two moons and the planet would form a perfectly straight line. These moons are more like 150 degrees apart, and that's not a stable orbital position.

You might want to check the journal data for more precise orbital periods than the game is reporting, to see if the match to all the decimal places. If they don't match, then rather than Trojans, what you've got are potentially "colliding moons", as the slightly-faster moon will eventually catch up to the slower one.
 
Heading out of the Bubble towards the Heart nebula and a little over 3KLY out I notice on my left hand panel what seems to be an inner triple with three worlds at a near-identical distance, yet when I FSS the system two of them are together and one is about sixty degrees off. I check in the Orrery view and it is clear: a pair of rocky icy worlds have a trojan companion that is also a rocky icy world!
hGwDQIJ.jpg

GZjYl09.jpg

g2PIjLa.jpg

QDQbEUL.jpg
 
In this system, I not only increased my record for gravity on a landable planet to 5.9g.
22ayqcpd.jpg
233wff7.png


in the system there was also a Trojan, or rather three Trojan Objects
24h9ddd.jpg


or even more exactly, four Objects, because the T-Tauri Star #16 and the metal rich world #17 together form a barycenter
and the High metal content Worlds #18 and #19 run 60° before and after this barycenter on the common orbit around the Star
sdd_en.png


here are the journal data for these Objects, the exact same semi-axes are marked
263ld32.png


and here is a picture of the surface of the High-G World
the Planet should be on place ca.240 of the landable Planets, from the G Forces, and for Metal-rich Planets it is the place 16.
27w1fi2.jpg



has such a trojan with leading and trailing object ever been found? :unsure:
 
Last edited:
Back
Top Bottom