Discussion What is the most efficient way to crowdsource the 3D system coordinates

wolverine2710 · Oct 20, 2014

RedWizzard said:
That's the one. It's a little annoying in that you have to resort twice when you jump to a new system. I might see what I can do about that tomorrow.

Didn't want to mention that but your are right. Sleep well as iirc in your TZ it is almost night.

Will have a test report ready for when you wake up. Have some little suggestions/findings for a potential improvement of your already excellent tool. Nothing major though ;-)

Have you decided how you are going to name your tool?

RedWizzard · Oct 20, 2014

wolverine2710 said:
Didn't want to mention that but your are right. Sleep well as iirc in your TZ it is almost night.

Will have a test report ready for when you wake up. Have some little suggestions/findings for a potential improvement of your already excellent tool. Nothing major though ;-)

Have you decided how you are going to name your tool?

I've got a couple of things I want to change too. Feel free to make any suggestions. And any suggestions for names (I haven't really thought about it yet).

gazelle · Oct 20, 2014

RedWizzard said:
Yeah, I'm finding that too. The cases I'm testing are:
1. Taran (-42.5, 45.46875, -3) to Ross 1051 (-37.21875, 44.5, -5.0625), ED shows 5.752
2. Taran (-42.5, 45.46875, -3) to Hagalaz (-50.59375 45.15625 11.09375), ED shows 16.255
3. LFT 668 (-19.03125, 25.65625, -24.21875) to Loga (-79.78125, 36.53125, -42.0625), ED shows 64.243
4. LHS 3297 (-36.46875, 22.6875, -16.53125) to Haras (-118.75, 14.40625, -21.40625), ED shows 82.840

I found a sollution:

multiply the x/y/z with 256 to get an integer
calculate the distance with the integers
round the result to 1/256 accuracy trunc((res*256)+0.5)/256
again divide by 256 and round the result to 3 decimals

Which would be equal to use 65536 instead of 1024 in your method "b" I think.

b. round(round(calculated_distance * 65536)/65536, 3)

Harbinger · Oct 20, 2014

Seems to work OK on php after making some modifications to my function courtesy of gazelle's information.

php test:

Code:

<?php

echo "<pre>";
echo "Taran to Ross 1051: ".calculate_distance(array("x" => -42.5, "y" => 45.46875, "z" => -3), array("x" => -37.21875, "y" => 44.5, "z" => -5.0625))." LY.\n";
echo "Taran to Hagalaz: ".calculate_distance(array("x" => -42.5, "y" => 45.46875, "z" => -3), array("x" => -50.59375, "y" => 45.15625, "z" => 11.09375))." LY.\n";
echo "LFT 668 to Loga: ".calculate_distance(array("x" => -19.03125, "y" => 25.65625, "z" => -24.21875), array("x" => -79.78125, "y" => 36.53125, "z" => -42.0625))." LY.\n";
echo "LHS 3297 to Haras: ".calculate_distance(array("x" => -36.46875, "y" => 22.6875, "z" => -16.53125), array("x" => -118.75, "y" => 14.40625, "z" => -21.40625))." LY.\n";
echo "</pre>";

function calculate_distance(array $from, array $to)
{
    $distance=sqrt(
                     pow((($to["x"] * 256) - ($from["x"] * 256)), 2) +
                     pow((($to["y"] * 256) - ($from["y"] * 256)), 2) +
                     pow((($to["z"] * 256) - ($from["z"] * 256)), 2)
                   );

    $distance*=256;
    $distance+=0.5;
    $distance=floor($distance);
    $distance/=pow(256, 2);

    return round($distance, 3);
}

?>

Output:

Code:

Taran to Ross 1051: 5.752 LY.
Taran to Hagalaz: 16.255 LY.
LFT 668 to Loga: 64.243 LY.
LHS 3297 to Haras: 82.84 LY.

Snuble · Oct 20, 2014

The most isolated system that I found in Smackers data is Tring, with 11.325LY to nearest system WREDGUIA DJ-0 B47-1

So inside the pill you need 11.325LY jump capability to visit all "known" systems. Correct?

Harbinger · Oct 20, 2014

Snuble said:
The most isolated system that I found in Smackers data is Tring, with 11.325LY to nearest system WREDGUIA DJ-0 B47-1

So inside the pill you need 11.325LY jump capability to visit all "known" systems. Correct?

