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

Fix bad Leiden result #4376

Merged

Conversation

ChuckHastings
Copy link
Collaborator

Once the termination criteria is met, the last level of the dendrogram contains a partitioning that reduces the overall modularity. This update overwrites the final dendrogram level with a k to k mapping.

This bug had a consequence of the numbering of the flattened Leiden partitions being non-consecutive integers. This should now be resolved.

Closes #4368

Once the termination criteria is met, the last level of
the dendrogram contains a partitioning that reduces the
overall modularity.  This update overwrites the final dendrogram
level with a k to k mapping.
@ChuckHastings ChuckHastings changed the title Bad Leiden result Fix bad Leiden result Apr 26, 2024
@ChuckHastings ChuckHastings self-assigned this Apr 26, 2024
@ChuckHastings ChuckHastings added bug Something isn't working non-breaking Non-breaking change labels Apr 26, 2024
@ChuckHastings ChuckHastings marked this pull request as ready for review April 26, 2024 18:21
@ChuckHastings ChuckHastings requested a review from a team as a code owner April 26, 2024 18:21
@ChuckHastings
Copy link
Collaborator Author

/merge

@rapids-bot rapids-bot bot merged commit 290b443 into rapidsai:branch-24.06 Apr 29, 2024
131 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cuGraph non-breaking Non-breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG]: Incorrect numbering of partitions in Leiden clustering
2 participants