Suresh,
This is baffling, and particularly annoying for someone just starting
out with mpl. I don't think there is any problem with the barchart
code--the demo works for me with numarray--and I don't see anything
obvious in the traceback. Are your matplotlib and numarray both from
Mandriva pa
This release is compiled against numpy-1.0 final. The binaries are
fresh on sourceforge, so they may take some time to propagate to the
mirrors.
http://cheeseshop.python.org/pypi/matplotlib/
http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=82474
Note: There is a compile err
Suresh,
That example works fine for me, using python 2.4.3, mpl 0.87.5 under
windows, and wxPython 2.6.3.3, with backend: WxAgg, numerix: numarray
(1.5.1), interactive: False, and axes.hold: True in the RC file.
I'd recommend going with numpy instead of numarray, if you can. See
http://numeric
And yes my numerix is set to numarray as default:
$ python barchart_demo.py --verbose-helpful
...
numerix numarray 1.5.2
...
Thanks,
Suresh
On Thu, 26 Oct 2006, Suresh Pillai wrote:
> The exception I posted is being thrown by numarray, so it is definitely
> being used.
>
> As I stated, it was
Hello Everybody,
I use the usual scipy + numpy + matplotlib combination for my daily
work. Unfortunately after switching to Fedora Core 6 (from FC5) I am
unable to compile matplotlib 0.87.6 on my system.
The steps involved so far where:
* First building numpy 1.0 final (installing blas,lapack,a
The exception I posted is being thrown by numarray, so it is definitely
being used.
As I stated, it was thrown while executing one of the examples provided
with the matplotlib package:
#!/usr/bin/env python
# barchart_demo.py
# a bar plot with errorbars
from pylab import *
N = 5
menMeans = (20
> "stochashtic" == stochashtic <[EMAIL PROTECTED]> writes:
stochashtic> I am brand spanking new to matplotlib and using
stochashtic> python for scientific computing (amazing product;
stochashtic> can't believe I didn't know about it before.) and
stochashtic> would appreciate
I receive an error when trying to plot barcharts. To confirm it was
nothing to do with my code, I tried running one of the demos provided and
received the same error:
$ python barchart_demo.py
Traceback (most recent call last):
File "barchart_demo.py", line 11, in ?
p1 = bar(ind, menMea
> "Karl" == Karl Guertin <[EMAIL PROTECTED]> writes:
Karl> I have a very customized matplotlibrc for rendering charts
Karl> for web pages. The biggest change is that I render
Karl> everything white on black by default. This has worked fine
Karl> up through 0.87.5 (the last rele
I have a very customized matplotlibrc for rendering charts for web
pages. The biggest change is that I render everything white on black
by default. This has worked fine up through 0.87.5 (the last release I
grabbed) but in 0.87.7, the ticks on the axes are black (the axes
color is white). Am I miss
> "David" == David Huard <[EMAIL PROTECTED]> writes:
David> Hi, is there a limit to the number of times one can call
David> ax.plot(x,y) ?
No, but if you are making a lot of them, say over 100, then
performance will start to suffer, and you may be better off with a
LineCollection. pl
On 26/10/06, Christian Meesters <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm producing eps files using matplotlib (current version) on a linux box with
> SuSE 10.0. Whenever I view those files with a standard viewer on that machine
> or try to embed it in a latex document there is no problem.
>
> Now I
Hi,
I'm producing eps files using matplotlib (current version) on a linux box with
SuSE 10.0. Whenever I view those files with a standard viewer on that machine
or try to embed it in a latex document there is no problem.
Now I've copied these files on a Windows machine and I opened them in Adob
Hi Derek,
yes you can, because you've got an axes instance:
freq, axe= windrose.windplot( ...
setp(axe.thetagridlabels,fontsize=16) #for directions
setp(axe.rgridlabels,fontsize=10) #for values
I want to change how windrose is called and controled, like all others
matplotlib graphs. Maybe in 0.6
2006/10/25, Darren Dale <[EMAIL PROTECTED]>:
> Could this be a data type issue?
>
> from numpy import arange
> arange(120, 130, dtype=Int8)
>
> Out: array([ 120, 121, 122, 123, 124, 125, 126, 127, -128, -127],
> dtype=int8)
>
I will have to check this, but I do not think that is the problem
15 matches
Mail list logo
