Re: Updating MPlot3D to a more recent matplotlib.

Hey Reiner -- please make sure you "reply-to-all" so others can
participate in the thread.  I'm am CC-ing the reply to the list.

On Wed, Apr 1, 2009 at 5:19 PM, Reinier Heeres <reinier@...> wrote:

> That is one issue, but if I try to solve that I get some
> strange-looking result. It seems that the patches I am drawing are not
> scaled properly; they are way too large. Do you know of any obvious
> change that might have resulted in this (I guess it might be in the
> "transform" parts)? And is there perhaps a nice web-interface to
> compare different versions of various files?

What version of mpl are you using?  The major transform work was done
between 0.91 and 0.98, which is why we removed the 3D stuff at that
time.  I assume you are already on some version of 0.98, so hopefully
the transforms changes from your branch to svn HEAD will be minimal.
The code diffs can be found at
http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/matplotlib/

I also removed the TextWithDash and saw the scaling problems you point to.

JDH

------------------------------------------------------------------------------

OpenGL backend and pyglet expertiments

Hello,

While looking at possible solutions for a matplotlib OpenGL backend,
I've been experimenting with pyglet (that has no dependencies) and coded
a terminal with embedded 2d arrays display.

Sources & screenshots are available at:
http://www.loria.fr/~rougier/glnumpy.html

Since pyglet seems mature enough, I would like to know if anyone
interested in helping writing the OpenGL backend (using pyglet) ?

Nicolas

------------------------------------------------------------------------------

Re: OpenGL backend and pyglet expertiments

The idea of a shell with inline plots is a fascinating one - I like
the minimalism and directness of being able to plot data like this.
And the speed of OpenGL is obviously attractive.

Is the figure() call syntax different from the existing syntax for
figure()? I think there's a usage pattern ingrained in my head that
says 'figure => new window,' and any change to the call syntax for
figure would seem to open up a lot of room for confusion.

It seems that the backend and the shell might be separate issues? My
view of the backends is that they only deal with knowing how to draw
artists, and are separate from the process of creating those artists
through an interactive shell.

The following old thread is also relevant, which you may have already seen:
http://www.nabble.com/opengl-backend-td19192625.html

Thanks,
Eric B

On Fri, Apr 3, 2009 at 7:17 AM, Nicolas Rougier
<Nicolas.Rougier@...> wrote:
>
> Hello,
>
> While looking at possible solutions for a matplotlib OpenGL backend,
> I've been experimenting with pyglet (that has no dependencies) and coded
> a terminal with embedded 2d arrays display.
>
> Sources & screenshots are available at:

Re: OpenGL backend and pyglet expertiments

Hi,

I agree, shell with inline plot is a different issue. I mainly coded  
it as a proof a concept and because I find it useful for my own needs.

The figure call is quite different from the figure call of matplotlib,  
only the name is common.
The idea was to be able to describe a configuration of arrays with a  
minimum amount of code.

figure(Z) -> plot Z
figure([Z1,Z2]) -> plot Z1,Z2 side by side
figure([[Z1,Z2], [Z3,Z4]]) -> plot Z1,Z2 side by side and below, Z3,Z4  
side by side

You can optionally indicate that an array spans several rows or columns:

figure([[Z1,'-'],
	     [Z3,Z4]]) -> plot Z1 on two columns and below, Z3,Z4 side by side
figure([[Z1,Z2],
	     ['|', Z4]]) -> plot Z1 on two rows,  then Z2 on first line and  
Z4 on second line.

