matplotlib-users Mailing List for matplotlib (Page 7)

In case there is some interest, I changed _mathtext_data.py to support 
nonslanted uppercase greek characters rather (\Omega & stuff, see .diff).


BTW, in _mathtext_data.py there is a line

font = FT2Font('/usr/local/share/matplotlib/cmr10.ttf')

I think this is a obsolete location, right? (at least I don't have it)

cheers,
steve

-- 
Random number generation is the art of producing pure gibberish as 
quickly as possible.

Christopher Barker wrote:
> Hi all,
> 
> I'm working on a MPL build for OS-X, and I'd like to be able to write 
> scripts that will test as much as I can. In particular, I want to have 
> this build work with Numeric, numarray and numpy.
> 
> To script that test, I need to be able to set numerix in a script, 
> rather than in matplotlibrc. Can that be done?

For testing you may also take advantage of command-line arguments:

python examples/image_demo.py --Numeric

for example, runs using Numeric as the numerix setting.

The relevant code in numerix/__init__.py is:
for a in sys.argv:
     if a in ["--Numeric", "--numeric", "--NUMERIC",
              "--Numarray", "--numarray", "--NUMARRAY",
              "--NumPy", "--numpy", "--NUMPY", "--Numpy",
              ]:
         which = a[2:], "command line"
         break
     del a

If such a command-line option is found, it overrides everything else.

Eric

On Thursday 13 July 2006 8:08 pm, Brian Wilfley wrote:
> Hello,
>
> I've just come across matplotlib and I'm very impressed. It looks very
> useful.
>
> I just installed on a WinXP machine:
> enthon-python2.4-1.0.0.beta3.exe
> matplotlib-0.87.4.win32-py2.4.exe.
>
> The install went fine. I also put the default matplotlibrc file into
> my %HOME%\.matplotlib.
>
> I ran ipython from the "Start" menu. Note that this runs ipython
> without the -pylab argument.
>
> I started to try the first example and had a problem with "from pylab
> import * ". Also this failure occured using the "ordinary" python
> shell. The output from ipython is below.
>
> I'm afraid I mixed and matched inappropriately withe the enthought 2.4
> beta 3 and matplotlibe 0.87.4 py2.4 pairing.
>
> Any thoughts?

>
> RuntimeError: module compiled against version 90709 of C-API but this
> version of numpy is 90907

I think the numpy version provided with enthought is pulled from the svn 
repository. If this is true, it will make life difficult for packages like 
matplotlib for windows that are compiled against the latest numpy release, in 
this case 0.9.8. Somebody please correct me if I'm wrong.

Hello,

I've just come across matplotlib and I'm very impressed. It looks very useful.

I just installed on a WinXP machine:
enthon-python2.4-1.0.0.beta3.exe
matplotlib-0.87.4.win32-py2.4.exe.

The install went fine. I also put the default matplotlibrc file into
my %HOME%\.matplotlib.

I ran ipython from the "Start" menu. Note that this runs ipython
without the -pylab argument.

I started to try the first example and had a problem with "from pylab
import * ". Also this failure occured using the "ordinary" python
shell. The output from ipython is below.

I'm afraid I mixed and matched inappropriately withe the enthought 2.4
beta 3 and matplotlibe 0.87.4 py2.4 pairing.

Any thoughts?

Thanks for your help.

Brian



--------------------ipython shell output----------------------------------
**********************************************************************
Python 2.4.3 - Enthought Edition 1.0.0.beta3 (#69, Jul  6 2006, 11:38:02) [MSC v
.1310 32 bit (Intel)]
Type "copyright", "credits" or "license" for more information.

IPython 0.7.2 -- An enhanced Interactive Python.
?       -> Introduction to IPython's features.
%magic  -> Information about IPython's 'magic' % functions.
help    -> Python's own help system.
object? -> Details about 'object'. ?object also works, ?? prints more.

In [1]: from pylab import *
C:\Python24\lib\site-packages\matplotlib\font_manager.py:453: UserWarning: Could
 not open font file C:\WINDOWS\Fonts\ORLANDO.TTF
  warnings.warn("Could not open font file %s"%fpath)
---------------------------------------------------------------------------
exceptions.RuntimeError                              Traceback (most recent call
 last)

C:\Python24\<ipython console>

C:\Python24\Lib\site-packages\pylab.py
----> 1 from matplotlib.pylab import *

C:\Python24\Lib\site-packages\matplotlib\pylab.py
    198 import mlab  #so I can override hist, psd, etc...
    199
--> 200 from axes import Axes, PolarAxes
    201 import backends
    202 from cbook import flatten, is_string_like, exception_to_str, popd, \

C:\Python24\Lib\site-packages\matplotlib\axes.py
     21 import cm
     22 from cm import ScalarMappable
---> 23 from contour import ContourSet
     24 import _image
     25 from ticker import AutoLocator, LogLocator, NullLocator

C:\Python24\Lib\site-packages\matplotlib\contour.py
     16
     17 from mlab import linspace, meshgrid
---> 18 import _contour
     19 from cm import ScalarMappable
     20 from cbook import iterable, is_string_like, flatten, enumerate, \

C:\Python24\Lib\site-packages\matplotlib\_contour.py
     15 else:                 # Must be numpy
     16     try:
---> 17         from matplotlib._ns_cntr import *
     18     except ImportError:
     19         numerix._import_fail_message("_contour", "_ns")

RuntimeError: module compiled against version 90709 of C-API but this version of
 numpy is 90907

In [2]:
----------------------------------------------------------

Christopher Barker wrote:
> To script that test, I need to be able to set numerix in a script, 
> rather than in matplotlibrc. Can that be done?

Yep, just do

from pylab import *
rcParams['numerix'] = 'numpy'

> While we're at it, it would be great if ANY of the config items in 
> matplotlibrc could, instead, be set at run time in a script. I now a 
> number of them can, but is there a standard way to do, and will it work 
> with ALL the items in there?

rcParams is the standard way and I think works for all items.

> Another note: it seems that numerix is very good at taking input from 
> any of the Num* packages, regardless of which one is being used 
> internally. Given that, I'm thinking of aiming for the future with my 
> OS-X package, and just using numpy, and not bothering to build in 
> support for the other two. any thoughts.
> 
> -Chris

If I was developing something now, I would only bother supporting numpy.

Gary R.

Hi Rob,

A couple of us reported this last week on the scipy list and I think it 
should be fixed in the version which was just released by Enthought, so 
if your friend will persevere and grab the latest version, it should be 
OK - I hope to try it out today.

Gary R.

Rob Hetland wrote:
> 
> I am trying to help somebody get going on numpy/scipy/mpl.  She is 
> having trouble when starting enthon's matplotlib.  She is a PC user (I 
> am a unix/mac person), so I really don't know where to start finding the 
> problem.  Below is her note to me.  Any advice would be helpful.
> 
> 
> """
> I got the enthought python etc. distribution (dated 7/5/06) again after
> talking to you, and still get the same error with "from pylab import *"
> Unfortunately, I can't grab the text from the ipython shell window, but
> the gist is that pylab.m, tries to import Xaxis and Yaxis from axis,
> axis.py tries to get FontProperties from font_manager.py, which in turn
> looks for ft2font in matplotlib.   Which is where the error message box
> saying "entry point _ctype could not be located in the dll lib
> msvcr71.dll" gets created.  Maybe we should get another dummy tester to
> try it.  My system has several mscvr71.dll's and it's probably choosing to
> use the wrong one....
> """

