matplotlib

I have great working matplotlib pylab code that fires
off a new plot when asked to.

Now we want to embed/add this code into an existing
wx gui....Is it possible to make the pylab code
embed the plot into an existing gui window rather than creating
a //new// plot window/widget?

Also, a colleague says wx doesn't seem to play nice
with pylab module.  Is pylab somehow slower or not
the best fit with wx??  He says 'Figure()' code seems
better with wx.  Any advice/comments greatly appreciated.

Sincerely,

Chris

Hi :

I hava a plot with mayor and minor ticks and
formatters. I want to rotate the labels of both the
mayor and minor ticks. I tried with the following
code:

#...
ax.xaxis.set_major_locator(major)
ax.xaxis.set_major_formatter(fmt_ma)
ax.xaxis.set_minor_locator(minor)
ax.xaxis.set_minor_formatter(fmt_mi)
labels = ax.get_xticklabels()
pylab.set(labels, rotation=30, fontsize=10)

However, only the mayor labels are rotated. How can I
rotate both the major and minor labels?

Regards,
Alejandro.


		
__________________________________ 
Do you Yahoo!? 
The all-new My Yahoo! - Get yours free! 
http://my.yahoo.com

I am making graphics of some topographical images. Something simple like:

from pylab import *
z=rand(256,256)
figure(figsize=(4,3)) 
a1=axes([.1,.1,.7,.85]) 
a2=axes([.85,.1,.05,.85]) 
a2.yaxis.tick_right() 
a2.xaxis.set_ticks([])

a1.imshow(z,cmap=cm.bone,extent=(0,1,0,1))
colorbar('%1.1e',cax=a2)

show()

I am getting the jet colormap in the colorbar, is it possible to change it 
manually?

Darren

Hi folks,

I am trying to do something similar to:

from pylab import *
plot([1,2,3,4])
text(1,3,'a)')
savefig('test.eps')

I can't render the eps file because of the way that "a)" is recorded ["(a)" 
will render, so its just a parsing issue]. I think, in the eps file "(a)) 
show" should read "(a\)) show" for the image will render.

Changing line 353 in backend_ps.py to 

self._pswriter.write("(%s) show\n"%s.replace(')','\)').replace('(','\('))

would do the trick.

I'm using gentoo linux and matplotlib 0.71.
-- 

Darren

i'm currently using python 2.3(enthought edition) on win 2000/xp.
i'm using boa constructor on the GUI part and matplotlib 0.71 on
plotting the graph.

i am using an MDIParentFrame. one of the child frame will be used for
the table part. then another child frame will be used to show the
graph, how am i going to do this? will i just import the child frame
containing the tables and then i'll be able to just get the data from
the table and use it to plot a graph?
how am i going to assign to a variable each input to the table?
can you please show me a sample code to do this?
i'm a little lost since i'm a bit new to python.

also, how am i going to assign to a variable anything that a user
inputs to a wxTxtCtrl?

any help would greatly be appreciated. thanks and more power

Since pylab's 'load' function has come up,
it may be worth mentioning that it overrides scipy's load function.
(And of course Numeric has its own 'load'.)

It may be a bad habit,
but I doubt I'm the only one who occasionally does
from scipy import *
from pylab import *

I would even claim that both encourage this ...
especially for new users.  If that is correct,
and if scipy+pylab is a common pair (as I
believe it is), then perhaps ...

fwiw,
Alan Isaac

Hi,

I had a problem with the load function. I have a file with some data in 
two columns. I'm trying to use load:

x,y=load('toto.dat')

with toto something like:

1 3
3 4
5 6

I obtained the error message:

ValueError: too many values to unpack

I understanded why. It's because the array is not use by columns but by 
lines when you unpack the array from load to x and y so I don't have 
enough variable. To solve this problem I add the transpose function:

x,y=transpose(load('toto.dat'))

I don't know if I'm alone with this problem but if yes that will be a 
good idea to update the help of the function.

Thanks,

    Nicolas

>>>>> "Chris" == Chris Barker <Chris.Barker@...> writes:

    Chris> anyway, to cut my rant short, here is my vote for
    Chris> matplotlib development (not that I get a vote, but
    Chris> hopefully I'll have time to help out someday)

Hey, I live in Chicago -- we pioneered "vote early, vote often". 

    Chris> 2) Improve the OO interface to make it just as easy to use.

