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

Support Negative Sampling in pylibcugraph and cuGraph-PyG #4660

Merged
merged 39 commits into from
Sep 30, 2024

Conversation

alexbarghi-nv
Copy link
Member

@alexbarghi-nv alexbarghi-nv commented Sep 20, 2024

Adds support for negative sampling in pylibcugraph and cugraph-pyg.

Closes rapidsai/cugraph-gnn#39
Merge after #4641

@alexbarghi-nv alexbarghi-nv self-assigned this Sep 20, 2024
@alexbarghi-nv alexbarghi-nv added this to the 24.10 milestone Sep 24, 2024
@alexbarghi-nv alexbarghi-nv marked this pull request as ready for review September 24, 2024 23:50
@alexbarghi-nv alexbarghi-nv requested review from a team as code owners September 24, 2024 23:50
@alexbarghi-nv alexbarghi-nv requested a review from a team as a code owner September 24, 2024 23:50
Copy link
Collaborator

@ChuckHastings ChuckHastings left a comment

Choose a reason for hiding this comment

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

Approving C API updates.

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.

I'm not familiar with this code and the PR is quite large, but I didn't see anything that jumped out as a problem. I did have one question/suggestion though which need not hold up approval.

Comment on lines +47 to +49
# Ensures that a CUDA context is not created on import of rapids.
# Allows pytorch to create the context instead
os.environ["RAPIDS_NO_INITIALIZE"] = "1"
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 assuming you tested this but I'm surprised this works since it comes after various cugraph imports above. Would it be safer to move up, in case something in cugraph is refactored to pull in a module that creates a CUDA context?

Copy link
Member Author

@alexbarghi-nv alexbarghi-nv Sep 27, 2024

Choose a reason for hiding this comment

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

You're right, this got pulled in from a similar file and ended up in the wrong place. I'll change it.

@alexbarghi-nv
Copy link
Member Author

I'm not familiar with this code and the PR is quite large, but I didn't see anything that jumped out as a problem. I did have one question/suggestion though which need not hold up approval.

This PR includes the other PRs (in-memory sampling, link prediction) which is why there are a lot of changes. But if you've reviewed everything we could merge this in place of the other ones.

@alexbarghi-nv
Copy link
Member Author

/merge

@rapids-bot rapids-bot bot merged commit 4dfd3b3 into rapidsai:branch-24.10 Sep 30, 2024
130 of 131 checks passed
@alexbarghi-nv alexbarghi-nv deleted the pyg-neg-sampling branch September 30, 2024 15:56
alexbarghi-nv added a commit to rapidsai/cugraph-gnn that referenced this pull request Sep 30, 2024
Buffered in-memory sampling in cuGraph-PyG, link prediction in cuGraph-PyG, and negative sampling in cuGraph-PyG (rapidsai/cugraph#4660)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CMake cuGraph feature request New feature or request non-breaking Non-breaking change python
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[FEA] Support Negative Sampling in cuGraph-PyG
3 participants