Skip to content
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

Fixes #1622: Add a traveling salesman procedure to apoc #3096

Merged
merged 3 commits into from
Dec 12, 2022

Conversation

vga91
Copy link
Collaborator

@vga91 vga91 commented Aug 2, 2022

Fixes #1622

Implemented via simulated annealing algo, i.e. https://www.baeldung.com/java-simulated-annealing-for-traveling-salesman

=== Travelling salesman

With a series of nodes like `CREATE (:City {lat:<latitude_value>, lon:<longitude_value>})`,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should support neo4j's native geo points instead

@ncordon
Copy link
Contributor

ncordon commented Sep 30, 2022

What's the use case for these procedures? They seem closer to gds than apoc

@jexp
Copy link
Member

jexp commented Sep 30, 2022

See tthe github issue.

@vga91 vga91 added the 4.4 label Oct 7, 2022
@ncordon
Copy link
Contributor

ncordon commented Oct 27, 2022

Given this is now a extended procedure, quality control here is out of Cypher Surface court.

Just a few comments: in one of the last meetings we mentioned to @jexp this could lie in GDS land and we shouldn't step in there if possible and there was some agreement in that regard.

@ncordon ncordon removed their assignment Oct 27, 2022
@conker84 conker84 merged commit 100bae8 into neo4j-contrib:4.4 Dec 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add a traveling salesman procedure to apoc
4 participants