Hi all,

I'm working on a MPL build for OS-X, and I'd like to be able to write 
scripts that will test as much as I can. In particular, I want to have 
this build work with Numeric, numarray and numpy.

To script that test, I need to be able to set numerix in a script, 
rather than in matplotlibrc. Can that be done?

While we're at it, it would be great if ANY of the config items in 
matplotlibrc could, instead, be set at run time in a script. I now a 
number of them can, but is there a standard way to do, and will it work 
with ALL the items in there?

Another note: it seems that numerix is very good at taking input from 
any of the Num* packages, regardless of which one is being used 
internally. Given that, I'm thinking of aiming for the future with my 
OS-X package, and just using numpy, and not bothering to build in 
support for the other two. any thoughts.

-Chris




-- 
Christopher Barker, Ph.D.
Oceanographer
                                     		
NOAA/OR&R/HAZMAT         (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chr...@no...

On Thu, 13 Jul 2006, John Hunter wrote:

> for x,y in zip(xs, ys):
>    ax.text(x+width/2., y, '%1.1f'%y, va='bottom', ha='center')

John, that did the trick perfectly!  Thanks a million!

-- Asheesh.

-- 
Tuesday After Lunch is the cosmic time of the week.

>>>>> "Asheesh" == Asheesh Laroia <as...@as...> writes:
    Asheesh> How do I show the *values* of the bars?  I'm sorry if I'm
    Asheesh> not using the right terminology.  Thanks all!

You need to create text instances at the places you want the bar
labels -- something like

from pylab import figure, nx, show

width = 0.5
xs = nx.arange(7)
ys = nx.mlab.randn(7)+5

fig = figure()
ax = fig.add_subplot(111)
ax.bar(xs, ys, width=width)

for x,y in zip(xs, ys):
    ax.text(x+width/2., y, '%1.1f'%y, va='bottom', ha='center')

show()

On Thu, 13 Jul 2006, PGM wrote:

> Vertical bars, I assume ?

Yup.

> Please check the screenshot page:
> http://matplotlib.sourceforge.net/screenshots/barchart_demo.py
> should be a big help.

It doesn't show how to put numbers above the bars.  It shows a lot of 
other things, and it was helpful for other things. (-:

> You can find  other examples here
> http://matplotlib.sourceforge.net/matplotlib_examples_0.87.1.zip.
>
> If you're into OOP, check  the "set_xticklabels" command.

Those set labels at the bottom.  I know how to set those.

I want to add labels (maybe that's not the right word?) to the *top* or 
the *inside* of the bars themselves that say the actual values.  Showing 
the numbers (as percentages) seems to be the default in pie graphs, at 
least, as per http://matplotlib.sourceforge.net/screenshots.html .

How do I show the *values* of the bars?  I'm sorry if I'm not using the 
right terminology.  Thanks all!

-- Asheesh.

-- 
You will gain money by a speculation or lottery.

I am trying to help somebody get going on numpy/scipy/mpl.  She is  
having trouble when starting enthon's matplotlib.  She is a PC user  
(I am a unix/mac person), so I really don't know where to start  
finding the problem.  Below is her note to me.  Any advice would be  
helpful.


"""
I got the enthought python etc. distribution (dated 7/5/06) again after
talking to you, and still get the same error with "from pylab import *"
Unfortunately, I can't grab the text from the ipython shell window, but
the gist is that pylab.m, tries to import Xaxis and Yaxis from axis,
axis.py tries to get FontProperties from font_manager.py, which in turn
looks for ft2font in matplotlib.   Which is where the error message box
saying "entry point _ctype could not be located in the dll lib
msvcr71.dll" gets created.  Maybe we should get another dummy tester to
try it.  My system has several mscvr71.dll's and it's probably  
choosing to
use the wrong one....
"""


----
Rob Hetland, Assistant Professor
Dept. of Oceanography, Texas A&M University
http://pong.tamue.edu/~rob
phone: 979-458-0096, fax: 979-845-6331

On Thursday 13 July 2006 14:05, Asheesh Laroia wrote:
> I'm making a bar chart that shows percentages (values from 0 to 100), and
> I'd like to have the actual bars labeled with their values.
>
> I don't see how to do this, though it seems that countour diagrams have
> the clabel() function to do this.  Is it possible with matplotlib?

Vertical bars, I assume ?
Please check the screenshot page:
http://matplotlib.sourceforge.net/screenshots/barchart_demo.py 
should be a big help.
You can find  other examples here 
http://matplotlib.sourceforge.net/matplotlib_examples_0.87.1.zip.

If you're into OOP, check  the "set_xticklabels" command.

Mark Bakker wrote:
> Eric -
> 
> To be honest, I think the native array storage order matters a lot.
> When you have a large dataset, transposing the matrix is not a cheap 
> command.

No, in this context it is very cheap relative to the rest of the plotting.

> 
> But I also understand the logic of plotting column against column.
> However, a 1D vector in Python is by default a row, while in Matlab it 
> is a column.
> What are you going to do if a 1D row is given as first argument and a 
> matrix as second???

No problem.  It is easy to treat a 1D array as either a column or a row, 
depending on whether one has chosen option 3 or option 4.  This could 
even be controlled by an rc option and/or a kwarg, but I think this is a 
bad idea.  Better to just pick 3 or 4 and stick with it, using transpose 
when needed.  Keep things simple and explicit.

> 
> I don't like the Matlab model when one matrix is passed. It should 
> really plot the first column along
> the x-axis and all the other columns along y. Like your 2nd option 
> below, but with NxM array.
> It would then be very nice to have an optional argument to the function 
> to plot all rows against the first row. That would be very easy to 
> implement and keep everybody happy.

To make sure I understand you: you are suggesting a kwarg that tells the 
plot command to plot subsequent rows (or it could be columns) against 
the first?  Something like

plot(Z, xvec='row')
plot(Z, xvec='column')
plot(Z, xvec=None)      #default: present behavior

But why is this better than the following?

plot(Z[0,:], Z[1:,:])

The latter would accomplish the same, be completely consistent with 
option 4, be completely explicit and unambiguous, require no more typing 
than using a kwarg, require no extra logic in the plot code, and require 
no extra documentation for the plot command.

Eric
> 
> As you said, there will be many more opinions,
> 
> Mark
> 
>  
> 
>     To summarize, the options seem to be:
> 
>     1) Leave plot argument parsing alone.
>     2) Accept an Nx2 array in place of a pair of arguments containing x
>     and y.
> 
>     3) Implement the Matlab model.
>     4) Implement the Matlab model, but taking rows instead of columns in an
>     X or Y array that is 2-D.
> 
>     I am open to arguments, but my preference is the Matlab model.  I don't
>     think that the difference in native array storage order matters much.
>     It is more important to have the API at the plot method and function
>     level match the way people think.
> 
>     Eric
> 
> 
> 
> ------------------------------------------------------------------------
> 
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

