[FEA] Change mutual_reachability_graph to use device_sparsity_owning_coo_matrix
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
We should update the mutual_reachability_graph function to use the device_sparsity_owning_coo_matrix instead of the older COO class that it is using now.
This will require some updates to sparse algorithms in RAFT, such as raft::sparse::linalg::symmetrize and raft::sparse::convert::sorted_coo_to_csr - which only accept the raft::sparse::COO class.
See https://github.com/rapidsai/cuvs/pull/323#discussion_r1783327611
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the mutual_reachability_graph function and inspect the RAFT sparse algorithms raft::sparse::linalg::symmetrize and raft::sparse::convert::sorted_coo_to_csr, which currently accept raft::sparse::COO. Review the linked pull request discussion for context. Done means the function uses device_sparsity_owning_coo_matrix and the affected sparse algorithms support it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100