-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add kwarg source_range to cumulative_distribution and equalize_hist #4056
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sciunto I've requested a couple of very minor changes. Approved pending those.
Co-Authored-By: Juan Nunez-Iglesias <juan.nunez-iglesias@monash.edu>
Co-Authored-By: Juan Nunez-Iglesias <juan.nunez-iglesias@monash.edu>
Absolutely, it's done. |
skimage/exposure/exposure.py
Outdated
Number of bins used to calculate histogram. This value is ignored for | ||
integer arrays, for which each integer is its own bin. | ||
source_range : string, optional | ||
'image' (default) determines the range from the input image. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'image' (default) determines the range from the input image. | |
'image' (default) determines the range from minimum and maximum value of the input image. |
is this true?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it's true, but not PEP8 compliant. =P
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm advocating to have this option set to 'source' by default. Although 'image' can be useful, it is not the most natural option to me. Especially, once you want to compare histograms, different ranges do not help. But, this is another story.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hmaarrfk Added and modified elsewhere also.
It doesn't seem related to this PR, but the travis failures look pretty serious! =\ |
I think those failures are because a bad version of qt is being pulled in. I really hate QT testing. Just look at how long Vispy has been trying to release their package, they are constantly stuck chasing changes in QT bugs |
Doesn't this need an easy test? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no test has been added for this new functionality.
Description
Xref #4054
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
.@meeseeksdev backport to v0.14.x