matplotlib-users Mailing List for matplotlib

On Mon, Jan 10, 2011 at 10:44 AM, Angus McMorland <am...@gm...> wrote:
> Hi all,
>
> Can anyone tell me why an additional point at the origin is added at
> the end of each PolyCollection path, on line 593 of collections.py?
>
> xy = np.concatenate([xy, np.zeros((1,2))])
>
> It's causing funny effects in my pcolor plots, as in the example
> included. In the 'noproblem' plots I've commented out that line.
>
> Thanks,
>
> Angus
>
The purpose of it is to close out the polygon path, but it is doing it
regardless of whether the path was already closed or not... commenting it
out breaks a lot of other code though (like hist()). It appears that pcolor
will always close out its paths, but other codes will not.
This might actually be related to another problem of mine...
Ben Root

Hi all,
Can anyone tell me why an additional point at the origin is added at
the end of each PolyCollection path, on line 593 of collections.py?
xy = np.concatenate([xy, np.zeros((1,2))])
It's causing funny effects in my pcolor plots, as in the example
included. In the 'noproblem' plots I've commented out that line.
Thanks,
Angus
-- 
AJC McMorland
Post-doctoral research fellow
Neurobiology, University of Pittsburgh

On Sun, Jan 9, 2011 at 13:04, Benjamin Root <ben...@ou...> wrote:
> You have run into a peculiar numpy bug that I have reported several months
> ago. Essentially, np.loadtxt() does a squeeze() on the data right before
> returning it. Therefore, if there is only one line, the array returned is a
> 1-d array rather than your expected 2d array.
>
> You can mitigate this by using np.atleast_2d() on the returned array. This
> will guarantee that your 'morning' array will always be 2d.
>
> I hope that helps!
It does! Thanks!
Cheers
Adam