cugraph
cugraph copied to clipboard
rapidsai
[FEA] Label propagation graph primitive patterns
The current implementation of graph primitives doesn't cover that. Label propagation is a recurring pattern for analytics going from Louvain to MST.
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.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Hi
I'm curious about this ability. I was looking for something similar to networkx's networkx.algorithms.node_classification.hmn.harmonic_function for propagating labels. It doesnt look like RAPIDS currently has anything like this out of the box, and as of now i'm unclear if there is anything which can easily be used to build a user defined process (message passing, map reduce, sparse matrix) directly on top of existing functionality. The closest may be to attempt a user defined function with cuDF.
Any pointers to suitable entry points (or some existing feature i've overlooked) to creating something like this without the need to write a lower level cugraph implementation.
Thanks
This issue has been labeled inactive-90d due to no recent activity in the past 90 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 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.
