matplotlib-users Mailing List for matplotlib

I was informed that the windows binaries for numarray for
matplotlib-0.61.0 were accidentally built without support for GTK. I
uploaded new binaries this afternoon and they should make it to the SF
mirrors soon (tomorrow?). Please consider downloading them if you're
interested in the GTK backend and numarray. 
Regards,
Todd Miller

>>>>> "James" == James Boyle <bo...@ll...> writes:
 James> The checkerboard goes to the edges but the color overlay
 James> has a gap on the right and bottom. I have not been able to
 James> figure this out.
Nor have I completely, yet. It's related to interpolation (worse for
bilinear and bicubic that nearest). matlab handles this (at least for
pcolor) by setting the axes lim to not include the last row. Eg, for
a 5x5 pcolor grid, the axes would be 4x4.
This is part of the problem, but there may be an off-by-one or
rounding error as well.
It's a priority to fix, only it ain't fixed yet!
JDH

in the example directory the layer_images.py produces a plot that has 
space between the color plot and the axes on the right side and the 
bottom.
This occurs if I use the PS or Agg backend. It is evident in the 
example plot in the 'Screenshots' examples:
http://matplotlib.sourceforge.net/screenshots/layer_images_large.png
The checkerboard goes to the edges but the color overlay has a gap on 
the right and bottom.
I have not been able to figure this out.
Thanks for any enlightenment.
Jim

>>>>> "FP" == Fernando Perez <Fer...@co...> writes:
 FP> The code already works fairly well, with one significant
 FP> caveat: any process started via os.system() (whether directly
 FP> or implicitly using !cmd) will hang after a while. I have
 FP> currently no solution for this, but will welcome any ideas.
 FP> Note that the problem seems to only affect long-running GUI
 FP> apps, simple '!grep foo *' type things appear to function just
 FP> fine. But something like '!gv foo.eps &' will open gv, and
 FP> after about 30 seconds the gv instance stops responding to all
 FP> keyboard/mouse input.
You probably already have tried this but how about using
os.spawnl(...). Here a simple use case:
 pid = os.spawnl(os.P_NOWAIT, script, script)
cheers,
prabhu

Hi all,
after help and discussions with John, I'm putting up AS ALPHA CODE, a small 
script which will load ipython in a multithreaded mode which allows it to run 
GTK gui apps, and in particular matplotlib with the GTK backends.
Please note that using this requires at the moment _both_ CVS ipython and CVS 
matplotlib, since John and I have worked in conjunction to make the necessary 
changes.
The code already works fairly well, with one significant caveat: any process 
started via os.system() (whether directly or implicitly using !cmd) will hang 
after a while. I have currently no solution for this, but will welcome any 
ideas. Note that the problem seems to only affect long-running GUI apps, 
simple '!grep foo *' type things appear to function just fine. But something 
like '!gv foo.eps &' will open gv, and after about 30 seconds the gv instance 
stops responding to all keyboard/mouse input.
Debugging multithreaded code is _very_ tricky, but this tool may prove useful 
to many who want the interactive convenience of ipython combined with the 
better matplotlib backends, or other GTK apps. All feedback from willing 
testers will be very welcome.
Note that those wanting to use matplotlib interactively, and willng to stick 
to the Tk backends, can already do so. Tk does not require manual threading 
control, so it works perfectly OK with normal ipython. John already posted in 
the past a 'pylab' ipython profile which loads and configures matplotlib for 
such use, I can repost it if necessary.
This will become part of ipython 0.6.3, but I want to try to resolve the 
os.system() deadlock first. Since both John and I are complete ignoramuses on 
threading issues, help from anyone with knowledge on the topic is most welcome.
If you don't want to update to CVS ipython/matplotlib but think you may have 
an idea, you can use this small shell for tests:
http://amath.colorado.edu/faculty/fperez/tmp/pyint-gtk.py
It provides a basic multithreaded shell as a standalone python script (no 
matplotlib or ipython needed), and will show the os.system() deadlock problem.
Many thanks in advance for any feedback, and to John for all the help on this. 
 We (I assume I speak for both John and I here :) hope you all find it useful.
Best,
f

I second that. This is:
- a great library and 
- an even better community
- and above all built on a langauge that I love
--- Darren Dale <dd...@co...> wrote:
> I wanted to share a story. We are running our
> experiment at the 
> synchrotron, which now includes a digital camera for
> X-rays. We take a 
> LOT of pictures. Yesterday, the guys realized they
> had no way to follow 
> the progress of the experiment, because they didnt
> have a good way to 
> look at these pictures as they are being created. We
> would be running blind.
> 
> In a couple hours, I hacked together a working
> program. Mostly, I 
> modified bits of your examples, specifically
> dynamic_image_wxagg, plus 
> coords and a few others, and learned some things
> about wx along the way. 
> The matplotlib event handling is great, I am putting
> it to good use. 
> People in the lab are really impressed with the
> quality of the plots, 
> and how quickly the code came together, both of
> which I attribute to 
> your work. Thank you.
> 
> Darren
> 
> 
> 
>
-------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest
> price on Blank Media
> 100pk Sonic DVD-R 4x for only 29ドル -100pk Sonic DVD+R
> for only 33ドル
> Save 50% off Retail on Ink & Toner - Free Shipping
> and Free Gift.
>
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
>
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 

I wanted to share a story. We are running our experiment at the 
synchrotron, which now includes a digital camera for X-rays. We take a 
LOT of pictures. Yesterday, the guys realized they had no way to follow 
the progress of the experiment, because they didnt have a good way to 
look at these pictures as they are being created. We would be running blind.
In a couple hours, I hacked together a working program. Mostly, I 
modified bits of your examples, specifically dynamic_image_wxagg, plus 
coords and a few others, and learned some things about wx along the way. 
The matplotlib event handling is great, I am putting it to good use. 
People in the lab are really impressed with the quality of the plots, 
and how quickly the code came together, both of which I attribute to 
your work. Thank you.
Darren