Conversation
We do not recompute probabilities when the frame and the ROI do not change. It saves a lot of time when adjusting the probability threshold, because ilastik takes a lot of time to launch everytime. Here we used the same strategy that for the Weka detector: we simply store the last probability map and check whether we need to recompute it next time the user presses the 'Preview' button. Nowe I have to check that it also works for 3D.
Amazingly enough, it is sufficient to simply add the smoothing parameter to the settings maps for it to work. Indeed, the smoothing is handled by the threshold detector, that for ilastik, operates on the probability map generated by the ilastik command. So there is only very little to do to make it work here. Unexpected but pleasant.
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.
No description provided.