Elite Observatory - Search your journal for potentially interesting objects, or notify you of new ones on the fly while exploring!

This is very nice, thanks for compiling this criteria list. I downloaded and will test. But one bug question in my mind: how it will get updated? Looks like it is a static list on the local PC and will become outdated regularly when new records are discovered.
Has to be updated manually. Fortunately the updates to these records are unusual and infrequent. If these change more than once a month or two months, I'll be shocked. Perhaps in some future date Elite Observatory would be able to remotely pull the data, but that seems to be quite outside the scope of the app at the moment.
Once a month is actually pretty frequent; that surprises me. Anywho, it wouldn't be a big deal to find a body that broke an outdated record, IMO. It's not like you can go looking for record-breaking bodies on purpose, and if you were (or if you can, I suppose) then you'd be up to speed already anyways. Just update the xml with the current record and wait until it triggers again.

Doable, along with Surface Pressure per body. For stars, absolute magnitude, stellar mass, radius, and surface temperature are currently trackable. It just takes more time, and that XML file already took me a while.....

Of course. Just suggesting.
 
Last edited:
Next challenge: I'm trying to write a check for planetary bodies with high inclination that orbit other bodies with rings. Past research has shown these are good for views.

Current criteria:
1) Inclination between 65 and 115, and -65 and -115
2) Parent body has rings
3) Body itself is not a star
4) Parent body is not a star

The following code returns results that don't seem to match the "parent body is not a star" check, eg. KOI 102 1. Any suggestions here?


XML:
<!--  High Inclination Moon of a body with rings -->
          
            <Criteria Comparator="And">
              
                 <Criteria Comparator="Or">
                    <Criteria Comparator="Between" LowerValue="65.0" UpperValue="115.0">
                        <Operation Operator="None">
                            <FirstValue Type="EventData">OrbitalInclination</FirstValue>
                        </Operation>
                    </Criteria>
                    <Criteria Comparator="Between" UpperValue="-65.0" LowerValue="-115.0">
                        <Operation Operator="None">
                            <FirstValue Type="EventData">OrbitalInclination</FirstValue>
                        </Operation>
                    </Criteria>
                  </Criteria>
                
                   <Criteria Comparator="Greater" Value="0">
                     <Operation Operator="None">
                        <FirstValue Type="EventData">Parent:Rings</FirstValue>
                    </Operation>
                   </Criteria>
              
                   <Criteria Comparator="Not">
                     <Criteria Comparator="Greater" Value="0">
                       <Operation Operator="None">
                         <FirstValue Type="EventData">StellarMass</FirstValue>
                       </Operation>
                    </Criteria>
                   </Criteria>
              
                   <Criteria Comparator="Not">
                      <Criteria Comparator="Greater" Value="0">
                         <Operation Operator="None">
                           <FirstValue Type="EventData">Parent:StellarMass</FirstValue>
                        </Operation>
                     </Criteria>   
                   </Criteria>
              
                <Description>High Inclination body near rings</Description>
                    <Detail>
                        <Item>OrbitalInclination</Item>
                    </Detail>
          
         </Criteria>
 
Last edited:
Next challenge: I'm trying to write a check for planetary bodies with high inclination that orbit other bodies with rings. Past research has shown these are good for views.

Current criteria:
1) Inclination between 65 and 115, and -65 and -115
2) Parent body has rings
3) Body itself is not a star
4) Parent body is not a star

The following code returns results that don't seem to match the "parent body is not a star" check, eg. KOI 102 1. Any suggestions here?


XML:
<!--  High Inclination Moon of a body with rings -->
     
            <Criteria Comparator="And">
         
                 <Criteria Comparator="Or">
                    <Criteria Comparator="Between" LowerValue="65.0" UpperValue="115.0">
                        <Operation Operator="None">
                            <FirstValue Type="EventData">OrbitalInclination</FirstValue>
                        </Operation>
                    </Criteria>
                    <Criteria Comparator="Between" UpperValue="-65.0" LowerValue="-115.0">
                        <Operation Operator="None">
                            <FirstValue Type="EventData">OrbitalInclination</FirstValue>
                        </Operation>
                    </Criteria>
                  </Criteria>
           
                   <Criteria Comparator="Greater" Value="0">
                     <Operation Operator="None">
                        <FirstValue Type="EventData">Parent:Rings</FirstValue>
                    </Operation>
                   </Criteria>
         
                   <Criteria Comparator="Not">
                     <Criteria Comparator="Greater" Value="0">
                       <Operation Operator="None">
                         <FirstValue Type="EventData">StellarMass</FirstValue>
                       </Operation>
                    </Criteria>
                   </Criteria>
         
                   <Criteria Comparator="Not">
                      <Criteria Comparator="Greater" Value="0">
                         <Operation Operator="None">
                           <FirstValue Type="EventData">Parent:StellarMass</FirstValue>
                        </Operation>
                     </Criteria>
                   </Criteria>
         
                <Description>High Inclination body near rings</Description>
                    <Detail>
                        <Item>OrbitalInclination</Item>
                    </Detail>
     
         </Criteria>
Hm. What an idea. How many stars orbit ringed bodies? And why wouldn't you want to detect a high inclination body around a ringed star? I didn't realize there were negative inclinations, so thanks for including that!

P.S. Does that mean that my mistake was using "greater than" instead of "greater" in my comparator fields? 🤦‍♂️ RTFM!
 
Last edited:
Ringed stars are very rare, but stars with belts showing as "rings" are fairly common (at least from the logs I have), so it's easier just to filter them out. Actual ringed stars will be REALLY OBVIOUS if you ever see one.

Also the negative inclination thing is weird and I'm not sure I understand it, I think it has to do with the rotation of the body relative to the parent.
 
snip
Current criteria:
1) Inclination between 65 and 115, and -65 and -115
2) Parent body has rings
3) Body itself is not a star
4) Parent body is not a star

The following code returns results that don't seem to match the "parent body is not a star" check, eg. KOI 102 1. Any suggestions here?
snip
How about this? In theory, it'll just check for a ringed planet parent, "Planet:[number]" being a field in the "Parent" event data if the parent is indeed a planet. This may be another non-starter, though, since "Planet" is not listed in Observatory's criteria.

XML:
<Criteria Comparator="And">
                 <Criteria Comparator="Or">
                    <Criteria Comparator="Between" LowerValue="65.0" UpperValue="115.0">
                        <Operation Operator="None">
                            <FirstValue Type="EventData">OrbitalInclination</FirstValue>
                        </Operation>
                    </Criteria>
                    <Criteria Comparator="Between" UpperValue="-65.0" LowerValue="-115.0">
                        <Operation Operator="None">
                            <FirstValue Type="EventData">OrbitalInclination</FirstValue>
                        </Operation>
                    </Criteria>
                 </Criteria>
         
        <Criteria Comparator="And">
                   <Criteria Comparator="Greater" Value="0">
                     <Operation Operator="None">
                        <FirstValue Type="EventData">Parent:Rings</FirstValue>
                    </Operation>
                   </Criteria>
                   <Criteria Comparator="Greater" Value="0">
                       <Operation Operator="None">
                         <FirstValue Type="EventData">Parent:planet</FirstValue>
                       </Operation>
                    </Criteria>
         </Criteria>

          <Description>High Inclination body near rings</Description>
               <Detail>
                   <Item>OrbitalInclination</Item>
               </Detail>   

</Criteria>
 
Last edited:
I'm 90% certain the parameter does not work like that. Parent:{EventData} has to match a valid {EventData} and according to the documentation "Planet" is not one of them. Always Read the fine manual.....
 
A lot of these are thanks to this app! And I think this one, in particular, is worth the occasional asteroidal interference IRT high inclination bodies orbiting rings. I can discern when a ring is a belt.

vokoV6i.jpg
 
Trying to come up with a criteria for squishy GG's. I've collected data on six I've come across recently, and it looks like if it has a radius of less than 70,000km and a Rotational Period of less than .8 days, it will likely be squishy. Can anyone confirm this?

