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.

Sign up for GitHub

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

Jump to bottom

expandK delivers different results than neo4j when k > thres #112

Open
1 of 4 tasks
cassinius opened this issue Oct 14, 2019 · 0 comments
Open
1 of 4 tasks

expandK delivers different results than neo4j when k > thres #112

cassinius opened this issue Oct 14, 2019 · 0 comments
Labels
bug

Comments

@cassinius
Copy link
Collaborator

cassinius commented Oct 14, 2019 •
edited
Loading

  • it seems that if the data set isn't large & expandK runs back and forth between already visited nodes, our results differ from neo4j's
  • formulate more test scenarios
  • create a separate test graph (small and manageable)
  • draw a decision diagram
  • once a solution is found, document extensively !!
@cassinius cassinius added the bug label Oct 14, 2019
@cassinius cassinius changed the title expandK delivers different results than neo4j when k high enough expandK delivers different results than neo4j when k > thres Dec 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cassinius