-
Notifications
You must be signed in to change notification settings - Fork 26
Kind of subgraphs matched by VF3 #5
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
Comments
0,0:19,1:12,2:5,3: is isomorphic to the query. You may confuse the homomorphism with isomorphism. |
@shaofengzeng -- thanks for your reply. Can you give your definition of homomorphism and isomorphism? And when you say
do you mean "the subgraph induced by 0 19 12 5 is isomorphic to the query"? Or something else? |
I'm sorry, i'm also confused about the results now. I haved tried the following command, |
should work |
It's very strange that I get different results on different computers. I can get the same results with g++ 5.4, and get different results with g++7.5 |
Sorry, I should have found the bug related to the wrong usage of a flag added in the last release to select between induced and non-induced subgraph isomorphism. |
Hi --
Running the example command
gives you the following matches
However, both edges
0 17
and17 0
exist in thetarget
graph, so the subgraph induced by0 12 17 19
has four edges:What kinds of subgraphs is VF3 trying to match? I thought it was "find a set of nodes in
target
s.t. the subgraph they induce is isomorphic toquery
" -- but the above example suggests it may be something different.As another example -- the subgraph induced by
0,0:19,1:12,2:5,3:
is not isomorphic toquery
-- there's an edge5 19
intarget
that isn't inquery
.(FWIW -- the VF2 implementation in
networkx
does not return either of the above examples, which IMO is the expected behavior.)Thanks!
The text was updated successfully, but these errors were encountered: