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.

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

Enable PLC algos to leverage the PLC graph #2682

Merged

Conversation

jnke2016
Copy link
Contributor

@jnke2016 jnke2016 commented Sep 11, 2022

This PR enables the PLC algos to leverage the PLC graph created prior to running the algos. This will enable the exclusion of the graph creation time from the algo's run time for more accurate benchmarks. This PR also updates the tests accordingly (by skipping the cython.cu renumbering) along with the docstrings.

closes #2375
closes #2374

@jnke2016 jnke2016 requested a review from a team as a code owner September 11, 2022 01:01
@codecov-commenter
Copy link

codecov-commenter commented Sep 11, 2022

Codecov Report

❗ No coverage uploaded for pull request base (branch-22.10@a291cfe). Click here to learn what that means.
Patch has no changes to coverable lines.

❗ Current head abf8229 differs from pull request most recent head 2eec7a8. Consider uploading reports for the commit 2eec7a8 to get more accurate results

Additional details and impacted files
@@               Coverage Diff               @@
##             branch-22.10    #2682   +/-   ##
===============================================
  Coverage                ?   60.04%           
===============================================
  Files                   ?      111           
  Lines                   ?     6184           
  Branches                ?        0           
===============================================
  Hits                    ?     3713           
  Misses                  ?     2471           
  Partials                ?        0           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@alexbarghi-nv alexbarghi-nv added improvement Improvement / enhancement to an existing function breaking Breaking change labels Sep 21, 2022
@alexbarghi-nv alexbarghi-nv added this to the 22.10 milestone Sep 21, 2022
Copy link
Contributor

@rlratzel rlratzel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great, I'm looking forward to these changes. I have a few comments and questions for now.



def eigenvector_centrality(
G, max_iter=100, tol=1.0e-6, normalized=True
G, max_iter=100, tol=1.0e-6
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing the normalized arg would technically be a breaking change, even though it appears to never have been used. We should have a discussion if these should be removed (at which point the docstring probably shouldn't mention normalized either), or if we need to maintain them for keeping a backwards-compatible signature.

@@ -92,7 +90,7 @@ def katz_centrality(
nstart['values'] : cudf.Series
Contains the katz centrality values of vertices

normalized : bool, optional, default=True
normalized : not supported
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same for this one, although this appears to still be present as an optional arg to this function.

Edit: looks like there's a few others like this too.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right. I still don't get why they were added in the first place since they were never supported.

@@ -151,7 +151,7 @@ def test_core_number_invalid_input(input_expected_output):
dg = cugraph.Graph(directed=True)
dg.from_dask_cudf_edgelist(
ddf, source='src', destination='dst',
edge_attr="value", renumber=True)
edge_attr="value", renumber=True, legacy_renum_only=True)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm a little worried about this change. What's the UX if legacy_renum_only=True is not specified? If not specifying this results in an error, then we'll need to figure out how to communicate that the user needs to specify this.

@jnke2016
Copy link
Contributor Author

rerun tests

@rlratzel
Copy link
Contributor

@gpucibot merge

@rapids-bot rapids-bot bot merged commit 7af4229 into rapidsai:branch-22.10 Sep 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking Breaking change improvement Improvement / enhancement to an existing function
Projects
None yet
4 participants