RV Sonnenkreis - Decoding Universal Cartographics

Jackie Silver

Jackie Silver
Interestingly it looks like the overdensities are not related to coordinates within the sector or subsector, but are instead related to the absolute x,y,z coordinates.

B overdensities appear at (e.g.) (20,20) (40,20) (60,20)
and C overdensities at (20,20) (60,20) (100,20) and so on.
 

marx

marx
Interesting that it mostly seems to appear in mass codes B and C. I wonder if this is a side-effect of how the Forge might generate stuff from the "left-over mass".

Could you check please if this happens with code D/E in the galactic core, or at least closer to it? Besides the obvious Eol Prou, there should still be some other sectors that would be good candidates.
 

Jackie Silver

Jackie Silver
marx said:
Interesting that it mostly seems to appear in mass codes B and C. I wonder if this is a side-effect of how the Forge might generate stuff from the "left-over mass".

Could you check please if this happens with code D/E in the galactic core, or at least closer to it? Besides the obvious Eol Prou, there should still be some other sectors that would be good candidates.
Click to expand...

Yep I'll check EOL PROU and maybe STUEMEAE - shouldn't take too long to check those.
 

Jackie Silver

Jackie Silver
Here's EOL PROU shown with all mass code E systems surveyed - I can't pick out clumping from the noise, and people have clearly been performing targeted searches.

colonia_in_E.png


I'm not sure what this means for our ongoing scale height researches, but it certainly complicates matters! :)
 
Last edited:

Satsuma

Satsuma
Man. I'd never thought to look for clumping like that. It's interesting that it looks like the scale of the clumping is different for different mass codes. That sure suggests that they ran the stellar forge in passes, one for each mass code.

I'm messing around in the "southern" section of the galaxy, by the way. Here's density data from the Eafots region.
 
Last edited:

Col Frost

Col Frost
Jackie, I'm searching wholesale mostly D mass sub sectors near the core.
In layman's terms, what information would be helpful to record for your research?
Up to now I've been recording AW's and ELW's along with first star type.
 

Jackie Silver

Jackie Silver
Col Frost said:
Jackie, I'm searching wholesale mostly D mass sub sectors near the core.
In layman's terms, what information would be helpful to record for your research?
Up to now I've been recording AW's and ELW's along with first star type.
Click to expand...

At this stage... I'm starting to find the sheer number of different things baffling. :)
But everything ties together.

Can you give me an idea of the scope of your search (like how many mass code D boxels you are looking at, are all the boxels contiguous, and are you scanning every single star system within the boxel, and are you uploading to edsm?) If you were to scan a set of neighbouring mass code D boxels in their entirety, it would be possible to extract the position data from edsm and plot them to see how the clumping looks. Or if you were to scan a column of mass code D boxels and record the masses and ages of the stars, we could look at how that varies with height above the plane, and if you note the number of stars within the boxel, we could look at the scale height as it specifically relates to mass code D stars - it's possible that each mass code has a scale height?

Ooh.

Now that is a thought, and ties to what Satsuma mentioned above and what others have alluded to - we know that certain mass codes drop out in different places.

(edited to add)

I am confused and baffled, but I'm having fun. :D And thanks to all of you and to also kudos to edsm and eddiscovery! :)
 
Last edited:

Col Frost

Col Frost
Jackie Silver said:
At this stage... I'm starting to find the sheer number of different things baffling. :)
But everything ties together.

Can you give me an idea of the scope of your search (like how many mass code D boxels you are looking at, are all the boxels contiguous, and are you scanning every single star system within the boxel, and are you uploading to edsm?) If you were to scan a set of neighbouring mass code D boxels in their entirety, it would be possible to extract the position data from edsm and plot them to see how the clumping looks. Or if you were to scan a column of mass code D boxels and record the masses and ages of the stars, we could look at how that varies with height above the plane, and if you note the number of stars within the boxel, we could look at the scale height as it specifically relates to mass code D stars - it's possible that each mass code has a scale height?

Ooh.

Now that is a thought, and ties to what Satsuma mentioned above and what others have alluded to - we know that certain mass codes drop out in different places.

(edited to add)

