Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add warning in python cugraph when auto-transpose will happen #2742

Closed
rlratzel opened this issue Sep 27, 2022 · 0 comments · Fixed by #2756
Closed

Add warning in python cugraph when auto-transpose will happen #2742

rlratzel opened this issue Sep 27, 2022 · 0 comments · Fixed by #2756
Assignees
@jnke2016
Milestone
22.10

Comments

@rlratzel
Copy link
Contributor

rlratzel commented Sep 27, 2022 •
edited
Loading

Add warning in python cugraph when auto-transpose will happen

Algos that require transposed, and will auto-transpose:

  • pagerank
  • katz
  • hits
  • eigenvector_centrality

What about the other algos that require non-transposed? Will they handle and auto-un-transpose a transposed graph?
@rlratzel rlratzel added this to the 22.10 milestone Sep 27, 2022
@jnke2016 jnke2016 mentioned this issue Sep 29, 2022
Merged
@rapids-bot rapids-bot bot closed this as completed in #2756 Oct 3, 2022
rapids-bot bot pushed a commit that referenced this issue Oct 3, 2022
@jnke2016
Raise a warning for certain algorithms (#2756)
2b8395a 
Certain algorithms (Katz, HITS, PageRank, Eigenvector centrality) require the flag `store_transposed` to be set to `True` for optimal performance. Although the CAPI internally `transposed` the graph at the algo's call if it wasn't at the graph creation, this adds extra overheads. This PR raises an exception if the user doesn't set the flag to `True` at the graph creation

closes #2742

Authors:
  - Joseph Nke (https://github.com/jnke2016)

Approvers:
  - Alex Barghi (https://github.com/alexbarghi-nv)
  - Rick Ratzel (https://github.com/rlratzel)

URL: #2756
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jnke2016 jnke2016

Labels
None yet
Projects
None yet
Milestone
22.10
Development

Successfully merging a pull request may close this issue.

Raise a warning for certain algorithms jnke2016/cugraph
2 participants
@rlratzel @jnke2016