[BUG] Fix bug with 0s in sparse matrix for LCC calculation #805
Conversation
This file contains 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
|
❌ Deploy Preview for graspologic failed. 🔨 Explore the source changes: f5e0807 🔍 Inspect the deploy log: https://app.netlify.com/sites/graspologic/deploys/60dde88bfcd3e700072a7891 |
|
@daxpryce you mentioned you were fine with this PR, mind approving? |
daxpryce
approved these changes
Jul 1, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this implement/fix? Briefly explain your changes.
Fixes a bug where explicit 0s stored in a scipy sparse matrix were treated as edges for the purposes of the largest connected component calculation. This was potentially causing inconsistent behavior depending on whether the array was represented as sparse or dense.