I am confused and baffled, but I'm having fun. :D And thanks to all of you and to also kudos to edsm and eddiscovery! :)
Click to expand...
Jackie, the areas i'm searching are detailed here
https://forums.frontier.co.uk/showthread.php/392642-New-Zunou-ELW-hunt/page2
Basically I have already searched all the 9881 D mass stars in Zunou GS-B D13-*, as Chiggy has done for the approx. 13,000 D mass stars in Zunou IN-B D13-*.
The GS-B sub sector is directly above the IN-B sub sector.
We both only started using EDDiscovery and exporting to EDSM part way through this search, so I don't believe all results are on EDSM.

I started a new search in the Zunou MT-Z D13-* sub sector and scanned the first 1,000 stars in the sequence of
10,674​
.
I then got distracted and went up vertically 1000 ly and scanned the fisrt 126 systems in
PHEIA SCRAA OO-Z D13-* sub sector with just over 5,000 stars​
.
I then changed to a
close by sub sector (ZUNOU FE-E D13-*) with just over 7,000 systems which is slightly lower in the Z axis. I've currently scanned 1400 systems here.

I intend to return to the
Zunou MT-Z D13-*​
sub sector soon and finish scanning all the systems in that sub sector.

Hope that gives a better idea[SUB] [/SUB]​
 

BaldEagle

BaldEagle
I have returned from Star One via Heart Nebula (asteroid base) and thought I would start a sequence here :)
Here is the first run:
https://docs.google.com/spreadsheets/d/1T408yL49xdbrdRgsI5bwsXtAlPNj8LA5Po5B4RaqZYM/edit#gid=0

I was planning a N-S line at 100Ly intervals (also looking out for likely volcanism) is this OK or would you prefer one of your 3x3's at just 50Ly (it may be a bit sparse for that here)?
You may have moved=on from these measurements, so do say if they are no longer of use ;)

edit
Added a couple more runs - not too exciting here as lots of systems are tagged
 
Last edited:

marx

marx
I have a question I couldn't really find an answer on my own: is it possible for a regular system to have two proc. gen. names? I'm not asking about overrides such as "Blah Nebula Sector ZZ-Z", where you could search for the underlying proc. gen. name and the search would point you to the overridden name, but whether it should be possible for this to happen between two "regular" sectors or not.
For example, if I were to search for "Blu Air AA-A d0" and end up on "Wizz AR-D d3". (Not that these two examples are anywhere near each other, they were just two that came to my mind.)
 

Jackie Silver

Jackie Silver
I don't think it is possible in "regular" use - I seem to remember that if you create a name that would be outside the 1280ly box of a sector, it may relate to a system in the next sector, but the name would never be seen in game.
 

Allitnil

Allitnil
Jackie Silver said:
I seem to remember that if you create a name that would be outside the 1280ly box of a sector, it may relate to a system in the next sector, but the name would never be seen in game.
Click to expand...
That's the new thing I learned today :D

eg Noijou BA-A h0 goes to Noijuae AA-A h0, Noijou CA-A h0 goes to Noiji AA-A h0, Noijou DA-A h0 goes to Hypuae Phyloea AA-A h0 and so on
 

Redfox

Redfox
AFAIK that's possible, even if just theoretically. I remember being explained by Alot that the system name syntax allows to reference systems way outside of its sector. Impressive example is "Core Sys Sector GX-F g38-0" for which the GalMap search will return SagA. So I guess this would also work for two PG systems.
 

marx

marx
Yep, that was it then. I was looking to bookmark some boundaries, and looks like I made a mistake on the naming. Now that I know that, I can reproduce that quite easily. Thanks!

Also, that "Core Sys Sector GX-F g38-0" is pretty neat.
 

Pyroboros

Pyroboros
It is not good explaint nor documented it may helps clear a few questions. e.g giving to big letter codes (Overflow in Sector Coords)
Also do to Google Doc limitations only 48bit numbers are possible to enter, so IDs may become to big for the sheet in high dense regions.
Basicly it finds the ProgGen Name of a System given the ID64. it also can generate a ID64 given the Sector X,Y,Z, InSector x,y,y, Layer and ID
Also it contains a Keyed List of all not Handmade Sectors as long a system in the sector was reported to EDSM an had a not Handmade Name

ED Sector Names
 
You must log in or register to reply here.
Back
Top Bottom