Closed andyjulin-bby closed 3 years ago
Thanks for reporting this. Sounds like a bug as the current single GPU version should ignore weights. We are looking into it.
One option is to use the new multi-GPU version which uses edge weights if the input graph is weighted. https://github.com/rapidsai/cugraph/issues/1313#issuecomment-747636762. The single GPU variant of this new version should also be accessible at the C++ layer https://github.com/rapidsai/cugraph/blob/branch-0.18/cpp/tests/experimental/pagerank_test.cpp#L251
Also, we are going to connect the upgraded PageRank backend (which accepts weights) to the single-GPU API in this release (0.18). This bug should go away as we do so. I opened #1331 to track the progress of this effort. Hope that helps!
Glad to hear it! Thank you for looking into this so quickly.
closed by #1332 and #1331
Describe the bug When using
cugraph.pagerank
on a graph initialized withfloat
values for theedge_attr
parameter, the returned values are well outside the [0, 1] range expected by the PageRank calculation (often by many orders of magnitude). If the underlying values are instead ofint
type, the calculation works as expected. The function is currently supposed to ignore the weights column for the calculation, so it seems to purely be a bug.Steps/Code to reproduce bug
Output:
Expected behavior The returned PageRank values should all be in [0, 1], and presumably match when the weights are
1
and1.0
.Output:
Environment overview (please complete the following information)
Environment details Please run and paste the output of the
cugraph/print_env.sh
script here, to gather any other relevant environment detailsClick here to see environment details