Looks like I'll need to set up a criteria for each class of GG, ya? How many criteria can one have under an "and?" Or could that work mathematically? If RxRP is less than 70000x.8 (56000)? I think I'll try that. Maybe the ratio works for larger diameter GG's? Am I making any sense?

🍸

WT* negative RP's!!!

XML:
<Criteria Comparator="And">
    <Criteria Comparator="Equal" Value="1">
        <Operation Operator="None">
            <FirstValue Type="EventData">PlanetClass:gas giant with ammonia based life</FirstValue> [One criteria for each GG type]           
        </Operation>
    </Criteria>
    <Criteria Comparator="Between" LowerValue="0" UpperValue="56000"> 
[Something tells me this should be type specific, but it also seems the higher the radius, the faster the necessary rotational period required to make a squishy, so maybe there is a constant?]
        <Operation Operator="Multiply">
            <FirstValue Type="EventData">Radius</FirstValue>
            <SecondValue Type="EventData">RotationPeriod</SecondValue>            
        </Operation>
    </Criteria>
    <Description>Ammonia Life Squishy</Description>
    <Detail>
        <Item>DistanceFromArrivalLS</Item>
    </Detail>
</Criteria>
 
Last edited:
Code:
 <Criteria Comparator="Between" LowerValue="0" UpperValue="56000"> 
    <Operation Operator="Multiply"> 
       <FirstValue Type="EventData">Radius</FirstValue> 
      <SecondValue Type="EventData">RotationPeriod</SecondValue>
I think this checks if <RotationPeriod * Radius> falls between 0 and 56000.
It won't ever fit there, because journals store Radius as meters and RotationPeriod as seconds.
Change <Operation Operator="Multiply"> to <Operation Operator="None"> and move RotationPeriod into its own criteria, while remembering correct units.
 
Unfortunately the oblate shape of planets isn't directly stored in the journals, and thus the EDSM data doesn't have it. Instead, it would need to be extrapolated from the rotational period of the planets, and related to their size. So I guess a sensible cutoff would need to be chosen.

My database is a bit clobbered at the moment, since it's currently running today's map and spreadsheet updates. :) But it looks like the rotational periods for gas giants have a really wide range. One of the slowest takes over 7 million days to rotate. One of the fastest is listed at about 0.2 seconds (Synuefe IK-C d14-69 2). Yikes.
 
Unfortunately the oblate shape of planets isn't directly stored in the journals, and thus the EDSM data doesn't have it. Instead, it would need to be extrapolated from the rotational period of the planets, and related to their size. So I guess a sensible cutoff would need to be chosen.

My database is a bit clobbered at the moment, since it's currently running today's map and spreadsheet updates. :) But it looks like the rotational periods for gas giants have a really wide range. One of the slowest takes over 7 million days to rotate. One of the fastest is listed at about 0.2 seconds (Synuefe IK-C d14-69 2). Yikes.
Excellent; sounds like a challenge.
 
One of the fastest is listed at about 0.2 seconds (Synuefe IK-C d14-69 2). Yikes.

That's a rotational speed of 10pi radians/s, with a radius of 77,192km that puts the velocity on the surface at 2.4 million km/s - versus an escape velocity of a mere 96km/s for a body of 885 earth masses with that radius.

I'm not sure that can work as a planet.
 
re: Oblongs, someone needs to find at least 4 or 5 examples in order for us to determine what orbital conditions make it happen, and then we can see if writing a check for it is possible
 
re: Oblongs, someone needs to find at least 4 or 5 examples in order for us to determine what orbital conditions make it happen, and then we can see if writing a check for it is possible
Yeah, I’m working on that. I just wondered if you had anything already.
 
About the oblateness of Gas Giants, I don't think radius & rotational period will work as criteria.
Why? Because I'm staring at pretty much perfectly spherical GG with rotational period of 0.5 days.
I think surface gravity combined with rotational period will give better clues.
 
Back
Top Bottom