Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Routes window has incorrect routes

See original GitHub issue

I noticed today some odd routes when trying to find a good hi sec trading hub. For instance, Pathfinder seems to think Uzistoon is connected to both Jita and Rens. Here is a copy and paste of both these routes (sorry for the messy html, just copy+pasted from browser):

Route to Jita: <td> </td>

Route to Rens: <td> </td>

Let me know if you need any additional information, thanks!

Issue Analytics

State:
Created 7 years ago
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

MorpheusXAUTcommented, Feb 15, 2017

My local pathfinder instance produces the correct path between 1V-LI2 and Jita, however the one between 1V-LI2 and Rens is slightly different, although of the same length as the result produced by e.g. dotlan or other route planning tools.

I thus assume both paths produced by my pathfinder instance should be correct. I’ve begun digging into the route generation of pathfinder and the tables used by it a bit… @ArtificialQualia Could it be you’re using an older/outdated EVE SDE for your CCP database?

As a test, could you run this query against the pathfinder database:

SELECT * FROM system_neighbour WHERE systemName LIKE 'Uzistoon';

The expected result would be a row with a jumpNodes value of Dooz:Bayuka:Sari. I guess your table will probably return something else, probably including Jita and Rens.

As a second test, could you run this query against the CCP database:

SELECT
  systems.solarSystemName
FROM
  mapSolarSystemJumps jumps INNER JOIN
  mapSolarSystems systems ON
  systems.solarSystemID = jumps.toSolarSystemID
WHERE
  jumps.fromSolarSystemID = 30000040;

The expected result would be three rows with values Dooz, Bayuka, Sari. Note that 30000040 is the solarSystemID of Uzistoon as retrieved from the mapSolarSystems table via:

SELECT systems.solarSystemID FROM mapSolarSystems systems WHERE systems.solarSystemName LIKE 'Uzistoon';

My assumption would be that your pathfinder and/or CCP database queries will return a different result, thus leading to pathfinder’s confusion in route generation. If the results are indeed different, you could try re-importing the latest EVE SDE (e.g. provided by Steve Ronuken here) and then re-running the system neighbour generation in pathfinder’s setup page. That should hopefully fix the issue.

Should the result be indeed the same as above, there’s something actually wrong in pathfinder’s code 😄

0reactions

exodus4dcommented, Feb 17, 2017

@MorpheusXAUT Thanks for the research!

@ArtificialQualia Is it possible that you did a manual search? - By using the dialog? If you have added multiple maps to it, it might be possible that there was any other connection in one of those maps that changed/shortened the route. The “refresh” icon remembers your setting when you click it. (at least until you changed your current active system).

The algorithm it selfe is called “Dijkstra algorithm”. I made some changes to it to work with Pathfinder´s data. It is not the same algorithm CCP used thats for sure, but it is basicalls doing the same. If there are multiple possible routes with the same length, the result might vary.

My implementation: https://github.com/exodus4d/pathfinder/blob/master/app/main/controller/api/route.php#L322

I guess we can close this one.