I looked at the thread you're talking about and it was the reason in  
the first place that I investigated pyglet.
My approach is a bit different since I use a texture and a single quad  
to render it, it makes things quite fast. The mapping from a float  
array to a texture data is pretty efficient using numpy interface and  
it allows me to continuously update texture data (just try modifying  

Re: OpenGL backend and pyglet expertiments

On Fri, Apr 3, 2009 at 4:17 AM, Nicolas Rougier
<Nicolas.Rougier@...> wrote:
>
> Hello,
>
> While looking at possible solutions for a matplotlib OpenGL backend,
> I've been experimenting with pyglet (that has no dependencies) and coded
> a terminal with embedded 2d arrays display.
>
> Sources & screenshots are available at:
> http://www.loria.fr/~rougier/glnumpy.html

Wow, the screenshots look gorgeous!

Unfortunately I tried to run it after installing it in my path and I
got this (same for glnumpy):

uqbar[bin]> ./glpython
Traceback (most recent call last):
  File "./glpython", line 70, in <module>
    logo = pyglet.resource.image('logo.png')
  File "/var/lib/python-support/python2.5/pyglet/resource.py", line
481, in image
    identity = self._cached_images[name] = self._alloc_image(name)
  File "/var/lib/python-support/python2.5/pyglet/resource.py", line
425, in _alloc_image
    file = self.file(name)
  File "/var/lib/python-support/python2.5/pyglet/resource.py", line 383, in file
    raise ResourceNotFoundException(name)
pyglet.resource.ResourceNotFoundException: Resource "logo.png" was not

Re: OpenGL backend and pyglet expertiments

Sorry for that, I coded it on linux and just tested on mac.
I fixed the error and upload the new version on the same link. Tell me  
if it's ok.

Nicolas

On 3 Apr, 2009, at 18:55 , Fernando Perez wrote:

> On Fri, Apr 3, 2009 at 4:17 AM, Nicolas Rougier
> <Nicolas.Rougier@...> wrote:
>>
>> Hello,
>>
>> While looking at possible solutions for a matplotlib OpenGL backend,
>> I've been experimenting with pyglet (that has no dependencies) and  
>> coded
>> a terminal with embedded 2d arrays display.
>>
>> Sources & screenshots are available at:
>> http://www.loria.fr/~rougier/glnumpy.html
>
> Wow, the screenshots look gorgeous!
>
> Unfortunately I tried to run it after installing it in my path and I
> got this (same for glnumpy):
>
> uqbar[bin]> ./glpython
> Traceback (most recent call last):
>  File "./glpython", line 70, in <module>

Re: OpenGL backend and pyglet expertiments

On Fri, Apr 3, 2009 at 10:00 AM, Nicolas Rougier
<Nicolas.Rougier@...> wrote:
>
>
> Sorry for that, I coded it on linux and just tested on mac.
> I fixed the error and upload the new version on the same link. Tell me if
> it's ok.

Great!

Would you have any interest in having this be shipped/developed as
part of IPython itself?

You are using a fair amount of internals of the ipython machinery, and
we're getting ready for a large cleanup.  Having your code shipped
with ipython itself would give it perhaps more exposure, as well as
allow it to evolve in sync with the rest of the API, since we could
test it as the internals change.

I think it would be great to ship this with ipython itself, and I'm
sure you'd get help and contributions from the rest of the ipython
team as well...

Best,

f

------------------------------------------------------------------------------

[Fwd: [Matplotlib-users] imshow without resampling]

Jouni, Darren,

I'm not sure who the SVG expert is, and I presume the attached message 
applies to pdf as well as ps.  I'm bringing it to your attention because 
it is suggesting what would seem to be significant improvements in some 
backends by taking better advantage of their native image support.  I 
know nothing about this; would either of you (or anyone else) like to 
comment?

Eric

From: Thomas Robitaille <thomas.robitaille@...>
Subject: [Matplotlib-users] imshow without resampling
Date: 2009-03-31 19:56:24 GMT

Hello,

I am using matplotlib to create postscript and SVG files. I am  
currently using imshow to show the contents of an array, but this  
means that when saving vector graphics files, matplotlib resamples the  
image/array onto a finer grid. What I would like, is for code such as  
this:

import matplotlib

Re: OpenGL backend and pyglet expertiments

Eric Bruning wrote:
> The idea of a shell with inline plots is a fascinating one -

Then check out reinteract -- very cool:

http://www.reinteract.org/trac/

(though no opengl)

-Chris

--

-- 
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chris.Barker@...

------------------------------------------------------------------------------

including AxesGrid in main mpl source?

John,

About a week ago, I introduced my own mpl toolkit
(http://dl.getdropbox.com/u/178748/AxesGrid/htdocs/index.html) in the
mpl dev-list. And I wonder if this package can be included in the main
matplotlib source.

As a matter of fact, I was a bit reluctant to do this because the
package is poorly documented at this moment. However, other people
(Matthew Turk and Jeff Oishi) showed their interests in this package
going into the main matplotlib source, and they're willing to help me
to improve the documentation (and other aspects).

I couldn't find any policy (or similar thing) about mpl_toolkits.
Currently, my package is consist of several pure python modules, so
including this in the main source would be straight forward.

Regards,

-JJ

------------------------------------------------------------------------------