Ideally FD should just use one of the catelog ids for one of the systems. I did actually post a bug for the m/M Carinae case but it hasn't changed in the game. Hopefully none of these systems are ever involved in a mission in game.
Discussion What is the most efficient way to crowdsource the 3D system coordinates
- Thread starter wolverine2710
- Start date
Ideally FD should just use one of the catelog ids for one of the systems. I did actually post a bug for the m/M Carinae case but it hasn't changed in the game. Hopefully none of these systems are ever involved in a mission in game.
I am really testing Redwizzards trillatation page now. I am about 9k ly out now. I have one improvement suggestion.
Then far out from the core systems your routine to suggest reference stars could be improved. Instead of searching for stars with short names it should search for the "best" stars...
But if you are closer ti the core system. Then the search for short star names is good.
Then far out from the core systems your routine to suggest reference stars could be improved. Instead of searching for stars with short names it should search for the "best" stars...
But if you are closer ti the core system. Then the search for short star names is good.
It only shows the systems that are best (in that they differentiate the most candidates or will increase the margin of the best candidate if you already have enough references to get coordinates). So there isn't really a way of measuring "best" that can distinguish the suggested systems. That's why it does it by length of the name. There is actually code to do it by distance from the system if we have coordinates but that is a bit too memory hungry and slow at the moment.
Last edited:
When you're far out cartographing, it would be better to choose systems with very extreme coordinates:
Fe 1 Sector LH-A b15-0
Bleae Aescs OU-D d13-12
Pheia Ain LD-K c8-26
HIP 61012
Stuemeae UZ-X c1-1867
Synuefe PM-H c24-0
Fe 1 Sector LH-A b15-0
Bleae Aescs OU-D d13-12
Pheia Ain LD-K c8-26
HIP 61012
Stuemeae UZ-X c1-1867
Synuefe PM-H c24-0
Yes, same here. My site asks for distances to verify known coordinates only if the expected angle between the actual system and the closest known reference is at least 15 degrees, but if no coordinates are known it's hard to make a good proposal.
Last edited:
I did the Buckyball to Sag A* and then mapped a few systems <400Ly from Sag A*. Using RedWizzard's tool I entered some extreme-coordinate systems as references, mostly 12-15 reference systems - all of the systems trilaterated OK in the tool but I think only about 3/4 of the systems got a trilaterated OK back from EDSC. The following are a handful of core-ish systems in EDSC:
Stuemeae UZ-X c1-1867
Stuemeae QD-T b3-7
Phua Aub MN-W c1-889
Phua Aub KN-W c1-8201
Phua Aub LN-W c1-987
Phua Aub LN-W c1-2999
Phua Aub CB-A c413
Phua Aub CB-A c8168
Myriesly SD-Z c27-6570
Myriesly MC-B c27-8172
Myriesly MC-B c27-573
Myriesly KH-B c27-5039
Myriesly GR-B c27-1815
Myriesly OS-B d13-4524
Myriesly JS-D b54-148
I have a question though - is Sagittarius A* excluded from being a reference system? - the back distance never appears.
Trilateration used by EDSC has some weak points - the distances submitted are only used one way, not backwards. A wrong distance submitted to EDSC, f.ex. a typo, stays inside the database forever and may prevent successful trilateration. RedWizzard & me have a way of removing wrong distances, coordinates and misspelled systems from the database (or at least not using them for any mathematics), and the errors in EDSC sum up, and will become a complete mess in a few weeks.
I want to add a way to submit distances to my site, if I find the time for it
And hopefully RedWizzard & Finwen are the first to implement my API, then hopefully others will follow, so we can get rid of the errors.
I want to add a way to submit distances to my site, if I find the time for it
And hopefully RedWizzard & Finwen are the first to implement my API, then hopefully others will follow, so we can get rid of the errors.
It's probably struggling to trilaterate Sag A* - there are a lot of distances recorded and most of them are about 26,000 Ly which isn't much help given they're spread over a small volume. With your distances it should work, I'll just need to clean up some of the useless distances.
Hey wow, for the last few systems I have mapped it is now giving a back-distance for Sagittarius A* - woot!
RedWizzard's page or EDSC? EDSC doesn't have coordiantes for Sag A*...
RedWizzard's tool. Previously when I entered Sagittarius A* as a reference system it didn't give a back-distance for it. But now it is. Most of the other systems I entered around the core got the green tick and I also added a distance to Sag A* from them. Does that mean Sag A* is locked in now in EDSC?
I've been entering Sag A* as a reference for all the systems I've mapped on the way back (roughly one every 1000Ly), they have all been successful so surely there's enough data in EDSC to trilat Sag A* now. Do you have a way to tell if the status of coordinates for Sag A* has changed in EDSC?
Yes, at least it worked. EDSC GetSystems API, queried for Sagittarius A*, returns
coord: [
25.21875,
-20.90625,
25899.96875
],
cr: 2,
commandercreate: "RedWizzard",
createdate: "2014-12-14 11:10:53",
commanderupdate: "Maddavo",
updatedate: "2015-05-04 12:14:11"
Edit: Strange... I fetched and merged EDSC systems and distances, cause I do every day, and can't remember Sag A* had coordinates. Maybe I overlooked them, maybe EDSC didn't spit them out when asked. Sometimes EDSC doesn't give all the answers you want.
coord: [
25.21875,
-20.90625,
25899.96875
],
cr: 2,
commandercreate: "RedWizzard",
createdate: "2014-12-14 11:10:53",
commanderupdate: "Maddavo",
updatedate: "2015-05-04 12:14:11"
Edit: Strange... I fetched and merged EDSC systems and distances, cause I do every day, and can't remember Sag A* had coordinates. Maybe I overlooked them, maybe EDSC didn't spit them out when asked. Sometimes EDSC doesn't give all the answers you want.
Last edited:
Has someone tried to poll distances for a specific system from EDSC/TGC lately? My script for comparing them to my own database suddenly stopped working, app. 20 hours ago. It asks EDSC, and after 30+ seconds it returns an empty answer. First I thought my script does somethiong wrong, but it worked well for 1 or 2 weeks. Now I tried JSFiddle http://jsfiddle.net/8d7szc64/ and this shows an empty answer, too.
Yes, without limiting distances to a specific system EDSC returns data (if you don't go too far backwards). EDSC missed several distances some CMDRs submitted to my site, and I wanted to submit them to EDSC again. Had many successful trilaterations, but can't continue because I can't check which distances are already stored at EDSC and which are not.
from TD:
Code:
'ARGETLÁMH',85.75,-170.6875,74.9375,'Gamma','2014-11-27 11:33:44'
'LíFTHRUTI',70.15625,-143.625,123.15625,'Gamma','2014-11-27 11:33:44'
'MANTóAC',41.75,-167.8125,119.34375,'Gamma','2014-11-27 11:33:44'
'NANTóAC',201.5,-177.8125,46.9375,'Gamma','2014-11-27 11:33:44'edit: I was juts in game and they seem to have corrected the names to the non accented characters:
Code:
ARGETLAMH, LIFTHRUTI, MANTOAC and NANTOAC
Last edited:
The JSFiddle is working for me now.
Yep, have 3-5 secs response time, and get answers with some contents ;-)
Weird thingy.
How did U fix it?
Last edited: