-
Notifications
You must be signed in to change notification settings - Fork 311
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
[FEA] Travelling Salesman Problem (TSP) and/or Hamiltonian path #1185
Comments
@jannisborn TSP is on the roadmap for roughly the January 2021 release. We have been doing a lot of research in that areas and are now ready to make it available. Hamiltonian paths is something that we have discussed but has not made it onto the roadmap for a specific release |
@BradReesWork that sounds fantastic! |
@jannisborn breaking your feature request into two part - TSP will be in the current 0.18 release that we are workign on. Hamilton paths a little later |
This PR implements an approximated solution to the Traveling Salesperson Problem (TSP). The algorithm is exposed under ```traversal``` through a Python API taking 2D pos as input and returning a route. This PR relies on RAFT KNN: rapidsai/raft#126 Solves: #1185 Authors: - Hugo Linsenmaier (@hlinsen) Approvers: - AJ Schmidt (@ajschmidt8) - Brad Rees (@BradReesWork) - Rick Ratzel (@rlratzel) - Alex Fender (@afender) - Andrei Schaffer (@aschaffer) URL: #1360
closed by #1360 |
Is your feature request related to a problem? Please describe.
Is there any plan to integrate NP algorithms like finding Hamiltonian paths or solving the TSP?
Describe the solution you'd like
A function that you can call with an undirected, possibly weighted graph and a starting node that returns the solution to the TSP.
Additional context
networkx
implementation of TSP is pretty slow, so this would be a great feature, I think.The text was updated successfully, but these errors were encountered: