Enable getting segmentations at any threshold #46
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
Until now, the RAG would output the *currently implied segmentation* when using the `get_segmentation` method. However, since we are storing the entire merge tree, it is efficient to get segmentations at any threshold. This commit enables that by passing a threshold to `self.tree.get_map`.
jni
added a commit
that referenced
this pull request
Apr 10, 2015
Enable getting segmentations at any threshold
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.
Until now, the RAG would output the currently implied segmentation
when using the
get_segmentationmethod. However, since we are storingthe entire merge tree, it is efficient to get segmentations at any
threshold. This commit enables that by passing a threshold to
self.tree.get_map.See question (5) in this thread on the mailing list for motivation.