2010/6/15 Olle Engdegård :
> The autoscaling might need a small fix for
>
> hist(rand(100),bins=20,histtype="step",log=1)
I just had a look at trunk (8623), and the lower y-limit looks good
now. The above problem was at rev 8475.
But an old, different, bug has turne
Hi,
The autoscaling might need a small fix for
hist(rand(100),bins=20,histtype="step",log=1)
Cheers,
Olle
--
ThinkGeek and WIRED's GeekDad team up for the Ultimate
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to th
Hi,
When "baseline" recently became the default for text(), it's no longer
possible to have two-line titles, title("First line\nSecond Line),
without adding va="bottom". It would be nice if title() somehow could
have "bottom" as default.
Cheers,
Olle
-
Hi,
Combining "stepfilled" with log scale sometimes gives inappropriate plots:
a=[4,4,4,4,4,4,4,4,4,4,4,5,5,5,5,5,5]
hist(a, range=(0,10), bins=10, histtype="stepfilled", log=True)
The problem is not restricted to the case here with more bins than unique
elements, but sometimes reducing the bin
On Thu, 19 Feb 2009, Michael Droettboom wrote:
> The drawing and then clipping is normal behavior. All of the backend formats
> have the ability to clip out arbitrary regions for drawing, so we take
> advantage of that rather than doing our own geometric clipping algorithm.
> The latter is a
works
here)
Mike
Michael Droettboom wrote:
I see it with 0.98.5.x, but not with SVN trunk. I'll look into this
further and see what I can determine.
Mike
Olle Engdegård wrote:
On Wed, 18 Feb 2009, Joshua Lippai wrote:
Interesting. I can't reproduce your result using either the
On Wed, 18 Feb 2009, Joshua Lippai wrote:
> Interesting. I can't reproduce your result using either the MacOSX or
> WXAgg backend. Which backend are you using, and does the problem
> persist if you use a different one?
Hmm, I see it in at least WXAgg, WX, GTKAgg ...
/Olle
--
Doing
from pylab import *
x=normal(10, size=1000)
hist(x)
xlim(0,10)
savefig("Image.svg")
and then importing the file to Inkscape and saving it there as a pdf gives
the attached result. The stuff right of x=10 is suddenly there. The
weirdest thing is that Inkscape _does not see this overspill
Hi,
I attach a trivial patch to pass a weight argument through hist() to
histogram().
Cheers,
Olle--- axes.py (revision 6329)
+++ axes.py (working copy)
@@ -6221,13 +6221,13 @@
def hist(self, x, bins=10, range=None, normed=False, cumulative=False,
bottom=None, histtype='b
On Fri, 20 Jun 2008, John Hunter wrote:
On Thu, Jun 19, 2008 at 11:52 AM, Olle Engdegård <[EMAIL PROTECTED]> wrote:
Here is a patch to add linestyles to patches.py. I have tried it with
unfilled step histograms (important for b/w print and colour blind people).
I'm happy to i
Here is a patch to add linestyles to patches.py. I have tried it with
unfilled step histograms (important for b/w print and colour blind
people).
What do you think?
Cheers,
OlleIndex: patches.py
===
--- patches.py (revision 5595
hist(histtype="step") worked fine in rev5412, but in the latest I get
>>> hist(randn(1000), histtype="step")
Traceback (most recent call last):
/.../
raise TypeError, 'There is no patch property "%s"'%key
TypeError: There is no patch property "closed"
Changing
closed = kwargs.get('closed',
> what do you mean by "range" parameter. What should this parameter actually
> do ?
>
Actually just pass it along to numpy.histogram(). I guess it just ignores
all data outside the range.
Cheers,
Olle
-
Check out the new
Hi,
Some more thoughts about hist():
A "range" parameter should be added and used in histogram()
A new histogram should get a new colour, just like plot() does
The "step" type should default to fill=False
Actually, personally I hardly ever use bar histograms at all, so if
step-mode (unfilled)
Hi,
I very much miss the 'l' shortcut for toggling log/lin y-scale in the
trunk! I use it a lot.
I suggest restoring it with something like
if self.get_yscale() is ("log" or "linear"):
self.toggle_log_lineary()
else: pass
I think most of time most people use log or linear scales.
The new
15 matches
Mail list logo
