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

[EPIC] NetworkX Compat #1922

Closed
1 of 35 tasks
BradReesWork opened this issue Nov 2, 2021 · 3 comments
Closed
1 of 35 tasks

[EPIC] NetworkX Compat #1922

BradReesWork opened this issue Nov 2, 2021 · 3 comments
Labels
Epic Tracker for a relatively large body of work that is broken down into stories and issues

Comments

@BradReesWork
Copy link
Member

BradReesWork commented Nov 2, 2021

22.04

  • one (or more) e2e workflows for Pagerank and/or BFS identified that currently run to completion with NetworkX. Even better if these are popular examples known by the community.
  • swap out import networkx as nx with from cugraph.experimental import nx and the workflows still run and produce the same results.

22.06

  • initial algos (PageRank and BFS) and performance comparison (use to drive where to optimize)

22.08

  • initial release (PageRank, BSF, SSSP, Louvain, WCC, SCC, BC, Jaccard) and performance tuned

22.10

  • refactor (cleanup) cuGraph code to remove Nx (this is the "consolidate all Nx compatibility into one place" goal below, meaning that all the code that accepts a NetworkX graph object needs to go into this new nx compatibility module)

**Goals**
  • Be a drop-in replacement for NetworkX
  • from cugraph.experimental import nx
  • Be faster than native NetworkX
  • Consolidate all Nx compatibility into one place

Likely areas where we will not be drop-in replacement (but we should discuss this further to gauge the impact and see if there still may be an option to support):

  • Likely this: Allow any hashable to be an attribute. You cannot create “MyData” and then assign it as an attribute

Checkboxes / functions

  • add_node
  • add_node_from
  • remove_node
  • remove_node_from
  • nodes
  • number_of_nodes
  • order
  • has_node
  • add_edge
  • add_edge_from
  • add_weighted_edges_from
  • remove_edge
  • removed_edge_from
  • update
  • has_edge
  • neighbors
  • edges
  • get_edge_data
  • adjacency
  • degree
  • clear
  • clear_edges

IO

  • read_edgelist
  • read_weighted_edgelist
  • read_adjlist

Graph Types

  • Graph
  • DiGraph

We need to wait on cuGraph before adding MultiGraph and Bipartite Graph

@BradReesWork BradReesWork added the Epic Tracker for a relatively large body of work that is broken down into stories and issues label Nov 2, 2021
@BradReesWork BradReesWork added this to Longterm & EPICs in 22.02 Release Nov 2, 2021
@rapidsai rapidsai deleted a comment from github-actions bot Jan 26, 2022
@BradReesWork
Copy link
Member Author

@acostadon can you add some goals to the description?

@BradReesWork BradReesWork removed this from Longterm & EPICs in 22.02 Release Jan 26, 2022
@BradReesWork BradReesWork added this to Longterm & EPICs in 22.04 Release Jan 26, 2022
@BradReesWork BradReesWork removed this from Longterm & EPICs in 22.04 Release Mar 22, 2022
@BradReesWork BradReesWork added this to the 22.06 milestone Mar 22, 2022
@BradReesWork BradReesWork added this to Longterm & EPICs in 22.06 Release Mar 22, 2022
@BradReesWork BradReesWork added this to 22.06 in Graph Roadmap Mar 22, 2022
@BradReesWork BradReesWork added the P2 label Apr 7, 2022
@BradReesWork BradReesWork removed this from the 22.06 milestone May 5, 2022
@BradReesWork BradReesWork removed this from Longterm & EPICs in 22.06 Release May 5, 2022
@BradReesWork BradReesWork removed this from 22.06 in Graph Roadmap May 5, 2022
@github-actions
Copy link

github-actions bot commented Jun 4, 2022

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

@BradReesWork
Copy link
Member Author

closing issue/epic. this will be replaced by work with Nx

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Epic Tracker for a relatively large body of work that is broken down into stories and issues
Projects
None yet
Development

No branches or pull requests

2 participants