Repository navigation
Fix computation of histogram bins for multichannel integer-valued images - #6413
Merged
Merged
Conversation
Contributor
Author
|
@meeseeksdev backport to v0.19.x |
meeseeksmachine
pushed a commit
to meeseeksmachine/scikit-image
that referenced
this pull request
Jun 11, 2022
…tichannel integer-valued images
jni
approved these changes
Jun 11, 2022
jni
pushed a commit
that referenced
this pull request
Jun 11, 2022
…s for multichannel integer-valued images) (#6414) Co-authored-by: Gregory Lee <grlee77@gmail.com>
grlee77
added a commit
to grlee77/cucim
that referenced
this pull request
Jun 13, 2022
This is a port of the following fix included in skimage 0.19.3: scikit-image/scikit-image#6413
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
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.
Description
closes #6412
When calling
np.bincount, we need to make sure the minimum bin is always zero, otherwise there can be a size mismatch across channels as encountered in #6412. A small test case for this was added to verify the fix.Checklist
./doc/examples(new features only)./benchmarks, if your changes aren't covered by anexisting benchmark
For reviewers
later.
__init__.py.doc/release/release_dev.rst.example, to backport to v0.19.x after merging, add the following in a PR
comment:
@meeseeksdev backport to v0.19.xrun-benchmarklabel. To rerun, the labelcan be removed and then added again. The benchmark output can be checked in
the "Actions" tab.