You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Wrong datalims with empty plots with shared axes #3118
Now ax1.get_xlim() returns erroneous (-0.06, 0.06) because when bounding boxes of two plots are united, infinitely small bounding box of ax2 (Bbox('array([[ inf, inf],\n [-inf, -inf]])')) is considered infinitely large in transforms.BboxBase.union(). E. g. transforms.BboxBase.union([ax1.dataLim, ax2.dataLim]) returns Bbox('array([[-inf, -inf],\n [ inf, inf]])') which is incorrect.
This bug prevents correct display of two plots with shared axis while one of them has empty data.
Good question; I don't know. But with this and with #2492, I can reproduce the problem with Anaconda, mpl 1.3.1, and not with mpl master on my Linux VM. There were a couple relevant-looking changes to transforms.py a year ago, but I don't think they actually affected this. I don't have time to track it down now, unfortunately.
Good question; I don't know. But with this and with #2492 #2492, I can reproduce
the problem with Anaconda, mpl 1.3.1, and not with mpl master on my Linux
VM. There were a couple relevant-looking changes to transforms.py a year
ago, but I don't think they actually affected this. I don't have time to
track it down now, unfortunately.
—
Reply to this email directly or view it on GitHub #3118 (comment)
.
No, on two counts: first, because the examples here don't use collections; and second, because the change to add_collections defaults to causing datalims to be calculated, but does not require it.
Activity
efiring commentedon Jun 5, 2014
This is present in 1.3.1, but fixed in master; 1.4 release is coming soon.
tacaswell commentedon Jun 6, 2014
When did this get fixed? This is a duplicate of another issue that I punted to 1.4.x a few days ago (#2492).
efiring commentedon Jun 6, 2014
Good question; I don't know. But with this and with #2492, I can reproduce the problem with Anaconda, mpl 1.3.1, and not with mpl master on my Linux VM. There were a couple relevant-looking changes to transforms.py a year ago, but I don't think they actually affected this. I don't have time to track it down now, unfortunately.
WeatherGod commentedon Jun 6, 2014
Might it possibly be related to changes made recently to add_collections()?
IIRC, that caused datalims to always be calculated (for better or worse).
On Fri, Jun 6, 2014 at 1:42 PM, Eric Firing notifications@github.com
wrote:
efiring commentedon Jun 6, 2014
No, on two counts: first, because the examples here don't use collections; and second, because the change to add_collections defaults to causing datalims to be calculated, but does not require it.
efiring commentedon Jun 6, 2014
26ed35b
Looks like that is the fix.
Is there an easy way to find the PR to which a commit like this corresponds?
tacaswell commentedon Jun 6, 2014
#2357 (found the commit in gitk and the child commit had that is the mesage).