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

[IMP] cuGraph-PyG Should Use torch_geometric.EdgeIndex #4051

Closed
Tracked by #3806 ...
alexbarghi-nv opened this issue Dec 6, 2023 · 0 comments · Fixed by #4384
Closed
Tracked by #3806 ...

[IMP] cuGraph-PyG Should Use torch_geometric.EdgeIndex #4051

alexbarghi-nv opened this issue Dec 6, 2023 · 0 comments · Fixed by #4384
Assignees
Labels
breaking Breaking change improvement Improvement / enhancement to an existing function
Milestone

Comments

@alexbarghi-nv
Copy link
Member

torch_geometric.EdgeIndex natively supports caching CSR/CSC formats and is a better maintained alternative to torch_sparse. We should migrate to this new class for the outputs of cuGraph-PyG sampling.

https://pytorch-geometric.readthedocs.io/en/latest/generated/torch_geometric.edge_index.EdgeIndex.html#torch_geometric.edge_index.EdgeIndex

@alexbarghi-nv alexbarghi-nv added improvement Improvement / enhancement to an existing function breaking Breaking change labels Dec 6, 2023
@alexbarghi-nv alexbarghi-nv added this to the 24.04 milestone Dec 6, 2023
@alexbarghi-nv alexbarghi-nv self-assigned this Dec 6, 2023
@alexbarghi-nv alexbarghi-nv modified the milestones: 24.04, 24.06 Feb 28, 2024
This was referenced Apr 16, 2024
@rapids-bot rapids-bot bot closed this as completed in 797a036 May 30, 2024
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
Development

Successfully merging a pull request may close this issue.

1 participant