Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

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

Closed
jankoeh wants to merge 1 commit into matplotlib:master from jankoeh:master

Conversation

Copy link

@jankoeh jankoeh commented Jul 11, 2015

Pull request in response to issue #4615

@tacaswell tacaswell added this to the proposed next point release milestone Jul 11, 2015
Copy link
Member

efiring commented Jul 11, 2015

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.

Copy link
Member

AxesImage is subtly different from the pcolors in that coordinates are
pixel centers versus pixel corners. Does pcolorfast take that into account?

On Sat, Jul 11, 2015 at 1:50 PM, Eric Firing notifications@github.com
wrote:

Interesting, this evidently changed the test image slightly. This might be
related to #4584 #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.


Reply to this email directly or view it on GitHub
#4625 (comment)
.

Copy link
Member

Also note that this would be an API change if accepted.

On Sat, Jul 11, 2015 at 5:02 PM, Benjamin Root ben.root@ou.edu wrote:

AxesImage is subtly different from the pcolors in that coordinates are
pixel centers versus pixel corners. Does pcolorfast take that into account?

On Sat, Jul 11, 2015 at 1:50 PM, Eric Firing notifications@github.com
wrote:

Interesting, this evidently changed the test image slightly. This might
be related to #4584
#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.


Reply to this email directly or view it on GitHub
#4625 (comment)
.

Copy link
Member

efiring commented Jul 11, 2015

@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.

Copy link
Contributor

@efiring @WeatherGod did you happen to remember if you were leaning towards merging or more discussion at last comment?

Copy link
Member

efiring commented Jan 10, 2017

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.

Copy link
Member

WeatherGod commented Jan 10, 2017 via email

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> .

Copy link
Contributor

I agree that it would be an API change; not a particularly disruptive one, but by definition, return types are part of the API.

@tacaswell tacaswell modified the milestones: 2.1 (next point release), 2.2 (next next feature release) Sep 24, 2017
Copy link
Member

jklymak commented Dec 12, 2017

Closing in lieu of #9987. Umm, this is slightly rude, as @jankoeh no longer gets credit for the PR. Happy to close my new one and have them either re-opne and get this one up to snuff, or have them open a new one. In either case, @jankoeh thanks a lot for this!

@QuLogic QuLogic modified the milestones: needs sorting, v2.2.0, v3.0 Feb 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Projects
None yet
Milestone
v3.0.0
Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /