-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
hist2d() is now using pcolormesh instead of pcolorfast #4625
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
Conversation
Interesting, this evidently changed the test image slightly. This might be related to #4584; it suggests there are inconsistencies in snapping or rounding among our various Artists. It looks like the problem here is only in the pdf. In this test the grid is regular, so pcolorfast was using AxesImage in the baseline image. |
AxesImage is subtly different from the pcolors in that coordinates are On Sat, Jul 11, 2015 at 1:50 PM, Eric Firing [email protected]
|
Also note that this would be an API change if accepted. On Sat, Jul 11, 2015 at 5:02 PM, Benjamin Root [email protected] wrote:
|
@WeatherGod, Yes, pcolorfast does take into account the way AxesImage works. The travis failure is coming from a very subtle shift in some boundaries in the pdf output. |
@efiring @WeatherGod did you happen to remember if you were leaning towards merging or more discussion at last comment? |
The test image would have to be changed. Once this is rebased and all tests pass, I would favor merging it. It would be nice to fix pcolorfast to work correctly with log scales, but that's a bigger job. |
The reason for it being an API change is the different interfaces for the
different objects returned by pcolorfast(). This is important for things
like animation code. By pinning the output type to be a particular type of
artist, we do make things more consistent overall, but it is still a
different object than what some users had before, and may have coded
against.
…On Tue, Jan 10, 2017 at 5:05 PM, Eric Firing ***@***.***> wrote:
The test image would have to be changed. Once this is rebased and all
tests pass, I would favor merging it. It would be nice to fix pcolorfast to
work correctly with log scales, but that's a bigger job.
I don't see why this would be considered an API change.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4625 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARy-MB7aaxB5xYLDB4XPA97JZt192CZks5rRACwgaJpZM4FWmtC>
.
|
I agree that it would be an API change; not a particularly disruptive one, but by definition, return types are part of the API. |
Pull request in response to issue #4615