I'm making a bar chart that shows percentages (values from 0 to 100), and 
I'd like to have the actual bars labeled with their values.

I don't see how to do this, though it seems that countour diagrams have 
the clabel() function to do this.  Is it possible with matplotlib?

Thanks!

-- Asheesh.

-- 
You single-handedly fought your way into this hopeless mess.

Stefan van der Walt wrote:
> On Thu, Jul 13, 2006 at 10:34:11AM +0200, Mark Bakker wrote:
> 
>>To be honest, I think the native array storage order matters a lot.
>>When you have a large dataset, transposing the matrix is not a cheap
>>command.
> 
> 
> If you use numpy, transposing is cheap.  You see it when you try
> 
> import numpy as N
> z = N.random.random([1000,1000])
> print "Transposing..."
> for x in range(10000): z.transpose()
> 
> in the latest SVN of numpy, they also have the convencience-shorthand
> of z.T (which calls z.transpose()).

It is especially cheap in comparison to everything else that happens 
when one plots with matplotlib!  Utterly negligible.

Eric

Hi Benoit,

leg.draw_frame(False) might be an option, but I use
self.axes.grid(True) and when the legend has no
borders, the grid is shown through the text and makes
ist nearly unredable.

-- Till Wagner

> why don't you try to remove the legend frame?

