matplotlib-users Mailing List for matplotlib (Page 7)

>>>>> "Fernando" == Fernando Perez <Fer...@co...> writes:

    Fernando> Basically my question is: does the font.latex.package
    Fernando> setting actually do _anything_?  Or am I using it
    Fernando> incorrectly?

Try flushine the cache ~/.matplotlib/tex.cache/

I didn't look, but we may not be including the latex header in the
font caching hash string.

JDH

Hi all,

I'm wondering if it's really possible to use other latex font packages.  I 
just updated to CVS mpl, dvipng 1.7 and ghostscript 8.50-gpl to make sure I 
was fully current.  My tex-related settings are:

text.usetex         : True
text.tex.engine     : latex

And yet, I can set:

font.latex.package  : foobar

or anything in 'foobar', and there is absolutely no change in the resulting 
plots.  My goal is to be able to use the latex helvetica fonts, but setting 
this to 'helvetica', doesn't work.  I've also tried 'times', 'pslatex' and 
other valid latex packages, to no avail (meaning, titles and labels continue 
using ComputerModern fonts).

Basically my question is: does the font.latex.package setting actually do 
_anything_?  Or am I using it incorrectly?

Any help appreciated...

f

I'd like to plot a large number of points (say 10**6 or 10**7) with
different colours.  The colours will not naturally be parametrized by
a single float, but rather the rgb components will all vary
independently, so I don't think I can use a colormap.  I've read the
tutorial, FAQ and skimmed the user's guide, and the only solution I've
found is to issue a separate

  plot([x], [y], '.', markeredgecolor=(r,g,b))

for each data point.  But this appears to use huge amounts of memory
and be very slow.

I thought about using an image, but my points don't naturally fall on
a grid, and the plots will typically fill only 20 to 30% of the
canvas, so an image might not be best.  

Various thoughts:

1) It would be nice if the above could be made fast, since it is
almost the first thing one might try, especially if one is generating
the points and the colours on the fly.  (I say "almost" because it
wasn't obvious that I had to use markeredgecolor rather than
markercolor or just color.)

2) Alternatively, if I could specify an array of colors of the
same length as the xdata and ydata arrays, that would work for me,
but this doesn't seem to be supported currently.

If I ignore the colors, and plot my data using one (or just a few)
plot commands with marker '.', the speed is reasonable.

3) Scatter plots are close, but currently only allow a colormap
indexed by a single float.  I'm also concerned about efficiency,
since every point seems to be plotted as a polygon, but I just 
want small dots.

4) I could do like scatter does and use a collection of polygons.
I might try this, but am worried about plotting that many polygons.

Anything else I haven't thought of?

Dan

Hi

With MPL 0.86.1:

plot([1,2,3]); xlabel("lala")

produces the xlabel on the leftmost side of the x-axis instead of in the 
center. Also

plot([1,2,3]); xlabel("lala", verticalalignment='center', 
horizontalalignment='center')

changes nothing. And even trying to put the label on the rightmost side

plot([1,2,3]); xlabel("lala", verticalalignment='center', 
horizontalalignment='right')

changes nothing.

I get this with GTKAgg and TkAgg. I found nothing regarding this problem
in my matplotlibrc (which is the one found in .../matplotlob/mpl-data) 
but the xxxalignment statements should override this anyway.

Does anyone have an idea?

cheers,
steve

-- 
"People like Blood Sausage too. People are Morons!" -- Phil Connors, 
Groundhog Day

This problem was more complicated than originally thought, but it is
working in cvs now.  I updated basemap and matplotlib to express the
shared namespace matplotlib.toolkits.  Now you should be able to use
matplotlib and basemap as separate eggs and all should work as
expected.

