Improve centroid calculation performance#288
Open
sophiamaedler wants to merge 16 commits intomainfrom
Open
Conversation
makes the code more robust and consistent
…points are never removed this prevents the points object from being removed from memory in the original sdata object
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
1 participant
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.
one larger datasets the memory requirements for computing the centroids with the numba accelerated functions increase dramatically if the cell_ids do not start at 1 and increase sequentially.
This addresses this issue to try and allow for the using of the numba acceralted functions over a larger subset of datasets before needing to revert to the dark-backed function get_centroids() that is much slower.
fixes #289