Sounds about right, I managed to navigate the pill without problems during mapping with a sidewinder that has a 12.26 LY per jump range.

wolverine2710 · Oct 20, 2014

WREDGUIA LW-E D11-129 issue - response from support

Harbinger and RedWizzard. Just in case support hasn't responded to you about the ticket you iirc both created. Others can do the beneath also and ticket it. The more data supports gets, the better.

Response from support:

Hi Jan,

Would you be able to add the following 3 lines of code to the 'Network' section of your AppConfig.xml file, then grab a netlog for us should this issue happen again? You Can find your AppConfig file in the same folder that you have installed the EliteDangerous.exe to. The 3 lines you need to add are:

VerboseLogging="1"
ReportSentLetters="1"
ReportReceivedLetters="1"

If you have any issues let us know.

Thanks, Ashley

The actually meant EliteDangerous32.exe. On my system its in C:\Users\wolverine\AppData\Local\Frontier_Developments\Products\FORC-FDEV-D-1001. I've flown to a few different sytems and tried to enter WREDGUIA LW-E D11-129. Does not work.

JesusFreke · Oct 20, 2014

RedWizzard said:
Sagittarius A*
I have 17 distances to the black hole now. Trilateration gives me (25.46875, -20.96875, 25899.96875), but I still get errors in the distances with those coordinates. I've adopted a new strategy: I do a brute force search of all 1/32 Ly grid coordinates in a 5x5x5 Ly cube around the trilateration results.

I grabbed your 17 distances and tried my algorithm to map out the candidate region. It looks like the candidate region is way too big for a star this far out, using only references from inside the pill. We just can't get the angular precision to resolve it. I let my algorithm try 60000 grid-aligned points, and it wasn't even close to fully mapping out the candidate region. For comparison, for most stars within the pill, the candidate region is fully mapped out after less than 1000 points.

wolverine2710 · Oct 20, 2014

Crowd sourcing when the pill gets bigger.

I've contacted Michael Brookes today about a partial list of sytem coordinates in the future:

Hello Mr Brookes,

Thanks for the information about SB2 having 600-607 star systems instead of 570. Very much appreciated.