Do you have some suggestions which would make the OO interface easier
to use?  For concreteness, here is the archetypal OO script

  from matplotlib.backends.backend_svg import FigureCanvasSVG
  from matplotlib.figure import Figure
  fig = Figure()
  ax = fig.add_subplot(211)
  ax.plot([1,2,3])
  ax.set_xlabel('time')
  canvas = FigureCanvasSVG(fig)
  canvas.print_figure('myfile.svg')

Things that leap to my mind:

  * hide the complexity of having both a canvas and the figure from
    the user, allowing them to deal only with figures, or at least
    have the figure store a ref to its canvas and allow you to do

    fig.savefig('myfig')
 
    which can forward the call on to its canvas print_figure method.

    This would bring the OO interface closer to the pylab interface
    and would prevent you from having to remember which methods were
    fig methods and which methods were canvas methods.  We could also
    provide a pylab independent factory function that instantiates a
    figure and canvas with the relevant initialization, allowing you to
    do something like

    fig, canvas = figure_factory(*args, **kwargs)  # use the current backend

    but I'm not sure how advisable it is to hide this complexity
    because what you ultimately do with the objects depends on whether
    you are using a GUI backend or not.  But for pure image backends
    it would be possible to have a single OO interface which works
    across backends.

  * move the (few) remaining pylab only methods (axis, colorbar) into
    the OO framework for full compatibility

  * use properties/traits so you could do

     ax.xlabel = 'hi mom'

    while retaining the setters and getters for backwards
    compatibility

  * provide more pure OO examples in the examples directory

  * significant;y expand the OO section of the user's guide

Do you have additional ideas?  Or are these the issues your were thinking of?

JDH

----- Original Message -----
From: John Hunter <jdhunter@...>
> Eg, if you have set your dpi parameter correctly to reflect your
> monitor 
> 
>    from pylab import *
>    fig = figure(dpi=96)
>    plot([1,2,3])
>    text(1,2,'hi mom', fontsize=72)
>    show()
> 
> creates text that is an inch high, irrespective of the view port.  I
> think this is the behavior most people expect, at least those who are
> used to thinking about fontsizes in points.

Well, I'd rather set the fontsize in Pixels, but I suppose I can do that
by setting DPI to 72. However, you generally don't want to zoom text as
you zoom in and out, you are zooming in on teh DATA, no the PICTURE of
the data.

By the way, if you do want that, check out my FloatCanvas, in the
wxPython lib. You'll have to draw your own Axes, but if you use
ScaledText, you'll get the whole picture to zoom and scroll.

-Chris

Hi all,

How can I add vertical/horizontal  lines (x=constant, y=constant 
respectively) to an existing plot with matplotlib ?
A small example would be appreciated.

Is there a simple command to plot closed polygons, which are defined by 
the coordinates  of the vertices ?
 
Thanks in advance.

Nils

I know if I modify the code, I can avoid these things. But out of my =
eccentric nature, all I am asking is how to do the zooming more nicely?

o The zooming of text, as you can test in <mathtext_demo.py>. I remember =
once I put some mathtext symbols, as I wished to see the subscript I =
tried zoom to see more sharply but I failed. I saved png and zoomed =
finally.
o The zooming of subplot, as you can test in <axes_demo.py>, well =
personally I assume if you zoom on a subplot you would expect it gets =
enlarged.
o The zooming of crosshaired frontend, as you can test in =
<wxcursor_demo.py>, this is minor problem, but when I zoom a random =
area, I see a vestigial image of the cross-hair which is a tiny bit =
unnatural.

And of course the speed of zooming...  but I see the pylab is redrawing =
the figure so this is understandable. I know this is a plotting module =
not an ACDsee or picasa, so forgive my eccentricity.

btw: along with this note
- how to insert a space in a bunch of mathtext as I wish to put spaces =
near '=3D'?
- could you stop the interactive console (at least make it configurable) =
after the figure is closed so that I don't need to put sys.exit().

Thank you (smile).

Bao=20

On Jan 26, 2005, at 10:14 AM, John Hunter wrote:

>>>>>> "Haibao" == Haibao Tang <bao@...> writes:
>
>     Haibao> Hi folks, I've noticed that zooming on the text won't make
>     Haibao> the text any larger, and some other instances like
>     Haibao> sub-axes share the problem too. And it is not the default
>     Haibao> zoom behavior people usually expect. Any solution to that?
>
> Well, I suspect we'd have to poll people to know whether this is the
> behavior they usually expect....
>
Exactly. I'd guess that most people would not want the text to zoom. I 
don't. If one takes zooming as a literal zoom of everything in the 
field, yes, I can understand that is what some might expect. But what 
is really most useful? I doubt that literal zooming is in the great 
majority of cases.

Perry