-
Notifications
You must be signed in to change notification settings - Fork 300
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
[BUG] MG PageRank requires the parameter store_transposed to be set to True #2455
Comments
jnke2016
added
? - Needs Triage
Need team to review and classify
bug
Something isn't working
labels
Jul 27, 2022
rapids-bot bot
pushed a commit
that referenced
this issue
Aug 4, 2022
This PR 1. Extends the capabilities of the `PageRank CAPI` to the `python cuGraph API` 2. Update or Add support for the parameters `personalization` `precomputed_vertex_out_weight` and `nstart` for both the SG and MG implementation closes #2455 closes #2430 Authors: - Joseph Nke (https://github.com/jnke2016) - Chuck Hastings (https://github.com/ChuckHastings) Approvers: - Chuck Hastings (https://github.com/ChuckHastings) - Seunghwa Kang (https://github.com/seunghwak) - Rick Ratzel (https://github.com/rlratzel) URL: #2467
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
A recent change to the python
cugraph-API
was introduced when integrating thePLC Graph
. The legacy(cython.cu
)Renumbering
(which sets the parameterstore_transposed
) now occurs at the lazy graph creation and this parameter can no longer be set at the algo's call. PageRank is currently the only algo affected by the change. A solution would be to leveragepylibcugraph
PageRank
which is already implemented or raise an exception if the user doesn't set the parameter at the lazy graph creation.Steps/Code to reproduce bug
Run the MG PageRank tests
The text was updated successfully, but these errors were encountered: