> Subject: Re: [Matplotlib-users] x axis non-uniform labeling (KURT PETERS)
> From: smit...@fusion.gat.com
> Date: Tue, 1 Oct 2013 11:34:39 -0700
> CC: pmhob...@gmail.com; matplotlib-users@lists.sourceforge.net
> To: petersk...@msn.com
>
>
> On Oct 1, 2013, at 8:59AM, KURT PETERS wrote:
>
> >
>
On Oct 1, 2013, at 8:59AM, KURT PETERS wrote:
>
> REPLY:
>
>
> here's what SHOULD be happening
>
> | 0 1 5 9 13 18 21 24 25 28
> 3 | x
> |x x
> | x
On Tue, Oct 1, 2013 at 1:55 PM, KURT PETERS wrote:
>
>
> > Date: Tue, 1 Oct 2013 19:35:39 +0200
>
> > Subject: Re: [Matplotlib-users] x axis non-uniform labeling (KURT PETERS)
> > From: goyod...@gmail.com
> > To: petersk...@msn.com
> > CC: pmhob...@gmail.com; matplotlib-users@lists.sourceforge.ne
On Oct 1, 2013, at 11:01AM, Jody Klymak wrote:
>
> On Oct 1, 2013, at 10:55 AM, KURT PETERS wrote:
>
>> Goyo,
>> Thanks, the code below seems to work. The problem is that with
>> "REAL/actual" data, I have SO many data points that each point is now
>> labeled and it takes forever to rend
On Oct 1, 2013, at 10:55 AM, KURT PETERS wrote:
> Goyo,
> Thanks, the code below seems to work. The problem is that with
> "REAL/actual" data, I have SO many data points that each point is now labeled
> and it takes forever to render. And when it does render, I cannot read the
> axis bec
> Date: Tue, 1 Oct 2013 19:35:39 +0200
> Subject: Re: [Matplotlib-users] x axis non-uniform labeling (KURT PETERS)
> From: goyod...@gmail.com
> To: petersk...@msn.com
> CC: pmhob...@gmail.com; matplotlib-users@lists.sourceforge.net
>
> 2013/10/1 KURT PETERS :
> > here's what SHOULD be happening
2013/10/1 KURT PETERS :
> here's what SHOULD be happening
>
> | 0 1 5 9 13 18 21 24 25 28
> 3 | x
> |x x
> | xx
> | x x
> -1|_x__x_
>12
It's not really clear to me what you're trying to do. But the rounding of the
axes limits is an expected behavior of matplotlib. You can set them manually if
you like. Also, I think this achieves what you want and is much simpler.
import numpy as npimport matplotlib.pyplot as
pltxdat=np.arange(
On Mon, Sep 30, 2013 at 4:50 PM, KURT PETERS wrote:
> That doesn't seem to fix it. What I'm expecting is at the top, 28 should
> correspond to the value -2. Instead it puts a 30 there.
> Kurt
>
>
It's not really clear to me what you're trying to do. But the rounding of
the axes limits is an ex