If SB3 (or a potential SB4) has more star systems in the bubble then SB2 (which you probably can't tell me atm) would it be possible for you to supply us "crowd sourcers" with a new list when SB3 goes live - or shortly after that. As you have been so kind to do for us with SB2. I don't mind if its only partial list because of PG generated systems - as has been the case with SB2.

With kind regards,
Jan Bessels

Michael Brookes: A partial list should be possible

To make it CLEAR. This is NOT a confirmation that SB3 could/will have more star systems then SB2. But if at a certain point in time the bubble expands then Michael Brookes will try to give us again a partial list.

That partial list could help us to define better reference points for THAT bubble then the current reference points (in the current bubble) perhaps could.

JesusFreke · Oct 20, 2014

gazelle said:
I found a sollution:

multiply the x/y/z with 256 to get an integer

calculate the distance with the integers

round the result to 1/256 accuracy trunc((res*256)+0.5)/256

again divide by 256 and round the result to 3 decimals

Which would be equal to use 65536 instead of 1024 in your method "b" I think.

b. round(round(calculated_distance * 65536)/65536, 3)

Hmm, I could have sworn I tried 65536 as well. I've give it a shot when I get home tonight.

JesusFreke · Oct 20, 2014

wolverine2710 said:
Harbinger and RedWizzard. Just in case support hasn't responded to you about the ticket you iirc both created. Others can do the beneath also and ticket it. The more data supports gets, the better.

Response from support:

Hi Jan,

Would you be able to add the following 3 lines of code to the 'Network' section of your AppConfig.xml file, then grab a netlog for us should this issue happen again? You Can find your AppConfig file in the same folder that you have installed the EliteDangerous.exe to. The 3 lines you need to add are:

VerboseLogging="1"
ReportSentLetters="1"
ReportReceivedLetters="1"

If you have any issues let us know.

Thanks, Ashley

The actually meant EliteDangerous32.exe. On my system its in C:\Users\wolverine\AppData\Local\Frontier_Developments\Products\FORC-FDEV-D-1001. I've flown to a few different sytems and tried to enter WREDGUIA LW-E D11-129. Does not work.

Oooo, I wonder if there's any other logging stuff like that we could turn on, to get some extra data..

TornSoul · Oct 20, 2014

Here are some test coordinates, that I've found in my random testing.

Currently my program does not catch these and reports a wrong p0 value (working on fixing that somehow - Lots still to try - So I'm hopeful

)

I would be interested in hearing if the rest of you catch these.
If not - It's some good test cases to tweak your program with.
If yes: Would be interested in hearing how you catch them

These are 8 sets of coordinates - out of 1 million random ones. The only ones I didn't catch - So just 0.0008% false positives. But dangit I want to catch those as well

These are the coordinates:
p0 is the one to determine given the other values.
p1-p5 are systems you have distances for.
The format is x,y,z,r - where r is the distance to p0 with 3 decimals

I'm copying them from excel, as i think thats the easiest way for people to lift them from here, as the forums seems to maintain the "tab" char

Code:

p0	-134.625	33.21875	-38.0625	0.000
p1	-101.09375	11	-24.09375	42.581
p2	-33.5625	33.125	13.46875	113.442
p3	-12.125	26	22.875	137.010
p4	-17.71875	19.125	19.59375	131.110
p5	-21.34375	22.375	16.25	126.096
				0.000
p0	-134.625	33.21875	-38.0625	0.000
p1	-60.84375	23.84375	-50.75	75.449
p2	-19	22.5625	-28.21875	116.532
p3	-18.21875	26.5625	-6.34375	120.834
p4	-21.96875	29.09375	-1.71875	118.445
p5	-29.4375	34.46875	21.53125	120.902
				0.000
p0	-74.09375	36.5625	-40.1875	0.000
p1	-113.25	16.78125	-28.34375	45.440
p2	-92.59375	15.1875	-9.15625	41.977
p3	-22	36	1	66.411
p4	-7.5625	42.59375	0.6875	78.317
p5	0.125	41.46875	11.96875	90.845
				0.000
p0	-118.75	14.40625	-21.40625	0.000
p1	-84.6875	50.21875	-6.40625	51.651
p2	-1.6875	29.65625	2.03125	120.356
p3	-7.90625	34.71875	2.125	115.120
p4	-21.96875	29.09375	-1.71875	99.850
p5	-43.78125	62.4375	-0.25	91.514
				0.000
p0	-76.6875	11.09375	-10.8125	0.000
p1	-38.46875	39.25	5.40625	50.165
p2	-19.75	41.78125	-3.1875	65.129
p3	-13.34375	53.78125	12.5625	79.881
p4	-21.65625	32.21875	-16.21875	59.194
p5	-3.4375	51.59375	2.03125	84.680
				0.000
p0	-88.625	38.09375	-13.65625	0.000
p1	-88.03125	47.1875	-6.15625	11.802
p2	-36.71875	41.6875	14.125	58.983
p3	-33.21875	37.34375	12.75	61.382
p4	-18.90625	27.21875	12.59375	75.286
p5	-18.3125	18.1875	4.90625	75.397
				0.000
p0	-123.59375	25.875	-33.25	0.000
p1	-74.875	31.75	-5.96875	56.145
p2	-39.84375	29.5625	-3.90625	88.818
p3	-32.3125	26.1875	-12.4375	93.624
p4	-60.625	35.125	3.21875	73.353
p5	-14.78125	33.46875	-0.40625	113.915
				0.000
p0	-134.625	33.21875	-38.0625	0.000
p1	-69.28125	32.25	-13.90625	69.673
p2	-64	24	-41	71.285
p3	2.65625	27.09375	-9.9375	140.266
p4	-60.625	35.125	3.21875	84.757
p5	-32.875	36.15625	15.5	115.024

Let me know how it works out for you.

gazelle · Oct 21, 2014

TornSoul said:
Here are some test coordinates, that I've found in my random testing.
[...]
Let me know how it works out for you.

My program would reject them all:

Code:

Calculating: p0-1 (from TornSoul)
Matches ref: 2, pos: 2, neg: 1
New: p0-1 (-134.65625,33.21875,-38): references: 2
     p1-1              :    42.581    42.585 !
     p2-1              :   113.442   113.442
     p3-1              :   137.010   137.010
     p4-1              :   131.110   131.111 !
     p5-1              :   126.096   126.097 !
     calculations: 20; time: .032000; coordinates: 1
     no insert

Calculating: p0-2 (from TornSoul)
Matches ref: 2, pos: 1, neg: 0
New: p0-2 (unknown): data not good enough
     p1-2              :    75.449
     p2-2              :   116.532
     p3-2              :   120.834
     p4-2              :   118.445
     p5-2              :   120.902
     calculations: 20; time: .015000; coordinates: 0
     no insert

Calculating: p0-3 (from TornSoul)
Matches ref: 2, pos: 0, neg: 1
New: p0-3 (unknown): data not good enough
     p1-3              :    45.440
     p2-3              :    41.977
     p3-3              :    66.411
     p4-3              :    78.317
     p5-3              :    90.845
     calculations: 20; time: .031000; coordinates: 0
     no insert

Calculating: p0-4 (from TornSoul)
Matches ref: 2, pos: 0, neg: 1
New: p0-4 (unknown): data not good enough
     p1-4              :    51.651
     p2-4              :   120.356
     p3-4              :   115.120
     p4-4              :    99.850
     p5-4              :    91.514
     calculations: 20; time: .016000; coordinates: 0
     no insert

Calculating: p0-5 (from TornSoul)
Matches ref: 2, pos: 1, neg: 0
New: p0-5 (unknown): data not good enough
     p1-5              :    50.165
     p2-5              :    65.129
     p3-5              :    79.881
     p4-5              :    59.194
     p5-5              :    84.680
     calculations: 20; time: .031000; coordinates: 0
     no insert

Calculating: p0-6 (from TornSoul)
Matches ref: 2, pos: 1, neg: 1
New: p0-6 (unknown): data not good enough
     p1-6              :    11.802
     p2-6              :    58.983
     p3-6              :    61.382
     p4-6              :    75.286
     p5-6              :    75.397
     calculations: 20; time: .016000; coordinates: 0
     no insert

Calculating: p0-7 (from TornSoul)
Matches ref: 2, pos: 1, neg: 1
New: p0-7 (unknown): data not good enough
     p1-7              :    56.145
     p2-7              :    88.818
     p3-7              :    93.624
     p4-7              :    73.353
     p5-7              :   113.915
     calculations: 20; time: .015000; coordinates: 0
     no insert

Calculating: p0-8 (from TornSoul)
Matches ref: 2, pos: 1, neg: 2
New: p0-8 (-134.625,33.25,-38.0625): references: 2
     p1-8              :    69.673    69.673
     p2-8              :    71.285    71.289 !
     p3-8              :   140.266   140.268 !
     p4-8              :    84.757    84.756 !
     p5-8              :   115.024   115.024
     calculations: 20; time: .032000; coordinates: 1
     no insert

It did came up with coordinates for p0-1 and p0-8 but the crosscheck doesn't succeed.
My algorithm works like:

permutate over all references with 3 coords
- calculate the two possible coords
- crosscheck distance with remaining references
- if all match remember calc-coords
iterate over all remembered calc-coords
- crosscheck distance with all references
- if all match remember add-coords
if there is only one add-coord -> insert
else -> no insert

Debug output for p0-1 calculation:

Code:

===============================================================================
Calculating: p0-1 (from TornSoul)
-------------------------------------------------------------------------------
 To: p1-1 (-3235,352,-771), ly: 42.581
 To: p2-1 (-1074,1060,431), ly: 113.442
 To: p3-1 (-388,832,732), ly: 137.010
Pp: (-134.625,33.21875,-38.03125) (-4308,1063,-1217)
Pn: (-135.5625,32.875,-36.15625) (-4338,1052,-1157)
ref check p4	p4-1 (-567,612,627), ly: 131.11
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 0.425 4195.095 4195.520
ref check p4	neg diff 0.678 4194.842 4195.520
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 0.013 131.097 131.110
ref check p4	neg diff 0.021 131.089 131.110
ref check p4	p5-1 (-683,716,520), ly: 126.096
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 0.446 4034.626 4035.072
ref check p4	neg diff 0.303 4035.375 4035.072
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 0.014 126.082 126.096
ref check p4	neg diff 0.009 126.105 126.096
-------------------------------------------------------------------------------
 To: p1-1 (-3235,352,-771), ly: 42.581
 To: p2-1 (-1074,1060,431), ly: 113.442
 To: p4-1 (-567,612,627), ly: 131.110
Pp: (-134.4375,33.28125,-38.4375) (-4302,1065,-1230)
Pn: (-134.78125,33.15625,-37.71875) (-4313,1061,-1207)
ref check p4	p3-1 (-388,832,732), ly: 137.01
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 0.099 4384.419 4384.320
ref check p4	neg diff 0.510 4383.810 4384.320
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 0.003 137.013 137.010
ref check p4	neg diff 0.016 136.994 137.010
ref check p4	p5-1 (-683,716,520), ly: 126.096
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 0.043 4035.029 4035.072
ref check p4	neg diff 0.415 4034.657 4035.072
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 0.001 126.095 126.096
ref check p4	neg diff 0.013 126.083 126.096
-------------------------------------------------------------------------------
 To: p1-1 (-3235,352,-771), ly: 42.581
 To: p2-1 (-1074,1060,431), ly: 113.442
 To: p5-1 (-683,716,520), ly: 126.096
Pp: (-134.65625,33.21875,-38.03125) (-4309,1063,-1217)
Pn: (-137.75,31.40625,-31.375) (-4408,1005,-1004)
ref check p4	p3-1 (-388,832,732), ly: 137.01
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 0.449 4384.769 4384.320
ref check p4	neg diff 2.080 4382.240 4384.320
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 0.014 137.024 137.010
ref check p4	neg diff 0.065 136.945 137.010
ref check p4	p4-1 (-567,612,627), ly: 131.11
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 0.466 4195.986 4195.520
ref check p4	neg diff 4.113 4191.407 4195.520
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 0.015 131.125 131.110
ref check p4	neg diff 0.129 130.981 131.110
-------------------------------------------------------------------------------
 To: p1-1 (-3235,352,-771), ly: 42.581
 To: p3-1 (-388,832,732), ly: 137.010
 To: p4-1 (-567,612,627), ly: 131.110
Pp: (-132.78125,33.40625,-41.625) (-4249,1069,-1332)
Pn: (-134.6875,33.1875,-37.9375) (-4310,1062,-1214)
ref check p4	p2-1 (-1074,1060,431), ly: 113.442
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 1.505 3631.649 3630.144
ref check p4	neg diff 0.030 3630.114 3630.144
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 0.047 113.489 113.442
ref check p4	neg diff 0.001 113.441 113.442
ref check p4	p5-1 (-683,716,520), ly: 126.096
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 1.355 4033.717 4035.072
ref check p4	neg diff 0.025 4035.047 4035.072
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 0.042 126.054 126.096
ref check p4	neg diff 0.001 126.095 126.096
-------------------------------------------------------------------------------
 To: p1-1 (-3235,352,-771), ly: 42.581
 To: p3-1 (-388,832,732), ly: 137.010
 To: p5-1 (-683,716,520), ly: 126.096
Pp: (-134.65625,33.21875,-38.03125) (-4309,1063,-1217)
Pn: (-142.84375,15.15625,-16.75) (-4571,485,-536)
ref check p4	p2-1 (-1074,1060,431), ly: 113.442
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 0.440 3630.584 3630.144
ref check p4	neg diff 43.372 3673.516 3630.144
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 0.014 113.456 113.442
ref check p4	neg diff 1.355 114.797 113.442
ref check p4	p4-1 (-567,612,627), ly: 131.11
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 0.466 4195.986 4195.520
ref check p4	neg diff 24.104 4171.416 4195.520
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 0.015 131.125 131.110
ref check p4	neg diff 0.753 130.357 131.110
-------------------------------------------------------------------------------
 To: p1-1 (-3235,352,-771), ly: 42.581
 To: p4-1 (-567,612,627), ly: 131.110
 To: p5-1 (-683,716,520), ly: 126.096
Pp: (-134.65625,33.21875,-38) (-4309,1063,-1216)
Pn: (-124.0625,25.6875,-56.8125) (-3970,822,-1818)
ref check p4	p2-1 (-1074,1060,431), ly: 113.442
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 0.014 3630.130 3630.144
ref check p4	neg diff 44.289 3674.433 3630.144
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 0 113.442 113.442
ref check p4	pos match
ref check p4	neg diff 1.384 114.826 113.442
ref check p4	p3-1 (-388,832,732), ly: 137.01
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 0.005 4384.325 4384.320
ref check p4	neg diff 12.648 4396.968 4384.320
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 0 137.010 137.010
ref check p4	pos match
ref check p4	neg diff 0.395 137.405 137.010
ref check p4	add pos
-------------------------------------------------------------------------------
 To: p2-1 (-1074,1060,431), ly: 113.442
 To: p3-1 (-388,832,732), ly: 137.010
 To: p4-1 (-567,612,627), ly: 131.110
Pp: (-134.65625,33.21875,-38) (-4309,1063,-1216)
Pn: (-137.65625,32.59375,-31.59375) (-4405,1043,-1011)
ref check p4	p1-1 (-3235,352,-771), ly: 42.581
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 0.134 1362.726 1362.592
ref check p4	neg diff 17.256 1379.848 1362.592
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 0.004 42.585 42.581
ref check p4	neg diff 0.539 43.120 42.581
ref check p4	p5-1 (-683,716,520), ly: 126.096
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 0.022 4035.094 4035.072
ref check p4	neg diff 2.771 4037.843 4035.072
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 0.001 126.097 126.096
ref check p4	neg diff 0.087 126.183 126.096
-------------------------------------------------------------------------------
 To: p2-1 (-1074,1060,431), ly: 113.442
 To: p3-1 (-388,832,732), ly: 137.010
 To: p5-1 (-683,716,520), ly: 126.096
Pp: (-130.1875,36.25,-45.90625) (-4166,1160,-1469)
Pn: (-134.65625,33.21875,-38) (-4309,1063,-1216)
ref check p4	p1-1 (-3235,352,-771), ly: 42.581
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 54.034 1416.626 1362.592
ref check p4	neg diff 0.134 1362.726 1362.592
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 1.689 44.270 42.581
ref check p4	neg diff 0.004 42.585 42.581
ref check p4	p4-1 (-567,612,627), ly: 131.11
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 5.232 4200.752 4195.520
ref check p4	neg diff 0.027 4195.547 4195.520
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 0.164 131.274 131.110
ref check p4	neg diff 0.001 131.111 131.110
-------------------------------------------------------------------------------
 To: p2-1 (-1074,1060,431), ly: 113.442
 To: p4-1 (-567,612,627), ly: 131.110
 To: p5-1 (-683,716,520), ly: 126.096
Pp: (-45.9375,134.6875,-35.5625) (-1470,4310,-1138)
Pn: (-134.65625,33.21875,-38) (-4309,1063,-1216)
ref check p4	p1-1 (-3235,352,-771), ly: 42.581
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 2986.624 4349.216 1362.592
ref check p4	neg diff 0.134 1362.726 1362.592
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 93.332 135.913 42.581
ref check p4	neg diff 0.004 42.585 42.581
ref check p4	p3-1 (-388,832,732), ly: 137.01
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 289.920 4094.400 4384.320
ref check p4	neg diff 0.005 4384.325 4384.320
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 9.060 127.950 137.010
ref check p4	neg diff 0 137.010 137.010
ref check p4	neg match
-------------------------------------------------------------------------------
 To: p3-1 (-388,832,732), ly: 137.010
 To: p4-1 (-567,612,627), ly: 131.110
 To: p5-1 (-683,716,520), ly: 126.096
Pp: (-100.34375,26.25,-81.96875) (-3211,840,-2623)
Pn: (-134.65625,33.21875,-38) (-4309,1063,-1216)
ref check p4	p1-1 (-3235,352,-771), ly: 42.581
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 552.773 1915.365 1362.592
ref check p4	neg diff 0.134 1362.726 1362.592
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 17.274 59.855 42.581
ref check p4	neg diff 0.004 42.585 42.581
ref check p4	p2-1 (-1074,1060,431), ly: 113.442
ref check p4	INTEGER, accuracy 3
ref check p4	pos diff 103.766 3733.910 3630.144
ref check p4	neg diff 0.014 3630.130 3630.144
ref check p4	LIGHTYEAR, accuracy 3
ref check p4	pos diff 3.243 116.685 113.442
ref check p4	neg diff 0 113.442 113.442
ref check p4	neg match
-------------------------------------------------------------------------------
Matches ref: 2, pos: 2, neg: 1
New: p0-1 (-134.65625,33.21875,-38): references: 2
     p1-1              :    42.581    42.585 !
     p2-1              :   113.442   113.442
     p3-1              :   137.010   137.010
     p4-1              :   131.110   131.111 !
     p5-1              :   126.096   126.097 !
     calculations: 20; time: .015000; coordinates: 1
     no insert

wolverine2710 · Oct 21, 2014

The OP has been updated. I still have to put the urls there. Let me know if it now better represents our current status and the future direction of the crowd source effort.

Harbinger: Don't want to get mental and scource this thread for the url of your tool. Can you please post it here.
TornSoul. I believe you have made your tool public. Can you give me the url.

I have the url for the tools of TunaMage and RedWizzard.

I WILL be forgetting someone. If someone has created a program to the public please give me the url of your program. It will be placed on the OP. I've said it before, I will say it again in the future but want to make this absolutely clear to everyone. COMMANDERS YOU ROCK.

Its 1:49 AM now. Hence time to go to bed.

Harbinger · Oct 21, 2014

http://coords.is-found.org/

TornSoul · Oct 21, 2014

gazelle said:
My program would reject them all:

It did came up with coordinates for p0-1 and p0-8 but the crosscheck doesn't succeed.

Thanks for the feedback.

Crosscheck catches them - super.

--

I did find a simple fix myself (just done running tests to confirm) - So I also now catch them.

Still - Some good (as in being nasty) coords to test on I think.

**********

@wolverine2710

URL is in my sig actually

But here you go: http://EDStarCoordinator.com

And yes it's public.

TornSoul · Oct 21, 2014

ROFL - Just found out that my public code actually already had the ability to catch those 8 bad cases.

For my test suite I had turned everything down (off actually) as I wanted to log statistics for everything - Even the bad stuff, hence those 8 slipped through in my test suite. Kinda ironic

Oh I should mention also : EDSC now only rejects 3% of cases (with 5 reference stars) - Still without letting any false positives through.
Working on getting that number even better - Pretty much just for the hell of it. As a rejection rate of just 2% is "in the noise" (and is probably mostly due to it being random data with bad edge cases)

wolverine2710 · Oct 21, 2014

TornSoul said:
@wolverine2710
URL is in my sig actually
But here you go: http://EDStarCoordinator.com
And yes it's public.

I'm having a deja vu here. I'm again getting the following message: "This is not the page you are looking for!"

OK. Thats it, last post, sleepy sleepy.

TornSoul · Oct 21, 2014

Fixed.
And thanks for letting me know.

I think I know what the issue might be... Testing to confirm, so it can be avoided for good in the future.

RedWizzard · Oct 21, 2014

gazelle said:
I found a sollution:

multiply the x/y/z with 256 to get an integer

calculate the distance with the integers

round the result to 1/256 accuracy trunc((res*256)+0.5)/256

again divide by 256 and round the result to 3 decimals

Which would be equal to use 65536 instead of 1024 in your method "b" I think.

b. round(round(calculated_distance * 65536)/65536, 3)

That's the closest to working yet, but it still doesn't exactly match for all my distance data. Can you check these ones in case I've made a mistake?

Code:

system1, system2, deltax, deltay, deltaz, eddistance
WREDGUIA UR-Q B46-2, HIP 91906, 10.3125, -0.3125, -16.15625, 19.17
LP 229-17, 35 Draconis, 62.09375, -42.71875, 37.34375, 84.114
LHS 534, Arabha, 62.53125, -31.875, -4.8125, 70.351
SZ Ursae Majoris, Clotti, 74.96875, -25.21875, -7.71875, 79.472
LHS 3749, Demeter, -14.21875, -28.34375, -30, 43.653
Ross 1069, Sol, -50.53125, 10.625, 1.03125, 51.647
AGKR 199, HIP 105906, 27.40625, -15.90625, 2.25, 31.767
LP 71-165, Jurua, 39.9375, -12.75, 48.53125, 64.131
Liabefa, Wolf 497, -77.125, -2.46875, -67.96875, 102.83

deltax is the difference in x coordinates for the systems
eddistance is the distance reported in the game

Discussion What is the most efficient way to crowdsource the 3D system coordinates

wolverine2710

Tutorial & Guide Writer

RedWizzard

gazelle

Harbinger

Snuble

Harbinger

wolverine2710

Tutorial & Guide Writer

JesusFreke

wolverine2710

Tutorial & Guide Writer

JesusFreke

JesusFreke

TornSoul

gazelle

wolverine2710

Tutorial & Guide Writer

Harbinger

TornSoul

TornSoul

wolverine2710

Tutorial & Guide Writer

TornSoul

RedWizzard