[QST] Is multi_source_bfs implemented in nightly (22.02) version or in stable (21.12) version?

[rewaza]

I was looking for an efficient way to get all pairs short paths from graphs. According to this post multi_source_bfs function should work but I'm receiving an error: line 249, in multi_source_bfs raise NotImplementedError(NotImplementedError: concurrent_bfs is coming soon! Please up vote the github issue 1465 to help us prioritize) Is this feature implemented in nightly (22.02) version or in stable (21.12) version?

Here's an example of my code:

import cugraph import cudf import pandas as pd from datetime import datetime s_time = datetime.now() dfs = pd.read_csv("/xxx/small.csv") data = {'source': [1,1,3,2], ... 'target': [7,5,7,6]} rcdf = pd.DataFrame(data) cuda_g = cudf.DataFrame.from_pandas(dfs) cuda_nc = cudf.DataFrame.from_pandas(rcdf) G = cugraph.Graph() G.from_cudf_edgelist(cuda_g, source='source', destination='target', edge_attr='cost') sources = set(rcdf.iloc[:, 1]) def msources(s): ... gr = cugraph.multi_source_bfs(G, s) ... print(gr[0]) msources({1,2}) Traceback (most recent call last): File "", line 1, in File "", line 2, in msources File "/xxx/anaconda3/envs/rapids-22.02/lib/python3.8/site-packages/cugraph/traversal/ms_bfs.py", line 249, in multi_source_bfs raise NotImplementedError( NotImplementedError: concurrent_bfs is coming soon! Please up vote the github issue 1465 to help us prioritize

Thank you!

[BradReesWork]

Currently there is no easy way to get all pair shortest path. We are planning on implementing a version of that and are hoping that we can squeeze it into this years roadmap. The multi-seed bfs/sssp code assume one seed per component. If you have a small graph, you can replicate the data into a number of disjoint components and then do one seed per component and rebuild the all-paths answer

[github-actions[bot]]

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.

[ChuckHastings]

Based on latest road map discussion this will not be addressed until later in 2023.