You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A note here that the given nodes (4,6,9) contain no edges:
The MRE shows that adding the nodes via add_nodes_from, or giving all nodes self-loops before do not fix the issue. With that said, adding an edge between two distinct nodes does add the nodes to the cuGraph implementation.
Granted this is not expected behavior, especially in the case of simulating edge rewiring or working with sparse graphs.
Code of Conduct
I agree to follow cuGraph's Code of Conduct
I have searched the open bugs and have found no duplicates for this bug report
The text was updated successfully, but these errors were encountered:
Hi @casonk , so sorry for the delay in responding.
The problem you're seeing is due to the lack of support for isolated vertices in the cugraph python library (see #1478). In your example above, nodes 4, 6, 9 are isolated and do not appear in the resulting edgelist that cugraph uses to create the graph structure on the GPU:
We now have support for isolated vertices in the C/C++ and pylibcugraph libraries, but we have not finished updating the cugraph python library. I don't think we'll be able to finish adding support for it in the 24.04 release, but I'll prioritize it higher so it should be in the 24.06 release (and if you can use nightly builds, you should be able to see support added sooner).
In the meantime, if you only need single-GPU support, I'd recommend using NetworkX with the nx-cugraph backend (README, blog) since the nx-cugraph backend correctly handles isolated vertices.
The nx-cugraph NetworkX backend uses the same cuGraph C++/CUDA library as the cugraph python library to GPU accelerate NetworkX. You should see approximately the same speedup using NetworkX+nx-cugraph as you'd see with the cugraph python library, especially for larger graphs.
I'll update this issue once we have support for isolated vertices, probably in 24.06.
Version
23.10.0
Which installation method(s) does this occur on?
Docker
Describe the bug.
Nodes exiting in a networkX graph do not proprly port to a cuGraph graph despite multiple approaches.
In MRE you can see nodes 4, 6, & 9 are always missing
Minimum reproducible example
Relevant log output
Environment details
Other/Misc.
A note here that the given nodes (4,6,9) contain no edges:
The MRE shows that adding the nodes via
add_nodes_from
, or giving all nodes self-loops before do not fix the issue. With that said, adding an edge between two distinct nodes does add the nodes to the cuGraph implementation.Granted this is not expected behavior, especially in the case of simulating edge rewiring or working with sparse graphs.
Code of Conduct
The text was updated successfully, but these errors were encountered: