Fixed EndNTM silently using weights to score solutions internally eve… - #264
Merged
Conversation
…n though it is an unweighted algorithm
Owner
|
Thanks for the fix, I missed the check on the default param. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
EndNTM is an unweighted algorithm but it was scoring solutions using weights due to a library default parameter. This was not even coherent because it was mixing weighted modularity with unweighted coverage.
The problem is that com.modularity defaults to weight="weight"
Release text
Fixed EndNTM silently partially using weights