>>  self.axes.plot(x_value, y_value, 'k-', 
>>                 label = labelLegend)
>> 
>>  self.axes.legend(loc = 'best', pad = 0.1)
>>  leg = self.axes.get_legend()
>
> leg.draw_frame(False)
>
> You won't have any problem with the legend box 
> anymore.  but maybe, I didn't understand what you
> want...
>
> Benoit

--
"Since man's natural instincts lead him to sin, all men are sinners;
and all sinners go to hell.  If everyone goes to hell, then you will
meet all your friends there. Heaven must be populated with some
rather strange creatures if all they lived for was to go to a place
where they can stump harps for eternity."- Anton Szandor LaVey
------------------------------------------------------------------------
Till Wagner <sac...@ya...>


	

	
		
___________________________________________________________ 
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de

On 7/13/06, John Hunter <jdh...@ac...> wrote:
> >>>>> "Charlie" == Charlie Moad <cw...@gm...> writes:
>
>     Charlie> Thanks for the note.  This is a known issue and has been
>     Charlie> addressed in svn.  The mplot modules have been added to
>     Charlie> svn and are being worked on.
>
> Actually, these changes are in 0.87.4, I think.

They are fixed in the matplotlib modules, but I guess I was referring
to the issue existing in mplot3d. Maybe the scipy wiki should mention
that it doesn't work with newer versions of mpl.  I don't know the
originally targeted version though.

