Hello,
in version 0.98.5.2 the polar plot still has a problem with negativ angles.
The polarplot is drawing a circle when the angle changes from negativ to
positiv (e.g. from -0.01 to +0.01).
But in What new in 0.98.4
(http://matplotlib.sourceforge.net/users/whats_new.html) I can read:
Fix
João,
Thank you for commenting on the code. sys.argv check is a wise one. Since I
was the only user of this little snippet I didn't give attention of this
detail, however eventually some other people will start using the code too.
I thought it is more efficient to only import functions that I
On Sun, May 17, 2009 at 2:17 PM, Gökhan SEVER gokhanse...@gmail.com wrote:
Hello Roy,
ipython splot.py 09_03_23_11_44_54.stats.tas
works, but I can't make it work with pylab switch. It executes my script,
however whos list an empty namespace :(
Gökhan,
The whos command works for me.
Also,
Hmm,
Is it working on your side from a bash shell as ipython --pylab script
argument
I couldn't make it work in this fashion. As I said whos list nothing :(
I am on Fedora 10 x86, Python 2.5.2, IPython 0.10.bzr.r1173
Without the pylab switch I see the interactive space with variables. I also
On 5/17/2009 2:44 PM Jae-Joon Lee apparently wrote:
I meant consistency with Matplotlib itself.
My point is that that is not well defined,
since most of the OO API in Matplotlib is
Python centric, but the subplot definition
is an exception.
So I am suggesting that any new functions
certainly
Hi mpl-users,
I have a web application in which I produce png files using
matplotlib. Unfortunately the files are quite big (up to ~300 kb). I
have however tried using the Linux tool pngnq to reduce the file size
with a factor ~3-4 with almost no degradation of the result. I
therefore wondered
Hi all,
I had a few off-list conversation with Alan, and I'm also quite agree
with him for this issue.
Just to rephrase, I think the current subplot interface has (at least)
two issues.
issue 1) the indexing convention is not that of python. The index
starts from 1, instead of 0. (eg 111)
I think the point here is that
img = Image('foo.png')
imshow(img)
and
img = Image('foo.png')
imshow(asarray(img))
give different results, since matplotlib.image.pil_to_array functions
differently from what PIL exposes in __array_interface__
--
Pauli
On Sun, May 17, 2009 at 5:03 PM, Alan G Isaac alan.is...@gmail.com wrote:
So I am suggesting that any new functions
certainly should not propagate this anomaly.
Understood. And, yes, I guess you're quite right in this regard.
And I'll try to deprecate the current matlab-like interface in future