On 1/18/06, Charlie Moad <cw...@gm...> wrote:
> We haven't put support in yet, but it is very easy to do.  I will add
> this to cvs very soon.  For now:
>
> Edit basemap's setup.py and replace "from distutils.core import setup"
> with "from setuptools import setup".
>
> In BOTH mpl's and basemap's setup.py file add this option to the setup
> method, "namespace_packages =3D 'matplotlib.toolkits'".
>
> Both mpl and basemap should be installed as eggs.  The namespace is
> how setuptools know separate packages share... a namespace.
>
> Let us know if you run into problems.
>
> - Charlie
>
> On 1/18/06, Tom Loredo <lo...@as...> wrote:
> >
> > Hi folks,
> >
> > I recently installed setuptools, and now whenever I build mpl
> > (I'm using 0.86), it gets installed in site-packages as an egg.
> > Fine, as far as use within python is concerned it works just
> > as before.  But I just tried to install basemap, and the
> > installer puts it in site-packages in a new matplotlib directory
> > (i.e., not in the matplotlib...egg directory).  If I try
> > to use it, I get an import error because it's not found
> > in the egg (which must the first place Python finds mpl).
> >
> > How can I properly install an mpl toolkit in the egg scenario;
> > or if there is no easy way, how can I "turn off" eggs so when
> > I build mpl it makes a normal install.  Just deleting the
> > build directory (and the egg from site-packages) and rebuilding
> > from scratch didn't do it.
> >
> > Thanks,
> > Tom
> >
> >
> > -------------------------------------------------
> > This mail sent through IMP: http://horde.org/imp/
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log =
files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> > _______________________________________________
> > Matplotlib-users mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >
>

There's not enough information here for me to help you. Try setting verbose to 
helpful to look for any error messages reported by tex, gs, etc during eps 
creation.

On Friday 20 January 2006 12:11, Vidar Gundersen wrote:
> this occurred on my Mac OS X 10.4 after
> installing matplotlib-0.86.1, when i try
> to convert .eps created by mpl to pdf:
>
> $ epstopdf plot.eps
>
> Error: /invalidfont in -dict-
> Operand stack:
>    LucidaGrande   --dict:11/14(L)--   Font   LucidaGrande  
> --dict:11/14(L)--   LucidaGrande Execution stack:
>    %interp_exit   .runexec2   --nostringval--   --nostringval--  
> --nostringval--   2   %stopped_push   --nostringval--   --nostringval--  
> --nostringval--   false   1   %stopped_push   1   3   %oparray_pop   1   3 
>  %oparray_pop   --nostringval--   1   3   %oparray_pop   1   3  
> %oparray_pop   .runexec2   --nostringval--   --nostringval--  
> --nostringval--   2   %stopped_push   --nostringval--   2   4  
> %oparray_pop   3   4   %oparray_pop   --nostringval--   --nostringval--  
> --nostringval--   7   5   %oparray_pop   --nostringval--   7   5  
> %oparray_pop Dictionary stack:
>    --dict:1123/1686(ro)(G)--   --dict:0/20(G)--   --dict:75/200(L)--  
> --dict:6/7(L)--   --dict:17/17(ro)(G)-- Current allocation mode is local
> Last OS error: 2
> AFPL Ghostscript 8.51: Unrecoverable error, exit code 1
> Broken pipe
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

-- 
Darren S. Dale, Ph.D.
Cornell High Energy Synchrotron Source
Cornell University
200L Wilson Lab
Rt. 366 & Pine Tree Road
Ithaca, NY 14853

dd...@co...
office: (607) 255-9894
fax: (607) 255-9001

this occurred on my Mac OS X 10.4 after
installing matplotlib-0.86.1, when i try
to convert .eps created by mpl to pdf:

$ epstopdf plot.eps 

Error: /invalidfont in -dict-
Operand stack:
   LucidaGrande   --dict:11/14(L)--   Font   LucidaGrande   --dict:11/14(L)--   LucidaGrande
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   1   3   %oparray_pop   1   3   %oparray_pop   --nostringval--   1   3   %oparray_pop   1   3   %oparray_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   2   4   %oparray_pop   3   4   %oparray_pop   --nostringval--   --nostringval--   --nostringval--   7   5   %oparray_pop   --nostringval--   7   5   %oparray_pop
Dictionary stack:
   --dict:1123/1686(ro)(G)--   --dict:0/20(G)--   --dict:75/200(L)--   --dict:6/7(L)--   --dict:17/17(ro)(G)--
Current allocation mode is local
Last OS error: 2
AFPL Ghostscript 8.51: Unrecoverable error, exit code 1
Broken pipe

Hi Nils,

On Friday 20 January 2006 07:28, Nils Wagner wrote:
> >>> import matplotlib
>
> /usr/lib64/python2.4/site-packages/matplotlib/__init__.py:698:
> UserWarning: matplotlibrc text.usetex can not be be used with ps backend
> unless ghostscript-8.16 or later is available on your system
>   warnings.warn('matplotlibrc text.usetex can not \
>
> >>> matplotlib.__version__
>
> '0.86.2cvs'
>
> gv -v
> gv 3.5.8
>
> Do I need an update ?

gv is not the same as ghostscript. Try gs -v. 

Maybe I got a little overzealous with the version requirement, but there have 
been lots of posts to this mailing list complaining about bad boundingboxes 
in postscript files with the usetex option, and all of them have been solved 
by updating to gnu-ghostscript-8.16. If you find this requirement too 
restrictive, please let me know and I will consider ways to alter mpl 
(perhaps raise a warning instead of an error.)

Darren

On Jan 19, 2006, at 9:33 PM, John Hunter wrote:

>>>>>> "Paul" == Paul Kienzle <pki...@us...> writes:
>
>     Paul> John, Alex added facets to pcolormesh today.  Eventually we
>     Paul> would like pcolormesh to be a drop-in replacement for
>     Paul> pcolor, only faster.  We are also working on performance
>     Paul> improvements.
>
>     Paul> The pcolormesh function can easily identify rectilinear
>     Paul> grids (e.g., when given x,y as vector rather than array) and
>     Paul> use either NonUniformImage or imshow as appropriate.  The
>     Paul> facets should be easy enough to draw on top if needed,
>     Paul> though obviously the result will be slower.
>
> One might be able to add the faceting as an image overlay, or blend
> the faceting into the existing image, which would solve the
> performance problem.  The more we can do with images the better, since
> we get interpolation and superior performance.  Ideally, we would have
> a single rectilinear image object that supports interpolation,
> nonuniform (but rectilinear) griding, and optional faceting.  This
> would cover every case except non-rectangular quadrilateral meshes,
> which is where your and Alex's recent contribution would kick in.

Another common case is a skewed mesh, which could be implemented
as a simple image transformation.

- Paul

>>> import matplotlib
/usr/lib64/python2.4/site-packages/matplotlib/__init__.py:698:
UserWarning: matplotlibrc text.usetex can not be be used with ps backend
unless ghostscript-8.16 or later is available on your system
  warnings.warn('matplotlibrc text.usetex can not \
>>> matplotlib.__version__
'0.86.2cvs'

gv -v
gv 3.5.8

Do I need an update ?

Nils

Hi Ryan,

I opened your subplottest.pdf with both kpdf and adobe reader, and the figure 
looked fine with each.

Darren
 

On Friday 20 January 2006 12:39 am, Ryan Krauss wrote:
> I am having a slight problem with the ps backend and printing the
> figure after including it in a LaTeX document.  If I run the attached
> script psbackend_test.py, it generates a fairly simple semilogx
> subplot(212) plot.  I generate plots of this format a lot.  This
> script saves test.eps (the usetex option is true in my matplotlibrc).
> If I run epstopdf on just the figure and open it up in acroread and
> print just the figure, it prints correctly.  But if I include the
> figure in a LaTeX document, the frame around the lower sub-figure does
> not print.  Can anyone else reproduce this behavior and does anyone
> know how to fix it?
>
> I printed the LaTeX file from acroread generated using pdflatex and
> latex->dvips->ps2pdf with the same lack of frame.
>
> Here are some other parameters from my matplotlibrc that may help
> understand the problem:
> text.color          : black
> text.usetex         : True  # use tex/latex for all text handling.
> See http://matplotlib.sf.net/matplotlib.texmanager.html
> text.tex.engine     : latex  # tex is faster, but latex is required to
> use special font packages
>
> # ps backend params
> ps.papersize      : letter   # executive, letter, legal, ledger,
> A0-A10, B0-B6, C0-C6
> ps.useafm         : False    # use of afm fonts -- breaks mathtext but
> results in small files
> #ps.usedistiller   : False    # can be: None, ghostscript or xpdf
> ps.usedistiller   : xpdf #False    # can be: None, ghostscript or xpdf
>                                           # Experimental: may produce
> smaller files.
>                                           # xpdf intended for
> production of publication quality files,
>                                           # but requires ghostscript,
> xpdf and ps2eps
> ps.distiller.res  : 6000      # dpi
>
> Thanks,
>
> Ryan

-- 
Darren S. Dale, Ph.D.
dd...@co...

I am having a slight problem with the ps backend and printing the
figure after including it in a LaTeX document.  If I run the attached
script psbackend_test.py, it generates a fairly simple semilogx
subplot(212) plot.  I generate plots of this format a lot.  This
script saves test.eps (the usetex option is true in my matplotlibrc).=20
If I run epstopdf on just the figure and open it up in acroread and
print just the figure, it prints correctly.  But if I include the
figure in a LaTeX document, the frame around the lower sub-figure does
not print.  Can anyone else reproduce this behavior and does anyone
know how to fix it?

I printed the LaTeX file from acroread generated using pdflatex and
latex->dvips->ps2pdf with the same lack of frame.

Here are some other parameters from my matplotlibrc that may help
understand the problem:
text.color          : black
text.usetex         : True  # use tex/latex for all text handling.=20
See http://matplotlib.sf.net/matplotlib.texmanager.html
text.tex.engine     : latex  # tex is faster, but latex is required to
use special font packages

# ps backend params
ps.papersize      : letter   # executive, letter, legal, ledger,
A0-A10, B0-B6, C0-C6
ps.useafm         : False    # use of afm fonts -- breaks mathtext but
results in small files
#ps.usedistiller   : False    # can be: None, ghostscript or xpdf
ps.usedistiller   : xpdf #False    # can be: None, ghostscript or xpdf
                                          # Experimental: may produce
smaller files.
                                          # xpdf intended for
production of publication quality files,
                                          # but requires ghostscript,
xpdf and ps2eps
ps.distiller.res  : 6000      # dpi

Thanks,

Ryan

>>>>> "Paul" == Paul Kienzle <pki...@us...> writes:

    Paul> John, Alex added facets to pcolormesh today.  Eventually we
    Paul> would like pcolormesh to be a drop-in replacement for
    Paul> pcolor, only faster.  We are also working on performance
    Paul> improvements.

    Paul> The pcolormesh function can easily identify rectilinear
    Paul> grids (e.g., when given x,y as vector rather than array) and
    Paul> use either NonUniformImage or imshow as appropriate.  The
    Paul> facets should be easy enough to draw on top if needed,
    Paul> though obviously the result will be slower.

One might be able to add the faceting as an image overlay, or blend
the faceting into the existing image, which would solve the
performance problem.  The more we can do with images the better, since
we get interpolation and superior performance.  Ideally, we would have
a single rectilinear image object that supports interpolation,
nonuniform (but rectilinear) griding, and optional faceting.  This
would cover every case except non-rectangular quadrilateral meshes,
which is where your and Alex's recent contribution would kick in.  The
image machinery is almost there already: all that is lacking is a
faceting option and a consistent interface.

    Paul> In the end we will have two functions: pcolor and imshow,
    Paul> with pcolor accepting x,y,z and imshow only z.

This looks like the right approach -- in the end it will be nice to
reduce the clutter of too many alternatives.  The only problem with
switching the underlying object (Image vs NonuniformImage vs QuadMesh
vs PolygonCollection) is that it would be difficult to deal with the
return object in a consistent way.  If we had the object described
above, we might imagine living with just two functions: imshow on
steroids that handles all rectilinear cases, and quadmesh for the
others.  pcolor would then simply be a thin interface to imshow for
matlab with different kwargs for matlab compatibility.

Thanks for your help; looking forward to the updates...

JDH

John,

Alex added facets to pcolormesh today.  Eventually we would
like pcolormesh to be a drop-in replacement for pcolor, only
faster.  We are also working on performance improvements.

The pcolormesh function can easily identify rectilinear
grids (e.g., when given x,y as vector rather than array)
and use either NonUniformImage or imshow as appropriate.
The facets should be easy enough to draw on top if needed,
though obviously the result will be slower.

In the end we will have two functions: pcolor and imshow,
with pcolor accepting x,y,z and imshow only z.

- Paul

On Jan 19, 2006, at 6:58 PM, John Hunter wrote:

>
> Alex Mont and Paul Kienzle just contributed a patch for more efficient
> handling of quadrilateral meshes, which supports non-rectangular
> meshes.
>
>   http://peds-pc311.bsd.uchicago.edu/misc/quadmesh.png
>
> Right now this is *Agg only, but I think/hope they will be adding
> support for other backends in the near future.
>
> Their original patch with detailed description can be found here
>
>    
> https://sourceforge.net/tracker/index.php? 
> func=detail&aid=1409190&group_id=80706&atid=560722
>
> and I just committed this to CVS.
>
> Combined with Nicholas Young's nonuniform image, this provides some
> new alternatives to those needing efficient pseudo-color plots (see
> http://www.nabble.com/interpolated-pcolor-image-t659211.html for a
> NonuniformImage example)
>
> Thus we now have
>
> pcolor - rectangular, possibly nonuniform mesh with optional facets.
>          Slow for large grids.  No interpolation.
>
> pcolormesh - Arbitrary quadrilateral meshes, agg only, faster than
>           pcolor and more efficient in memory.  No interpolation.
>
> imshow - Pseudocolor plots with interpolation but no faceting.  Faster
>       than pcolor or pcolormesh
>
> NonUniformImage - uses image machinery but supports nonuniform,
>    rectangular meshes with interpolation and no faceting.  Again,
>    faster than pcolor or pcolormesh.
>
> Given the bewildering array of options, it would be nice to have a
> wiki entry with examples showing when and how to use these various
> classes and functions.  Volunteers welcome; a good starting point
> would be this email and the example from the nonuniform image link
> above and the discussion by Alex and Paul on the link at the
> sourceforge site.
>
> Here is a quadrilateral mesh example, which is now
> examples/quadmesh_demo.py in CVS.
>
> from matplotlib.mlab import linspace, meshgrid
> import matplotlib.numerix as nx
> from pylab import figure,show
>
> n = 56
> x = linspace(-1.5,1.5,n)
> X,Y = meshgrid(x,x);
> Qx = nx.cos(Y) - nx.cos(X)
> Qz = nx.sin(Y) + nx.sin(X)
> Qx = (Qx + 1.1)
> Z = nx.sqrt(X**2 + Y**2)/5;
> Z = (Z - nx.mlab.amin(Z)) / (nx.mlab.amax(Z) - nx.mlab.amin(Z))
>
> fig = figure()
> ax = fig.add_subplot(111)
> ax.pcolormesh(Qx,Qz,Z)
> show()
>
>

Alex Mont and Paul Kienzle just contributed a patch for more efficient
handling of quadrilateral meshes, which supports non-rectangular
meshes.

  http://peds-pc311.bsd.uchicago.edu/misc/quadmesh.png

Right now this is *Agg only, but I think/hope they will be adding
support for other backends in the near future.

Their original patch with detailed description can be found here

  https://sourceforge.net/tracker/index.php?func=detail&aid=1409190&group_id=80706&atid=560722

and I just committed this to CVS.

Combined with Nicholas Young's nonuniform image, this provides some
new alternatives to those needing efficient pseudo-color plots (see
http://www.nabble.com/interpolated-pcolor-image-t659211.html for a
NonuniformImage example)

Thus we now have

pcolor - rectangular, possibly nonuniform mesh with optional facets.
         Slow for large grids.  No interpolation.

pcolormesh - Arbitrary quadrilateral meshes, agg only, faster than
          pcolor and more efficient in memory.  No interpolation.

imshow - Pseudocolor plots with interpolation but no faceting.  Faster
      than pcolor or pcolormesh

NonUniformImage - uses image machinery but supports nonuniform,
   rectangular meshes with interpolation and no faceting.  Again,
   faster than pcolor or pcolormesh.

Given the bewildering array of options, it would be nice to have a
wiki entry with examples showing when and how to use these various
classes and functions.  Volunteers welcome; a good starting point
would be this email and the example from the nonuniform image link
above and the discussion by Alex and Paul on the link at the
sourceforge site.

Here is a quadrilateral mesh example, which is now
examples/quadmesh_demo.py in CVS.

from matplotlib.mlab import linspace, meshgrid
import matplotlib.numerix as nx
from pylab import figure,show

n = 56
x = linspace(-1.5,1.5,n)
X,Y = meshgrid(x,x);
Qx = nx.cos(Y) - nx.cos(X)
Qz = nx.sin(Y) + nx.sin(X)
Qx = (Qx + 1.1)
Z = nx.sqrt(X**2 + Y**2)/5;
Z = (Z - nx.mlab.amin(Z)) / (nx.mlab.amax(Z) - nx.mlab.amin(Z))

fig = figure()
ax = fig.add_subplot(111)
ax.pcolormesh(Qx,Qz,Z)
show()

Hi,

Thanks for replying.

On Thu, 19 Jan 2006 21:45:11 +0200, Jouni K Seppanen
<jk...@ik...> wrote:

> Faheem Mitha <fa...@em...> writes:
>
>> The current boxplot function in matplotlib does not appear to support
>> labels for individual boxplots, if there are several on the same plot.
>
> Do you mean the tick labels on the x axis, or something else?

Yes, I mean the tick labels on the x axis.

>> I know I can manually add labels, but would prefer not to do so, since
>> I am trying to automate the process of graph creation as much as
>> possible.
>
> Perhaps I'm not getting what you mean by "automate", but you'll be
> writing a script anyway and can easily add the labels after plotting, eg
>
>   boxplot(data)
>   setp(gca(), 'xticklabels', ['first', 'second', 'third'])

Yes, using xticklabels works. I can do

***********************************************************
from pylab import *
from matplotlib.backends.backend_ps import FigureCanvasPS

fig = Figure()
fig.set_figwidth(6)
fig.set_figheight(6.2)
canvas = FigureCanvasPS(fig)
ax = fig.add_subplot(111)
ax.boxplot([1, 2, 3, 4, 5, 6, 7, 8])
ax.set_xticklabels(["test"])
ax.set_xlabel("Test boxplot,")
canvas.print_figure("test.eps")
***********************************************************

Thanks.                                             Faheem,

>>>>> "Ryan" == Ryan Krauss <rya...@gm...> writes:

    Ryan> Try this: in your /etc/apt/sources.list and then add

    Ryan> deb http://peds-pc311.bsd.uchicago.edu binary/

    Ryan> and do

    >> sudo apt-get update sudo apt-get python-matplotlib-jdh

You might give these a try now -- I just updated the debs to
matplotlib-0.86.2cvs with numpy 0.9.2 support.

JDH

Eric Emsellem wrote:
> Ok thanks. (in fact the cvs version seemed to have solved it for some reason)
> 
> I did that only because when doing "help(arange)" it gave me that dependency and
> I wanted to be sure to use the right one here. So why is Ipython giving me that
> instead of the most direct one?

arange is defined in the module numpy.core.multiarray. That information is
stored in the builtin_function_or_method object itself. It can't know that it is
being imported into the root numpy namespace or anywhere else. Consequently, the
help() function can't know that you are accessing it as "from numpy import *;
help(arange)", and only gives you the information that it knows.

-- 
Robert Kern
rob...@gm...

"In the fields of hell where the grass grows high
 Are the graves of dreams allowed to die."
  -- Richard Harter

Eric Emsellem wrote:
> Ok thanks. (in fact the cvs version seemed to have solved it for some reason)
> 
> I did that only because when doing "help(arange)" it gave me that dependency and
> I wanted to be sure to use the right one here. So why is Ipython giving me that
> instead of the most direct one?

Because IPython doesn't read mailing lists or manuals :)  It only shows what 
the inspect.get* routines return, and that's where arange _lives_ at the 
internal, implementation level.  IPython tries really, really hard to make 
your life easy, but there's a limit to its powers :)

Cheers,

f

Ok thanks. (in fact the cvs version seemed to have solved it for some reason)

I did that only because when doing "help(arange)" it gave me that dependency and
I wanted to be sure to use the right one here. So why is Ipython giving me that
instead of the most direct one?

thanks again
Eric

> I agree.  numpy.core.multiarray is the base object for arrays, but it
> not really supposed to be used directly.  All arrays should have a
> dtypechar property, and since that was the source of your original
> error, I am even more sure you shouldn't use it directly.  Chris's
> suggestions are the correct approach.
>
> On 1/19/06, Christopher Barker <Chr...@no...> wrote:
> > Eric Emsellem wrote:
> >
> > > I have switched to numpy (I was using numarray before) with matplotlib.
> >
> > > x = numpy.core.multiarray.arange(0.,6.,1.)
> >
> > Why not use:
> >
> > x = numpy.arange(0.,6.,1.)
> >
> > Or maybe better with MPL:
> >
> > import matplotlib.numerix as nx
> > x = nx.arange(0.,6.,1.)
> >
> > after setting numerix appropriately in .matplotlibrc.
> >
> > -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...
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> > for problems?  Stop!  Download the new AJAX search engine that makes
> > searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> > _______________________________________________
> > Matplotlib-users mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >
>


-- 


--------------------------------------------------------------------------
Ce message a été envoyé depuis le webmail IMP (Internet Messaging Program)

Faheem Mitha <fa...@em...> writes:

> The current boxplot function in matplotlib does not appear to support
> labels for individual boxplots, if there are several on the same plot.

Do you mean the tick labels on the x axis, or something else?

> I know I can manually add labels, but would prefer not to do so, since
> I am trying to automate the process of graph creation as much as
> possible.

Perhaps I'm not getting what you mean by "automate", but you'll be
writing a script anyway and can easily add the labels after plotting, eg

  boxplot(data)
  setp(gca(), 'xticklabels', ['first', 'second', 'third'])

-- 
Jouni

Charlie Moad wrote:
> I agree.  numpy.core.multiarray is the base object for arrays, but it
> not really supposed to be used directly.  All arrays should have a
> dtypechar property, and since that was the source of your original
> error, I am even more sure you shouldn't use it directly.

As Darren noted, A.dtypechar was recently changed to A.dtype.char in numpy, and
matplotlib in CVS now reflects that change.

-- 
Robert Kern
rob...@gm...

"In the fields of hell where the grass grows high
 Are the graves of dreams allowed to die."
  -- Richard Harter

I agree.  numpy.core.multiarray is the base object for arrays, but it
not really supposed to be used directly.  All arrays should have a
dtypechar property, and since that was the source of your original
error, I am even more sure you shouldn't use it directly.  Chris's
suggestions are the correct approach.

On 1/19/06, Christopher Barker <Chr...@no...> wrote:
> Eric Emsellem wrote:
>
> > I have switched to numpy (I was using numarray before) with matplotlib.
>
> > x =3D numpy.core.multiarray.arange(0.,6.,1.)
>
> Why not use:
>
> x =3D numpy.arange(0.,6.,1.)
>
> Or maybe better with MPL:
>
> import matplotlib.numerix as nx
> x =3D nx.arange(0.,6.,1.)
>
> after setting numerix appropriately in .matplotlibrc.
>
> -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...
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D103432&bid=3D230486&dat=
=3D121642
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Eric Emsellem wrote:

> I have switched to numpy (I was using numarray before) with matplotlib.

> x = numpy.core.multiarray.arange(0.,6.,1.)

Why not use:

x = numpy.arange(0.,6.,1.)

Or maybe better with MPL:

import matplotlib.numerix as nx
x = nx.arange(0.,6.,1.)

after setting numerix appropriately in .matplotlibrc.

-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...

Hi
it seems that a problem with the tcl headers is still there.

When I am downloading the cvs version of matplotlib I STILL have to do 
the following to install it
(I thought the problem was solved?)

# add one line in setupext.py:

        o.tcl_inc="/usr/include/"

# before
        if not os.path.exists(o.tcl_inc):
            print 'cannot find tcl/tk headers. giving up.'
            sys.exit()
    return o


cheers
Eric

-- 
===============================================================
Observatoire de Lyon                 ems...@ob...
9 av. Charles-Andre                      tel: +33 4 78 86 83 84
69561 Saint-Genis Laval Cedex            fax: +33 4 78 86 83 86
France               http://www-obs.univ-lyon1.fr/eric.emsellem
===============================================================