-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Fix specifying number of levels with log contour #27576
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
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
12ce07f
Fix specifying number of levels with log contour
dstansby d307114
Fix log contours when using default levels
dstansby d6a445e
Update test
dstansby 917bc62
PEP8 fix
dstansby 0eadaf0
Clean up contour level logic
dstansby b4fc4d3
Factor out logic to set default locator
dstansby 47b2ca0
Rename locator setting method
dstansby 8c0775e
Move parameter description
dstansby File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
Maximum levels on log-scaled contour plots are now respected | ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
When plotting contours with a log norm, passing an integer value to the ``levels`` | ||
argument to cap the maximum number of contour levels now works as intended. |
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
This could still be made clearer / the current code is still convoluted (but possibly better as a followup PR to not make too many changes and complicate review)
args
is not the originalargs
but stripped from leading[X, Y], Z
. Effectively it can only be empty or contain a single element that containslevels
passed positionally (which is supported, but a bit cumbersome to write out as a signature because the optional[X, Y]
require to absorb all positional parameters in*args
and we therefore have to reunite a possible positional level from args with the possible kwarg level.The current implementation also has the surprising side effect that you can do
contour(Z, levels1, levels=levels2)
and the positionallevels1
is sliently ignored.The only use of
args
here is to pass on a possible positionallevel
. We can push the logic out of the function and unite the positional and kwarg paths oflevels
in the caller_contour_args
- where it belongs logically.I think eventually we should also make
levels
kw-only.contour(Z, 5)
orcontour(X, Y, Z, [-1, 0, 1])
are not very readable anyway.