matplotlib-devel Mailing List for matplotlib

Gael Varoquaux wrote:
> Hi,
>
> 	Trying out version 0.87.4 I noticed that the example given on
> pages 
> http://matplotlib.sourceforge.net/screenshots/plotmap.py
> and
> http://scipy.org/Cookbook/Matplotlib/Maps
> fail with :
>
> In [1]: from matplotlib.toolkits.basemap import Basemap
> ---------------------------------------------------------------------------
> exceptions.ImportError Traceback (most
> recent call last)
>
> /home/varoquau/<ipython console>
>
> ImportError: No module named toolkits.basemap
>
> I had a quick look and couldn't find where basemap had gone. How
> should these pages be modified ?
>
> 
Gabriel: Basemap is a separate toolkit - it's not included in 
matplotlib. You can get it from the matplotlib sf project page.
-Jeff
-- 
Jeffrey S. Whitaker Phone : (303)497-6313
Meteorologist FAX : (303)497-6449
NOAA/OAR/PSD R/PSD1 Email : Jef...@no...
325 Broadway Office : Skaggs Research Cntr 1D-124
Boulder, CO, USA 80303-3328 Web : http://tinyurl.com/5telg

I would like to ask about the behavior of colorbar(). In my opinion, the 
default colorbar is too big. I know the default is similar to matlab's 
colorbar, but I dont think it should stretch beyond the axes. Also, there is 
arguably too much space between the colorbar and the right edge of the 
figure. I'm attaching two pngs, one is the default behavior and the other is 
my suggested alternative, which I did with colorbar(fraction=0.0305). I don't 
understand what fraction is scaled to. I expected fraction=1 to make the 
height equal to the original axes height, but that actually crashes python:
terminate called after throwing an instance of 'std::bad_alloc'
 what(): St9bad_alloc
Aborted
I don't want to seem too critical of the work that has already been put into 
the colorbar. I just think it needs a bit of polish. Comments?
Darren

Hi Stephen,
Yep, ipython is not bad, but it is not really a replacement for a real
IDE. IPython also seems to act a little wanky with graphs to me. For
instance my plots seem to get drawn interactively (read: very
SLOOOOOWLY) when I use the special -pylab mode. Maybe I'm not
configuring ipython properly, but part of my point is that end users
shouldn't have to think about it, and shouldn't need some special
-pylab mode. It should just work. And I think it would if the
displayer's guts were in a completely separate process, acting as a
graph display server.
The only complication I can see is for callbacks from mouse and
keyboard events that occur on the graphs (but does matplotlib even
support that yet?-- I only saw it mentioned on the web page). Those
events would still need to find their way into callbacks in the
original process. But that's doable too, I think. Just use a
separate thread for communication with the graph display server. And
would perhaps be even less painful than dealing with the wx event
loop.
Anyway, it's more of a 'food for thought' suggestion than anything
else. It's not like I'm going to have time to implement it (though it
seems like it would be a fun project if I did have the time).
I am curious as to what the current thinking is about tacking such
event loop issues, though. Surely folks don't think that "use
ipython" is the be-all-and-end-all ultimate solution.
--bb
On 7/26/06, Stephen Walton <ste...@cs...> wrote:
> Bill Baxter wrote:
> > I think all these problems could be fixed if the display interface
> > were turned into a separate process
> Have you tried ipython?
>
> http://ipython.scipy.org/

Hi,
I've just moved from MATLAB to matplotlib, and I'm really impressed
with the quality of the PS figures it generates with usetex and the
xpdf distiller. I've hit a couple of problems though, one I've manged
to solve (patch against 0.87.4 attached) and the other I'd be greatful
if you could help me with please.
I've been using imshow to basically put a set of axes round an image
produced my simulation code. Here's a minimal version of my script:
----------------------------------------------
from pylab import *
rc('text', usetex=True)
rc('ps', usedistiller="xpdf")
figure(1,figsize=(6, 4))
im=imread('image.png') # a 301x318 image
imshow(im,interpolation='nearest',extent=[0.98, 20, 0.01, 0.5])
axis('normal');
savefig('image.eps')
--------------------------------------------
The first problem I noticed is that the distilling process was causing
some of my images to have (lossy) compression applied and others not.
It turns out that it is a feature of ps2pdf that it tries to detect
the content of the image and apply appropriate compression. You can
over ride this distiller options. My patch adds a new rc option
ps.image_compression that can be set to auto (preserves the current
behaviour), DCTEncode (applies lossy JPEG compression), and
FlateEncode (lossless compression). The distiller commands are
embedded in the ps file. I looked at making it a flag on each image,
but couldn't get it to work. Another way to do it is to pass extra
command line options to ps2pdf (-dAutoFilterColorImages=false
 -sColorImageFilter=FlateEncode should do it for colour images). I
thought embedding it in the PS file would be more flexible.
My second problem involved the resolutions of the image. I'd like to
preserve the resolution of my image in the PS output, but I can't
figure out how to stop the image being resized and interpolated.
Obviously you need to do this for the bitmap backends, but for vector
ones surely you can just scale the original image in the vector
output.
Thanks in advance for you help and some great software!
JIM
---

Hi all,
 I would like to enable the key pressed event (key '1' '2' 'a' 'g' .. )
of NavigationToolbar2 in my pyGTK app.
(These keys shortcut are described here:
http://sourceforge.net/tracker/index.php?func=detail&aid=1432252&group_id=80706&atid=560722
)
The shorcuts work perfectly using pylab. But when I include matplotlib in my
pyGTK app the shorcuts are broken.
How could I manage to make them work,
and/or,
where I should start in the source code to undestand how it work, that I
could reproduce the shorkey behavior directly in my own application code?.
Thanks,
David

Bill Baxter wrote:
> I think all these problems could be fixed if the display interface
> were turned into a separate process
Have you tried ipython?
http://ipython.scipy.org/

 Hi,
	Trying out version 0.87.4 I noticed that the example given on
pages=20
http://matplotlib.sourceforge.net/screenshots/plotmap.py
and
http://scipy.org/Cookbook/Matplotlib/Maps
fail with :
In [1]: from matplotlib.toolkits.basemap import Basemap
-------------------------------------------------------------------------=
--
exceptions.ImportError Traceback (most
recent call last)
/home/varoquau/<ipython console>
ImportError: No module named toolkits.basemap
 I had a quick look and couldn't find where basemap had gone. How
should these pages be modified ?
--=20
 Ga=EBl