| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
If the user explicitly passes a levels array (the default is auto-determined), let's assume that they know what they are doing.
|
Is this comment from @ianthomas23 dealt with? "We should probably add a check for no levels specified by the user for a contour call, as already happens for contourf." |
Sorry, something went wrong.
|
I'm not sure what this really means, but if it's adding a check for levels=[], I'd say that's again something explicitly asked by the user and we should not warn (just like we don't warn for plot([], [])). |
Sorry, something went wrong.
|
My comment meant that if there is an explicit check for user-specified levels for a contourf call, there should be a similar check for a contour call so that the checks are consistent. But as you are removing the contourf check then that makes them consistent too, as neither checks. |
Sorry, something went wrong.
There was a problem hiding this comment.
I see the point of:
(I could consider keeping the warning for now in the case where the user didn't pass levels but z is uniform throughout, as that's more likely to be a "data-exploration" case.)
but do not have strong opinions enough to claim that it should be there. Seems like a quite safe option though.
Sorry, something went wrong.
|
Let's see what others think here. |
Sorry, something went wrong.
There was a problem hiding this comment.
I'm in favor of removing this warning and if we get reports of "all constant and no lines" we can consider putting the warning back in the fully automatic case (and it would make sense to check on the "all constant" case explicitly).
Sorry, something went wrong.
|
Sounds good; this is good to go, then? |
Sorry, something went wrong.
|
Let's get this in for 3.7. |
Sorry, something went wrong.
…912-on-v3.7.x Backport PR #24912 on branch v3.7.x (Remove contour warning for "no-valid-levels".)
| Back | FazBrowse Home | New Git URL |
If the user explicitly passes a levels array (the default is auto-determined), let's assume that they know what they are doing. Closes #23778.
(I could consider keeping the warning for now in the case where the user didn't pass levels but z is uniform throughout, as that's more likely to be a "data-exploration" case.)
PR Summary
PR Checklist
Documentation and Tests
Release Notes