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

Investigate Migrating cugraph.gnn Subpackage #4407

Open
Tracked by #3806
alexbarghi-nv opened this issue May 9, 2024 · 1 comment
Open
Tracked by #3806

Investigate Migrating cugraph.gnn Subpackage #4407

alexbarghi-nv opened this issue May 9, 2024 · 1 comment
Assignees
Labels
improvement Improvement / enhancement to an existing function
Milestone

Comments

@alexbarghi-nv
Copy link
Member

cuGraph-PyG and cuGraph-DGL are being decoupled from cuGraph to rely on pylibcugraph instead, but we still have a cugraph.gnn subpackage within cugraph that both libraries need. We should find a better long-term home for that subpackage, especially since we are thinking of changing the release cycle of cuGraph-PyG and cuGraph-DGL and those packages are very tightly coupled with cugraph.gnn.

@alexbarghi-nv alexbarghi-nv self-assigned this May 9, 2024
@alexbarghi-nv alexbarghi-nv added the improvement Improvement / enhancement to an existing function label May 9, 2024
@alexbarghi-nv alexbarghi-nv added this to the 24.08 milestone May 9, 2024
@alexbarghi-nv
Copy link
Member Author

This is complicated by the distributed sampler's reliance on cuDF - maybe there could be an alternative where pytorch tensors are written instead so that cuDF could be an optional dependency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement Improvement / enhancement to an existing function
Projects
None yet
Development

No branches or pull requests

1 participant