- Charlie

>>>>> "Charlie" == Charlie Moad <cw...@gm...> writes:

    Charlie> Thanks for the note.  This is a known issue and has been
    Charlie> addressed in svn.  The mplot modules have been added to
    Charlie> svn and are being worked on.

Actually, these changes are in 0.87.4, I think.

JDH

Thanks for the note.  This is a known issue and has been addressed in
svn.  The mplot modules have been added to svn and are being worked
on.

- Charlie

On 7/12/06, Andrew M. Bradley <am...@st...> wrote:
> Hi:
>
> I obtain the following error when saving a figure to postscript after
> running one of the test routines in mplot3d.py:
>
> >>> from numpy import *; import mpl3d.mplot3d as p3; import pylab as p
> >>> p3.test1()
> >>> p.savefig('test1')
> Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
>   File "/usr/local/lib/python2.4/site-packages/matplotlib/pylab.py",
> line 811, in savefig
>     return fig.savefig(*args, **kwargs)
>   File "/usr/local/lib/python2.4/site-packages/matplotlib/figure.py",
> line 660, in savefig
>     self.canvas.print_figure(*args, **kwargs)
>   File "/usr/local/lib/python2.4/site-packages/matplotlib/backends/backend_ps.py",
> line 1061, in print_figure
>     self.figure.draw(renderer)
>   File "/usr/local/lib/python2.4/site-packages/matplotlib/figure.py",
> line 531, in draw
>     for a in self.axes: a.draw(renderer)
>   File "/usr/local/lib/python2.4/site-packages/mpl3d/mplot3d.py", line
> 714, in draw
>     self.w_xaxis.draw(renderer)
>   File "/usr/local/lib/python2.4/site-packages/mpl3d/mplot3d.py", line
> 613, in draw
>     tick.draw(renderer)
>   File "/usr/local/lib/python2.4/site-packages/matplotlib/axis.py",
> line 161, in draw
>     if self.label1On: self.label1.draw(renderer)
>   File "/usr/local/lib/python2.4/site-packages/matplotlib/text.py",
> line 1166, in draw
>     self.update_coords(renderer)
>   File "/usr/local/lib/python2.4/site-packages/mpl3d/mplot3d.py", line
> 411, in update_coords
>     return text_update_coords(self, renderer)
>   File "/usr/local/lib/python2.4/site-packages/mpl3d/mplot3d.py", line
> 102, in text_update_coords
>     we = self._mytext.get_window_extent(renderer=renderer)
> AttributeError: TextWithDash instance has no attribute '_mytext'
>
> I installed matplotlib-0.87.3 and mpl3d yesterday and today. After a
> bit of hunting, I noticed there are two similar definitions of
> TextWithDash in matplotlib's text.py: _TextWithDash and TextWithDash.
> Noting the underscored version defines _mytext but the underscore-free
> version does not, I switched the underscores. Now things are working
> (though perhaps I've broken something else in the process). I suspect
> the error is a product of on-going changes to matplotlib; nonetheless,
> I thought my email might be helpful to others.
>
> Andrew
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

On Thursday 13 July 2006 10:32, Martin Manns wrote:
> > The bigger problem is that each file format has basic characteristics
> > and limitations.  If you draw a million markers and line segments, you
> > are inevitably going to have a big postscript file, unless the
> > postscript backend somehow detects the fact that almost all of your
> > points are indistinguishable and therefore deletes most of them--and
> > this is really asking too much of a plotting backend, I think.  (An
> > alternative is to generate a pixel image and make the postscript from
> > that; this is what matlab does under some circumstances, but it can
> > result in big files of poor quality.)
>
> The problems with crashing applications do not occur, if only dots are
> printed. Furthermore, only if line lengths shrink to infinitesimal values,
> ghostscript keeps processing them with a CPU load of 100% and Gigabytes of
> RAM consumption. Even if this may be a ghostscript bug, I think that
> a postscript backend for scientific plotting should look for lines that
> have a length of less than epsilon (what might be 1/1e6 inch or
> something) and exclude them from the eps.

I spent quite a bit of effort streamlining eps file creation. Adding a step to 
compare each point with the last one written will add a lot of overhead in 
order to deal with a relatively rare case such as yours. There are lots of 
users who want mpl to run as fast as possible, so please try to understand 
that there has to be some tradeoffs. 
 
> > Finally, we dont include tiff previews in our eps files, so this is not a
> > bug.
>
> At least for me, including a tiff preview would really be beneficial.
> I did not want to call this behavior a bug, but please consider such an
> option.

I dont think we can consider this until we bring the file size down by 
improving the font handling. But you can submit a feature request at the 
sourceforge site, although a patch would be preferred.

> > Your options include: filter your points beforehand so you only plot
> > points that are distinct; or use a pixel-based format like png, which
> > keeps the file size under control.
>
> Unfortunately, this much easier in the proof of error that I sent
> you than in my actual problem, since I then have to create a copy
> of the data just for plotting.

Just so for the postscript backend.

Darren

> > I suggest upgrading to 0.87.3.
>
> However, I still do see no working Gentoo ebuild. Is there any out there?

You can find one at http://bugs.gentoo.org/show_bug.cgi?id=136429

Problem is that you'd have to get the whole gentooscience overlay, so, here's 
the matplotlib ebuild and the corresponding files. Just uncompress in 
$OVERLAY/dev-python, run ebuild matplotlib-0.87.4.ebuild digest, and emerge.
(You may wanna get the whole overlay anyway as you'll probably need some other 
packages, or you could just let me know offlist).

Word of advice: there've been some changes in the USE keywords, check them 
with emerge -pv first. The "wxwindows " is still buggy, but I was able to get 
a working installation with  USE="agg gtk tcltk" emerge -v matplotlib

Hi all:

> > When I use matplotlib for a scatter plot with both dots and connecting
> > lines, the exported eps file is huge, if the distances between many points
> > are small. I think of this as a bug, since no preview tiff is included in
> > the generated eps and a variety of text processing applications (including
> > OpenOffice) crash when I try to import the eps. Ghostscript takes forever,
> > too. Is there anything that I can do in order to export reasonable eps
> > files?
>
> I suggest upgrading to 0.87.3.

However, I still do see no working Gentoo ebuild. Is there any out there?

> The bigger problem is that each file format has basic characteristics
> and limitations.  If you draw a million markers and line segments, you
> are inevitably going to have a big postscript file, unless the
> postscript backend somehow detects the fact that almost all of your
> points are indistinguishable and therefore deletes most of them--and
> this is really asking too much of a plotting backend, I think.  (An
> alternative is to generate a pixel image and make the postscript from
> that; this is what matlab does under some circumstances, but it can
> result in big files of poor quality.)

The problems with crashing applications do not occur, if only dots are
printed. Furthermore, only if line lengths shrink to infinitesimal values,
ghostscript keeps processing them with a CPU load of 100% and Gigabytes of
RAM consumption. Even if this may be a ghostscript bug, I think that
a postscript backend for scientific plotting should look for lines that
have a length of less than epsilon (what might be 1/1e6 inch or
something) and exclude them from the eps. Looking for dots that lie close
together however surely would be too much to ask for but this does not
lead ghostscript, OpenOffice, etc. to fail. (Printers normally time out.)

> Finally, we dont include tiff previews in our eps files, so this is not a bug.

At least for me, including a tiff preview would really be beneficial.
I did not want to call this behavior a bug, but please consider such an
option.

> Your options include: filter your points beforehand so you only plot
> points that are distinct; or use a pixel-based format like png, which
> keeps the file size under control.

Unfortunately, this much easier in the proof of error that I sent
you than in my actual problem, since I then have to create a copy
of the data just for plotting.

Thus, for now I use png images but I still would prefer eps.

Thank you for all of your answers.

Martin

Hi,

why don't you try to remove the legend frame?

> self.axes.plot(x_value, y_value, 'k-',=20
>                label =3D labelLegend)
>=20
> self.axes.legend(loc =3D 'best', pad =3D 0.1)
> leg =3D self.axes.get_legend()

leg.draw_frame(False)

You won't have any problem with the legend box anymore.  but maybe, I=20
didn't understand what you want...

Benoit

> ltext =3D leg.get_texts()
> setp(ltext, fontsize=3D'x-small')
>=20
> -- Till Wagner=20
>=20
>=20
>=20
> --
> "Since man's natural instincts lead him to sin, all men are sinners;
> and all sinners go to hell.  If everyone goes to hell, then you will
> meet all your friends there. Heaven must be populated with some
> rather strange creatures if all they lived for was to go to a place
> where they can stump harps for eternity."- Anton Szandor LaVey
> -----------------------------------------------------------------------=
-
> Till Wagner <sac...@ya...>
>=20
>=20
> 	=09
> ___________________________________________________________=20
> Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
>=20
>=20
> -----------------------------------------------------------------------=
--
> Using Tomcat but need to do more? Need to support web services, securit=
y?
> Get stuff done quickly with pre-integrated technology to make your job =
easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geron=
imo
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=
=3D121642
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>=20
>=20

--=20
Benoit Donnet
Universit=E9 Pierre & Marie Curie (Paris VI)
Laboratoire LIP6 - R=E9seaux & Performances
8, rue du Capitaine Scott
75015 Paris
France
Phone: 00 33 (0)1 44 27 88 83
traceroute@home Project: http://trhome.sourceforge.net
Home Page: http://rp.lip6.fr/~donnet

Hi Darren,

> You can set legend.pad in your rc settings, or you
> can change the legend's pad property either when you
> create it or after the fact
> 
> l=legend(['ok'], pad=0.5)
> l.pad=1.5
> draw()

But pad seems to have mainly an effect on the space
between the text and the left and right border. My
problem is that the upper border is to close to the
text, so it is very hard to read. Also the legend has
to be as small as possible, because there are up to
seven graphs displayed and I need the space fo the
graphs. So I need a solution which increases the space
between text and upper border without having an effect
on the space between text and right/left border. 


> Would you post an example that exposes the problem?


Here is a code-snippnet right from my program:

self.axes.plot(x_value, y_value, 'k-', 
               label = labelLegend)

self.axes.legend(loc = 'best', pad = 0.1)
leg = self.axes.get_legend()
ltext = leg.get_texts()
setp(ltext, fontsize='x-small')

-- Till Wagner 



--
"Since man's natural instincts lead him to sin, all men are sinners;
and all sinners go to hell.  If everyone goes to hell, then you will
meet all your friends there. Heaven must be populated with some
rather strange creatures if all they lived for was to go to a place
where they can stump harps for eternity."- Anton Szandor LaVey
------------------------------------------------------------------------
Till Wagner <sac...@ya...>


		
___________________________________________________________ 
Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

On Thu, Jul 13, 2006 at 07:45:37AM -0500, John Hunter wrote:
> >>>>> "Eric" =3D=3D Eric Firing <ef...@ha...> writes:
>     Eric> To reply more directly to your proposal now that I have
>     Eric> thought about it more: although I see the logic in it, I
>     Eric> don't see much gain from your Nx2 idea; it not very hard to
>     Eric> simply write P.plot(z[:,0], z[:,1]).  Furthermore,
>=20
> And with the new .T attribute in numpy, you can do
>=20
>   from numpy import rand
>   X =3D rand(20,2)
>   plot(*X.T)

Except that rand is no longer in the numpy namespace :)

One reason why I don't like this syntax is that you can't use further
arguments or keywords easily:

def foo(a,b,c,keyw=3D"asd"): print a,b,c,keyw
x =3D ['1','2','3]
foo(*x) # works fine
foo(*x,"123") # breaks
foo(*x,keyw=3D"123") # breaks
foo(*x,**{'keyw'=3D"123"}) # works

But I guess you can always plot first and adjust parameters later.

Cheers
St=E9fan