Excellently spotted CMDR
that IS somewthing significant, as until now UA were limited to the UA shell 150LY around Merope !For those excited about UA spawn, last night I roved across a 600ly area on that side of the UA and the spawn rates are absurd on that entire side, even some 300ly away from the systems we are looking at closely at the moment.
The first O/B class I went to netted me 4 within 10 minutes and this was at least 400ly away. I'm trying to say in a roundabout way I don't think the spawn rate means much
Two more to go I guess.
Is the base active by any chance ?
It could be that the UL is a way to get the nearest systems with a thargoid site from a known active one
That would be cool.
And kudos to FD, it is really nice stuff you did here.
Actually I'm sitting over those coordinates and can't see anything at all
Do we know if these are abandoned Thargoid installations, or is it more likely they're crashed ships?
Because if they're ships then I'm wondering what (and who) did that to them. And more to the point, where are they now?
that IS somewthing significant, as until now UA were limited to the UA shell 150LY around Merope !
Indication of more Tharg bases re-activating ?
Edit: that also would implicate that we have to look for UP in Ammonia-Worlds in that area ??
Listen to the transmission given by the unknown link starting around 23 seconds in the following video for example: https://www.youtube.com/watch?v=O2x3i3_ZqbM
The transmission consists of high and low notes in segments of three separated by warbles and delays. The first number in the video would be...
> HLH HLH <warble> HHL LLL LHL (0:23-0:32 in the video)
Where 'H' stands for a high frequency note and 'L' for a low frequency note. Each high frequency note represents binary 0 and low frequency note represents 1. This gives the following binary numbers:
> 010010 <warble> 001111101
Throwing these in any binary to decimal converter (first result on google: http://www.binaryhexconverter.com/binary-to-decimal-converter) should give the following decimal representation.
> 18 <warble> 125
The final part to the decoding is to realize that the <warble> stands in for a division, yielding the 18 / 125 fraction.
There's three different transmission so this gives us the following fractions:
Code:I: 157/1000 31/1000 24/25 or in decimal 0.157 0.031 0.960 II: 18/125 31/1000 189/200 or in decimal 0.144 0.031 0.945 III: 151/1000 1/25 937/1000 or in decimal 0.151 0.040 0.937
These were hypothesized to represent distances from unknown systems to specific reference systems, as in... system I would be 0.157 units from reference 1, 0.031 units from reference 2, 0.960 units from reference 3. We made the following educated assumptions:
- The unit of distance is the same that the Unknown Probe used: 871.018 Ly (distance between Merope and Col 70 Sector FY-N c21-3).
- Reference 1 is Merope.
- Reference 2 is HIP 14919.
- Reference 3 is Col 70 Sector FY-N C21-3.
So for system I we'd be trying to find a system that is...
- 871.018 * 0.157 light years from Merope
- 871.018 * 0.031 light years from HIP 14919
- 871.018 * 0.960 light years from Col 70 Sector FY-N c21-3
We can come up with good match for systems I and III but the numbers representing system II don't have a likely candidate that I've found.
My brute force approach for finding the final list of systems was to use the EDDB data set to find all the systems near Merope and check which ones of these are within the required distances of the reference systems. The fastest way for this is to download the systems data set from eddb or edsm (https://eddb.io/api), load it up in a proper database - I used MongoDB but an SQL database should work just fine and query it given the conditions. Downside with this approach is that it misses any system which isn't mapped in EDSM.