On Sector Surveys - Tools and Strategies

Between some nifty improvements to my Cobra's jump range (30.5 ly, thank you Ms. Farseer and Coriolis.io) and some inspiration from Chiggy's ELW Hunt, I've decided to take on a sector survey as my first deep space expedition. But I'm running into problems at the planning stage. Specifically, finding or building the needed tools to collect and analyze the data.

My Goal:

I'm curious on whether or not any patterns exist in star system formation. Before we started discovering exoplanets, our solar system was assumed to be the standard model for planetary formation - rocky worlds close in, gas giants further out. Today, the model is more complex, suggesting that some areas of the galaxy are more friendly to certain planet types, as well as certain stars are more or less friendly to certain planet types.

Of course, the Stellar Forge is not a perfect model, but it is what is used for the Elite universe - the Elite's "laws of nature" if you will. I'm under no illusions that studying planet formation in Elite will lead to real-life breakthroughs (though that would be cool), but it might lead to a greater understanding of this model galaxy we are priviledged to fly in.

My Proposed Method:

After some thought on the problem, I decided that a survey, focussing on a particular stellar class and a particular sector, would be a good way to gather data for this project. At each star of a given type, determine the planets orbiting it, noting their types and orbits. Once enough stars had been cataloged in this fashion, group the data together to see if a pattern emerges. Since this would be my first expedition, I figured 100 stars should be a good sample size - big enough that if a pattern exists it should become apparent, but small enough that a newbie like myself won't overextend himself. I hope to be able to produce a graph (or series of graphs) that would show how many planets orbit at what distances from their parent stars.

The Problem:

According to the guides I have read, there are 16 different planet types. Building a spreadsheet that will allow me to record each planet type, and to do so for certain distances from the parent star, and ultimately produce totals of planets per distance range, has on a first pass resulted in a huge spreadsheet that is almost impossible to navigate. I could easily see myself making simple errors in data entry that could spoil the experiment.

I have been told that a database would be better suited to crunch this much information, but I have no experience with building databases - I don't even know what programs I can use to build a database.

As for specialized tools like EDDiscovery - my experience with them is limited, but they are more suited to showing people where you've been and what's there, and less suited for the kind of analysis I want to perform.

So, I would like to ask if there is some way to either streamline the spreadsheet, to build a database or to create a tool without needing to get a programming degree first. Any advice is welcome.
 

Jon474

Banned
As for specialized tools like EDDiscovery - my experience with them is limited, but they are more suited to showing people where you've been and what's there, and less suited for the kind of analysis I want to perform..

Don't write EDD off too quickly. You can now scan and collect data in EDD and then export it to other applications. The journal file is pretty comprehensive.

Flying happy
Jon
Type-6E
 
Once ED Discovery has read all your journals then you can export all the scan data to csv - including the star types and the planet type and semi-major axis for the bodies you scan. It then becomes an exercise in getting the data from that into the form you want to present it.

If you're looking at 100 systems then that's probably doable in a spreadsheet - if you were looking at taking the json dump of all the known bodies from eddb then learning how to get that into a proper database would start to become necessary but that sounds like an exercise for a later date at the minute...
 
What the honoured CMDRs above said. These days we've got the luxury of all that data in the Journal, so using a spreadsheet for *entering* data etc. is wasted time in most cases (except you really have a very specific topic/interest not covered by the Journal). Of course spreadsheets can be quite usefull for analysing and visualising the available data.

A propos data: There's tons - or rather Gigabytes - of data already available to play around with, e.g. here: https://eddb.io/api.

Please do post your progress here, as you'll get great input/feedback and hints towards knowledge that might be buried in some old threads.
 
Okay, update.

Frist, thanks for the responses thus far. Especially thanks to those who pointed out that ED Discovery can export its data. This will let me deal with crunching the data after I get back, rather than while I'm out in field. Among other things, this will also free me for secondary tasks, like searching for volcanic activity and charting for worlds rich in FSD synthesis materials.

However, after looking at the data I've already collected, I can see I'll still have to manually transfer the data I need into a form that I can crunch effectively. I've worked out a better spreadsheet for my survey, and have only to incorporate graph functionality into it. By the time 2.3 drops, it should be ready to go.

Goemon: I had a look at the linked thread; I confess I'm a little confused as to how it can help. It's been over 20 years since I worked with any programming language, and I have zero experience with Python. Sorry.

A couple of questions for everyone:

First, I see that EDDiscovery has the ability to reset the journal; I'm hoping to use this just before I start my survey. If I made sure my data was synced with EDSM before resetting, would there be any consequences I should know about?

Second, when it comes to breaking my findings down by planet type, are there any particular groupings people would like to see? Breakdowns of rocky planets vs gas gaints, say? Please let me know!
 
How do we red-headed step children (xbox one owners) do something similar?
I don't know of any journal or log that we can make use of.
I have just started to dip my toe in to surveying with a max-jump-range-bubble survey from a random system where I laid my hat.
So far, even getting a list of systems to visit and those visited is an exercise in sharpening a pencil. It's not good enough.

If I set GalMap colours to visited/not visited, this goes some way to helping but I would like to exclude all systems from my Nav Panel that are filtered out in the GalMap.
So, once I've scanned all systems within 10LY, I only see systems >10LY on my Nav Panel list.
 

Jon474

Banned
A couple of questions for everyone:

First, I see that EDDiscovery has the ability to reset the journal; I'm hoping to use this just before I start my survey. If I made sure my data was synced with EDSM before resetting, would there be any consequences I should know about?

Second, when it comes to breaking my findings down by planet type, are there any particular groupings people would like to see? Breakdowns of rocky planets vs gas gaints, say? Please let me know!

Re First: Not sure if this is the same thing, but I reset my EDD database before DWE. I sync'd to EDSM, closed EDD, took a copy of the database file and renamed it. Deleted the original, re-started EDD and off I went. Make sure you tick "Sync to EDSM only" in Settings and not both ways and, I think, you are pretty much good to go.

Re Second: my preference, as much detail as you can bear! Give people the data and they can slice it how they want. Record Axial Tilt if you can...my particular favourite!

Good luck, Cmdr

Flying happy
Jon
Type-6 Explorer
 
Back
Top Bottom