Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Enter distances to several known stars #1

Closed
Harbinger73 opened this issue Apr 20, 2015 · 7 comments
Closed

Feature request: Enter distances to several known stars #1

Harbinger73 opened this issue Apr 20, 2015 · 7 comments

Comments

@Harbinger73
Copy link

I like the way you can enter distance measurements between the last star you've visited and submit the data to EDSC but unless you're going to jump back and forth between the star with no coordinates and those with known coordinates it's not terribly effective a means of mapping the coordinates of unknown stars.
EDDiscovery could really do with a feature to manually enter distances to 5+ systems of known coordinates in a way similar to what is possible on the EDSC website.

@0xyg3nist
Copy link

Trading Data went hard with the OCR... time to start getting the OCR going for the navigation panel That way it will automatically enter all the start systems it sees there (of more than 0.5ly away)

@Majkl578
Copy link
Contributor

Hi,
preliminary support for this is in my trilateration branch, reusing trilateration math used by ed-systems/entry.html. There is still some work left though.
In meantime you can use this site: http://robert.astronet.se/Elite/ed-systems/entry.html
trilateration

@0xyg3nist: I'm afraid the data from Navigation panel are not precise enough. Any distance over 10.00Ly is listed with only one decimal place which is not enough (IIRC). So it would be applicable only to the systems below 10.00Ly...

@finwen
Copy link
Contributor

finwen commented Jun 19, 2015

Looks promissing.

Prefered place to get distance is from the Galaxy map. It has always 2 decimals.

@0xyg3nist
Copy link

It's not the decimal places per se. The accuracy is a function of the number of significant figures in the distance, and the accuracy of the sin function.
The math will sort itself out, if you can data mine ten times as much data out of ED because it's twenty-times easier to get it from a half decent OCR.
If we n00bs had an application which dragged out the screenshots and dumped them in separate folders: Galaxy map screenshots (auto cropped to the star info), commodity screens (also semi-cropped?), navigational panel screenshots (cropped), and then in a seperate process scan each folder and grab the simple data automatically, keep a repository of data the needs verification until it's two hours old and then dump it... I can't code beyond the pseudo code I learnt fifteen years ago.
Get ten locations on a star instead of five from those around it, some with some luck some are galaxy map four or five significant-figure measurements from there. The confidence factor will deal with the need to improve on those that are only 3 significant figures and beyond the sin functions' accuracy.

@Majkl578
Copy link
Contributor

@0xyg3nist: I agree it would be nice to have much more data automatically, it's a nice idea. But I'm still not sure what impact it would have if we got most of the systems with only one decimal place. I suppose it'd at least require (a lot) more system distances for trilateration (minimum is 5 now and this algorithm doesn't have nice asymptotic complexity). I believe @SteveHodge (the author of ed-systems) could tell you more about this.

And here's an update for this issue:
Trilateration

@SteveHodge
Copy link

I believe the nav panel calculates the distance from your ship position and not the primary star. That makes it quite difficult to use as the nav panel distances don't always correspond to the galaxy map distances even when the distance is less than 10 Ly and the nav panel shows 2 decimal places.

@Majkl578
Copy link
Contributor

Majkl578 commented Jul 3, 2015

Closing, trilateration was implemented in 2.3.0.0.

@Majkl578 Majkl578 closed this as completed Jul 3, 2015
finwen pushed a commit that referenced this issue Feb 13, 2016
Making my EDDiscovery up to date with master code
finwen pushed a commit that referenced this issue Apr 3, 2016
getting my fork back up to date
klightspeed referenced this issue in klightspeed/EDDiscovery Feb 16, 2017
Merge branch 'master' into master-configchanged-events
finwen pushed a commit that referenced this issue Oct 4, 2017
robbyxp1 pushed a commit that referenced this issue Aug 1, 2018
robbyxp1 pushed a commit that referenced this issue Aug 22, 2018
robbyxp1 pushed a commit that referenced this issue Apr 22, 2021
Merge pull request #3040 from Eahlstan/master
robbyxp1 pushed a commit that referenced this issue Jun 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants