You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While CSC order is technically correct, it does not match the order of the ogb datasets, which specify CSR order. This has caused numerous issues with the examples based on OGB datasets, which are also the templates for most user datasets. To avoid user confusion, the default order should be reverted to CSR.
The text was updated successfully, but these errors were encountered:
…se edges in cuGraph-PyG (#3980)
OGB and many other datasets express the edge index in CSR order, but in release 23.10, the default order was changed to CSC, which broke downstream workflows. This PR restores the original default, which should be acceptable for the most common datasets, and familiar to most PyG users.
Closes#3969
Authors:
- Alex Barghi (https://github.com/alexbarghi-nv)
Approvers:
- Tingyu Wang (https://github.com/tingyu66)
- Rick Ratzel (https://github.com/rlratzel)
URL: #3980
While CSC order is technically correct, it does not match the order of the ogb datasets, which specify CSR order. This has caused numerous issues with the examples based on OGB datasets, which are also the templates for most user datasets. To avoid user confusion, the default order should be reverted to CSR.
The text was updated successfully, but these errors were encountered: