Markus Pfeiffer
3f51d24266
Bug fix for K_SHORTEST_PATHS ( #10389 )
...
* Add a test that reproduces k Shortest Paths bug
* Fix a bug in KShortestPathFinder
The finder was too eager to return a "shortest" path when there was actually
potentially a shorter path still to be discovered
* A little bit of cleanup
* Add missing include
* Address review comment
* Add another missed include
2019-11-11 17:37:58 +03:00
Tobias Gödderz
e2c84acfaf
Use explicit default destructors where possible ( #10166 )
2019-10-04 15:58:30 +02:00
Jan
c52f2a8315
refactoring ( #9411 )
2019-07-09 11:15:52 +02:00
Jan
9cb08ded92
make the comparison functions unambiguous ( #9349 )
...
* make the comparison functions unambiguous
* added @kaveh's suggestion
2019-07-01 16:35:28 +02:00
Jan
59b67cad40
fix various small annoyances ( #9079 )
2019-05-23 17:36:38 +02:00
Markus Pfeiffer
65d090be9d
Fix warning about incompatible types in KShortestPathsFinder ( #8936 )
2019-05-08 15:29:51 +02:00
Markus Pfeiffer
c9a35ea2fa
Improve k Shortest Paths performance ( #8889 )
...
* Only consider spur paths from after the branchpoint
from the previous path
* Cache neighbourhoods around vertices
2019-05-07 13:21:52 +02:00
Markus Pfeiffer
304e8f861d
Fix k Shortest Paths with weights, reactivate cluster tests ( #8761 )
...
* Make find in ShortestPathPriorityQueue const
* Fix k Shortest Paths with weights, reactivate cluster tests
2019-04-17 15:10:59 +02:00
Michael Hackstein
b3205dada8
USe smart-pointer in Priority Queue, it seems the usages have been correct everywhere (so no leaks) but memory responibility was hard to understand, should now be much simpler. ( #8768 )
2019-04-16 12:06:42 +02:00
Jan
449ab1ed8e
Bug fix/cppcheck 13042019 ( #8752 )
2019-04-15 10:13:56 +02:00
Markus Pfeiffer
a14386267a
k Shortest Paths ( #8715 )
...
* Add k-shortest-paths finder
2019-04-12 21:58:18 +02:00