-
Notifications
You must be signed in to change notification settings - Fork 65
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
Leiden Clustering implementation #186
Comments
We are unlikely to have time for this for a bit, but we'll take a look at it when we have time. |
Hi @arthurp, |
The clusters are represented as a new property containing integer cluster IDs. Is this not acceptable for your use case? Do you want a new graph for each cluster? We could add a separate operation which partitions a graph based on a property (as created by the clustering algorithms). If that would be helpful, please file a separate issue. It's a good idea I think. Though it may not be applicable to large graphs (millions of nodes) because there could be a huge number of clusters and the operation could consume too much memory to be useful. |
I didn't understand the purpose of --output_CID option earlier. I may be able to work with it. Thank you for mentioning it. |
Shouldn't this be closed considering #544 ? |
Implemented now |
Following from issue #70
I saw that in previous version of Galois ("git clone https://github.com/IntelligentSoftwareSystems/Galois"), there is an implementation of leiden clustering under clustering folder (Galois/lonestar/analytics/cpu/clustering). Why was this removed in the latest version? Can you please add it again?
Last commit with leiden clustering in message.
commit ce78fe5
Author: Udit Agarwal [email protected]
Date: Tue Apr 28 13:55:32 2020 -0500
The text was updated successfully, but these errors were encountered: