Repository navigation
feat(neo4j): implement and validate initial Cypher queries - #16
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #6
Stacked on #15 (retarget as the stack merges).
Queries live in
backend/src/visual_graph/graph/cypher/and are loaded byvisual_graph.graph.queries.run_query, so the backend can reuse them:objects_in_image,objects_by_class,relationships_in_image,objects_nearimages_with_two_classesimages_with_near_pattern,images_with_left_of_pattern(structural/spatial)Integration tests run every query against the sample scene and compare with the manually created graph. One test shows why relationships matter: a person and a chair co-occur in the image (class query matches), but the
NEARpattern query correctly returns nothing.Verified: 19 integration tests pass against Neo4j, ruff and mypy clean.