Re: [Matplotlib-users] type error with python 3.2 and version 1.1.1 of matplotlib (numpy error)

[Eric Firing]

On 2012/09/05 6:17 PM, Paul Tremblay wrote:
> Hmm. I found that mpl handled my datetime objects just fine:

Right, mpl has handled python datetime objects for a long time, but the 
numpy array with a datetime dtype is a new and different object, and it 
will take a bit of work to support it properly.

Eric

>
> # put the weeks on the x axis
> # dates are datetime.datetime
> ax.plot(dates, defects)
> ax.xaxis.set_major_formatter(
>  matplotlib.dates.DateFormatter('%W'))
>
> # create an invisible line in order to
> # create a secondary x axis below
> # the first axis, which just has the month(s)
> newax = fig.add_axes(ax.get_position())
> newax.spines['bottom'].set_position(('outward', 25))
> newax.patch.set_visible(False)
> newax.yaxis.set_visible(False)
> # months are also datetime. However, I filtered out
> # all dates except the first date for each month
> newax.plot_date(months, y,  visible=False)
> newax.xaxis.set_major_locator(
>  matplotlib.dates.MonthLocator()
> )
> newax.xaxis.set_major_formatter(
>  matplotlib.dates.DateFormatter('%b')
> )
>
> On Thu, Sep 6, 2012 at 12:02 AM, Eric Firing  > wrote:
>
> On 2012/09/05 4:04 PM, Paul Tremblay wrote:
>  > I am using numpy 1.7, which I built myself (python3 setup.py
> build). I
>  > had a chance to look a bit deeper into matplotlib, which in turn
> forced
>  > me to learn a bit of numpy, and now I see that it probably makes more
>  > sense to use numpy arrays for my data. Since the default for an
> array is
>  > a float, most users won't encounter the problems I did, but a
> warning in
>  > a FAQ might solve a few headaches, regardless of how the developers
>  > decided to go.
>
> Paul,
>
> numpy 1.7 has a new datetime dtype which probably would be good for your
> use--except that mpl doesn't support it yet.  That will be a project for
> mpl v1.3.
>
> Eric
>
>  >
>  > Thanks for your help.
>  >
>  > Paul
>  >
>  > On Tue, Sep 4, 2012 at 3:09 PM, Benjamin Root  
>  > >> wrote:
>  >
>  >
>  >
>  > On Tue, Sep 4, 2012 at 2:20 PM, Paul Tremblay
>  > mailto:paulhtremb...@gmail.com>
> >>
> wrote:
>  >
>  >
>  > The following Python code:
>  >
>  >  >>ax.fill_between(dates, lower, upper, facecolor='gray',
> alpha=0.5)
>  >
>  > Produces this error with Python 3.2:
>  >
>  > Traceback (most recent call last):
>  >File "scripts/audit_reports_weekly.py", line 150, in
> 
>  >  ax.fill_between(dates, lower, upper, facecolor='gray',
>  > alpha=0.5)
>  >File
>  >
> 
> "/home/local/ANT/ptrembl/.local/lib/python3.2/site-packages/matplotlib/axes.py",
>  > line 6741, in fill_between
>  >  y1 = ma.masked_invalid(self.convert_yunits(y1))
>  >File
>  >
> 
> "/home/local/ANT/ptrembl/.local/lib/python3.2/site-packages/numpy/ma/core.py",
>  > line 2241, in masked_invalid
>  >  condition = ~(np.isfinite(a))
>  > TypeError: ufunc 'isfinite' not supported for the input
> types,
>  > and the inputs could not be safely coerced to any supported
>  > types according to the casting rule ''safe''
>  >
>  >
>  > [Decimal('3619.900530366609820157812617'), .]
>  >
>  > If I change the list from type Decimal to type float, then I
>  > don't get the error. Likewise, if I use Python 2.7, I
> also don't
>  > get an error.
>  >
>  > After reading over the error message, I realize that this
> error
>  > really results because of numpy, not matplotlib. But I'll go
>  > ahead and post this message, in case you are unaware of the
>  > problem.
>  >
>  >
>  > Just a quick note, mpl v1.1.x is not officially supported for
> py3k.
>  > The upcoming release of v1.2.0 will be the first official release
>  > with such support.
>  >
>  > That being said, it probably would be a good idea to make
> sure where
>  > the bug lies for this one (numpy or matplotlib).  Which
> version of
>  > numpy are you using?
>  >
>  > Ben Root
>  >
>  >
>  >
>  >
>  >
> 
> --
>  > Live Security Virtual Conference
>  > Exclusive live event will cover all the ways today's security and
>  > threat landscape has changed and how IT managers can respond.
> Discussions
>  > will include endpoint security, mobile security and the latest in
> ma

Re: [Matplotlib-users] type error with python 3.2 and version 1.1.1 of matplotlib (numpy error)

[Paul Tremblay]

Hmm. I found that mpl handled my datetime objects just fine:

# put the weeks on the x axis
# dates are datetime.datetime
ax.plot(dates, defects)
ax.xaxis.set_major_formatter(
matplotlib.dates.DateFormatter('%W'))

# create an invisible line in order to
# create a secondary x axis below
# the first axis, which just has the month(s)
newax = fig.add_axes(ax.get_position())
newax.spines['bottom'].set_position(('outward', 25))
newax.patch.set_visible(False)
newax.yaxis.set_visible(False)
# months are also datetime. However, I filtered out
# all dates except the first date for each month
newax.plot_date(months, y,  visible=False)
newax.xaxis.set_major_locator(
matplotlib.dates.MonthLocator()
)
newax.xaxis.set_major_formatter(
matplotlib.dates.DateFormatter('%b')
)

On Thu, Sep 6, 2012 at 12:02 AM, Eric Firing  wrote:

> On 2012/09/05 4:04 PM, Paul Tremblay wrote:
> > I am using numpy 1.7, which I built myself (python3 setup.py build). I
> > had a chance to look a bit deeper into matplotlib, which in turn forced
> > me to learn a bit of numpy, and now I see that it probably makes more
> > sense to use numpy arrays for my data. Since the default for an array is
> > a float, most users won't encounter the problems I did, but a warning in
> > a FAQ might solve a few headaches, regardless of how the developers
> > decided to go.
>
> Paul,
>
> numpy 1.7 has a new datetime dtype which probably would be good for your
> use--except that mpl doesn't support it yet.  That will be a project for
> mpl v1.3.
>
> Eric
>
> >
> > Thanks for your help.
> >
> > Paul
> >
> > On Tue, Sep 4, 2012 at 3:09 PM, Benjamin Root  > > wrote:
> >
> >
> >
> > On Tue, Sep 4, 2012 at 2:20 PM, Paul Tremblay
> > mailto:paulhtremb...@gmail.com>> wrote:
> >
> >
> > The following Python code:
> >
> >  >>ax.fill_between(dates, lower, upper, facecolor='gray',
> alpha=0.5)
> >
> > Produces this error with Python 3.2:
> >
> > Traceback (most recent call last):
> >File "scripts/audit_reports_weekly.py", line 150, in 
> >  ax.fill_between(dates, lower, upper, facecolor='gray',
> > alpha=0.5)
> >File
> >
> "/home/local/ANT/ptrembl/.local/lib/python3.2/site-packages/matplotlib/axes.py",
> > line 6741, in fill_between
> >  y1 = ma.masked_invalid(self.convert_yunits(y1))
> >File
> >
> "/home/local/ANT/ptrembl/.local/lib/python3.2/site-packages/numpy/ma/core.py",
> > line 2241, in masked_invalid
> >  condition = ~(np.isfinite(a))
> > TypeError: ufunc 'isfinite' not supported for the input types,
> > and the inputs could not be safely coerced to any supported
> > types according to the casting rule ''safe''
> >
> >
> > [Decimal('3619.900530366609820157812617'), .]
> >
> > If I change the list from type Decimal to type float, then I
> > don't get the error. Likewise, if I use Python 2.7, I also don't
> > get an error.
> >
> > After reading over the error message, I realize that this error
> > really results because of numpy, not matplotlib. But I'll go
> > ahead and post this message, in case you are unaware of the
> > problem.
> >
> >
> > Just a quick note, mpl v1.1.x is not officially supported for py3k.
> > The upcoming release of v1.2.0 will be the first official release
> > with such support.
> >
> > That being said, it probably would be a good idea to make sure where
> > the bug lies for this one (numpy or matplotlib).  Which version of
> > numpy are you using?
> >
> > Ben Root
> >
> >
> >
> >
> >
> --
> > Live Security Virtual Conference
> > Exclusive live event will cover all the ways today's security and
> > threat landscape has changed and how IT managers can respond. Discussions
> > will include endpoint security, mobile security and the latest in malware
> > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> >
> >
> >
> > ___
> > Matplotlib-users mailing list
> > Matplotlib-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >
>
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> Matplotlib-users mailing list
> Matplotlib-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
---

Re: [Matplotlib-users] type error with python 3.2 and version 1.1.1 of matplotlib (numpy error)

[Eric Firing]

On 2012/09/05 4:04 PM, Paul Tremblay wrote:
> I am using numpy 1.7, which I built myself (python3 setup.py build). I
> had a chance to look a bit deeper into matplotlib, which in turn forced
> me to learn a bit of numpy, and now I see that it probably makes more
> sense to use numpy arrays for my data. Since the default for an array is
> a float, most users won't encounter the problems I did, but a warning in
> a FAQ might solve a few headaches, regardless of how the developers
> decided to go.

Paul,

numpy 1.7 has a new datetime dtype which probably would be good for your 
use--except that mpl doesn't support it yet.  That will be a project for 
mpl v1.3.

Eric

>
> Thanks for your help.
>
> Paul
>
> On Tue, Sep 4, 2012 at 3:09 PM, Benjamin Root  > wrote:
>
>
>
> On Tue, Sep 4, 2012 at 2:20 PM, Paul Tremblay
> mailto:paulhtremb...@gmail.com>> wrote:
>
>
> The following Python code:
>
>  >>ax.fill_between(dates, lower, upper, facecolor='gray', alpha=0.5)
>
> Produces this error with Python 3.2:
>
> Traceback (most recent call last):
>File "scripts/audit_reports_weekly.py", line 150, in 
>  ax.fill_between(dates, lower, upper, facecolor='gray',
> alpha=0.5)
>File
> 
> "/home/local/ANT/ptrembl/.local/lib/python3.2/site-packages/matplotlib/axes.py",
> line 6741, in fill_between
>  y1 = ma.masked_invalid(self.convert_yunits(y1))
>File
> 
> "/home/local/ANT/ptrembl/.local/lib/python3.2/site-packages/numpy/ma/core.py",
> line 2241, in masked_invalid
>  condition = ~(np.isfinite(a))
> TypeError: ufunc 'isfinite' not supported for the input types,
> and the inputs could not be safely coerced to any supported
> types according to the casting rule ''safe''
>
>
> [Decimal('3619.900530366609820157812617'), .]
>
> If I change the list from type Decimal to type float, then I
> don't get the error. Likewise, if I use Python 2.7, I also don't
> get an error.
>
> After reading over the error message, I realize that this error
> really results because of numpy, not matplotlib. But I'll go
> ahead and post this message, in case you are unaware of the
> problem.
>
>
> Just a quick note, mpl v1.1.x is not officially supported for py3k.
> The upcoming release of v1.2.0 will be the first official release
> with such support.
>
> That being said, it probably would be a good idea to make sure where
> the bug lies for this one (numpy or matplotlib).  Which version of
> numpy are you using?
>
> Ben Root
>
>
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
>
> ___
> Matplotlib-users mailing list
> Matplotlib-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Re: [Matplotlib-users] type error with python 3.2 and version 1.1.1 of matplotlib (numpy error)

[Paul Tremblay]

I am using numpy 1.7, which I built myself (python3 setup.py build). I had
a chance to look a bit deeper into matplotlib, which in turn forced me to
learn a bit of numpy, and now I see that it probably makes more sense to
use numpy arrays for my data. Since the default for an array is a float,
most users won't encounter the problems I did, but a warning in a FAQ might
solve a few headaches, regardless of how the developers decided to go.

Thanks for your help.

Paul

On Tue, Sep 4, 2012 at 3:09 PM, Benjamin Root  wrote:

>
>
> On Tue, Sep 4, 2012 at 2:20 PM, Paul Tremblay wrote:
>
>>
>> The following Python code:
>>
>> >>ax.fill_between(dates, lower, upper, facecolor='gray', alpha=0.5)
>>
>> Produces this error with Python 3.2:
>>
>> Traceback (most recent call last):
>>   File "scripts/audit_reports_weekly.py", line 150, in 
>> ax.fill_between(dates, lower, upper, facecolor='gray', alpha=0.5)
>>   File
>> "/home/local/ANT/ptrembl/.local/lib/python3.2/site-packages/matplotlib/axes.py",
>> line 6741, in fill_between
>> y1 = ma.masked_invalid(self.convert_yunits(y1))
>>   File
>> "/home/local/ANT/ptrembl/.local/lib/python3.2/site-packages/numpy/ma/core.py",
>> line 2241, in masked_invalid
>> condition = ~(np.isfinite(a))
>> TypeError: ufunc 'isfinite' not supported for the input types, and the
>> inputs could not be safely coerced to any supported types according to the
>> casting rule ''safe''
>>
>>
>> [Decimal('3619.900530366609820157812617'), .]
>>
>> If I change the list from type Decimal to type float, then I don't get
>> the error. Likewise, if I use Python 2.7, I also don't get an error.
>>
>> After reading over the error message, I realize that this error really
>> results because of numpy, not matplotlib. But I'll go ahead and post this
>> message, in case you are unaware of the problem.
>>
>>
> Just a quick note, mpl v1.1.x is not officially supported for py3k.  The
> upcoming release of v1.2.0 will be the first official release with such
> support.
>
> That being said, it probably would be a good idea to make sure where the
> bug lies for this one (numpy or matplotlib).  Which version of numpy are
> you using?
>
> Ben Root
>
>
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Re: [Matplotlib-users] Using the lasso tool when file is not main

[Tony Yu]

On Wed, Sep 5, 2012 at 7:19 PM, Mark Budde  wrote:

> Hi,
> I'm not an expert so please go easy on me. I am using the pyplot lasso
> demo, and have got it to work how I would like. I am having a problem,
> however, where I cannot get it to work if my python file is not the
> main file (where __name__ is not __main__).
>
> I took the part at the bottom in the "if __name__ == '__main__':" and
> put it into a class. Everything works fine if I call the class from
> within the same file. However, if I call the class from another file,
> the graph loads fine but the lasso tool does not work. Troubleshooting
> revealed that LassoManager.onpress is not being called when I click
> the mouse. Any suggestions are welcome because this is driving me
> crazy!
> Thanks,
> Mark
>
>
Hi Mark,

I can't seem to reproduce your issue, but it's a bit difficult without
seeing how exactly you wrapped up the "main" part of the code. Just
guessing: maybe the two cases aren't *exactly* the same.

Is it possible that you have ``lman`` (the LassoManager instance) defined
in the same block of code as ``show`` in one case but not the other? If,
for example, ``lman`` is defined in a method of your class, but not saved
anywhere then it'll get discarded after the method finishes. So ``show``
would need to be called inside that method, or saved as a class attribute.

Like I said, that's just a wild guess. You should paste the class def if
you're still having problems.

Best
-Tony

P.S. If you're running matplotlib from Github master, you might be
interested in an alternative lasso tool  (LassoSelector) that may be
simpler to use.:
https://github.com/matplotlib/matplotlib/blob/master/examples/widgets/lasso_selector_demo.py
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Re: [Matplotlib-users] Using the lasso tool when file is not main

[Benjamin Root]

On Wednesday, September 5, 2012, Mark Budde wrote:

> Hi,
> I'm not an expert so please go easy on me. I am using the pyplot lasso
> demo, and have got it to work how I would like. I am having a problem,
> however, where I cannot get it to work if my python file is not the
> main file (where __name__ is not __main__).
>
> I took the part at the bottom in the "if __name__ == '__main__':" and
> put it into a class. Everything works fine if I call the class from
> within the same file. However, if I call the class from another file,
> the graph loads fine but the lasso tool does not work. Troubleshooting
> revealed that LassoManager.onpress is not being called when I click
> the mouse. Any suggestions are welcome because this is driving me
> crazy!
> Thanks,
> Mark


I can assure you that it does work from a library because I have done that.
 Most likely it is some minor error in your code.  Is it possible to post a
simple example to demonstrate your problem?

Ben Root
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

[Matplotlib-users] Using the lasso tool when file is not main

[Mark Budde]

Hi,
I'm not an expert so please go easy on me. I am using the pyplot lasso
demo, and have got it to work how I would like. I am having a problem,
however, where I cannot get it to work if my python file is not the
main file (where __name__ is not __main__).

I took the part at the bottom in the "if __name__ == '__main__':" and
put it into a class. Everything works fine if I call the class from
within the same file. However, if I call the class from another file,
the graph loads fine but the lasso tool does not work. Troubleshooting
revealed that LassoManager.onpress is not being called when I click
the mouse. Any suggestions are welcome because this is driving me
crazy!
Thanks,
Mark

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Re: [Matplotlib-users] Legend Marker Color Bug

[Sterling Smith]

On Sep 4, 2012, at 5:33PM, Jae-Joon Lee wrote:

> On Wed, Sep 5, 2012 at 6:05 AM, Sterling Smith  wrote:
>> I still do not get black markers.  Furthermore, if you try to make a new 
>> legend with the result of leg.get_lines(), you will get lines without 
>> markers, which leads me to the conclusion I stated in my previous email 
>> (which you did not copy)
 I suspect that this is because the legend marker is drawn separately from 
 the legend line to accommodate the numpoints argument of the legend 
 functions.  Then the question is how to access these markers if they are 
 separate from the line2d objects in the legend.  I didn't even see them in 
 the children of the legend [legend.get_children()].
> 
> This is correct. To support legend handle like --o-- (i.e., no markers
> at the ends), lines and markers are drawn as a separate artist. You
> may use something like,
> 
> line[0]._legmarker.set_markerfacecolor('black')
> line[1]._legmarker.set_markerfacecolor('black')
> 
> I, personally, recommend you to use a proxy artist.
> 
> http://matplotlib.sourceforge.net/users/legend_guide.html#using-proxy-artist
> 
> For example,
> 
> You may do something like
> 
> import pylab
> pylab.plot(pylab.linspace(0,1,100),marker='o',ls='')
> pylab.plot(pylab.linspace(0,1,100),marker='o',ls='-')
> 
> # creates artists for legend purpose only
> l1, = pylab.plot(pylab.linspace(0,1,100), 'ko-')
> l2, = pylab.plot(pylab.linspace(0,1,100), 'ko')
> # remove them from the axes.
> l1.remove()
> l2.remove()
> 
> leg=pylab.legend([l1, l2], ["Test 1", "Test 2"], loc='best')
> 
> Regards,
> 
> -JJ

JJ,

Thank you for responding.  I was looking for the _legmarker method, which works 
great.

Thanks,
Sterling


--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Re: [Matplotlib-users] axes_grid1.inset_axes frame background color

[Jae-Joon Lee]

There is no easy way to do it (the extent of axes including the labels
is determined only when the plot is drawn).
And most straight forward way is to define your own artist.
Attached is an one example of such artist. I think it is good to have
such an artist class in matplotlib and I may able to push some
generalized version of this into matplotlib.

On the other hand, your reason to draw a white box is to improve the
visibility of tick labels, I recommend you to use path_effect.

from matplotlib.patheffects import withStroke
plt.setp(axins1.xaxis.get_majorticklabels(),
 path_effects=[withStroke(foreground="w", linewidth=3)])

IHTH,

-JJ


On Thu, Aug 16, 2012 at 12:39 AM, Scott Henderson  wrote:
> Hello,
>
> I'm trying to modify the following script to no avail:
> http://matplotlib.github.com/examples/axes_grid/demo_colorbar_with_inset_locator.html
>
> I'd like to have a white background behind the inset colorbar that
> adjusts automatically to figure resizing. I'm thinking of doing this by
> adding a Rectangle patch with the appropriate axes coordinates. What's
> the easiest way get those coordinates (sufficiently big to include the
> ticklabels) & draw the patch?
>
> Thanks,
>
> --
> ---
> Scott T. Henderson
> http://www.geo.cornell.edu/eas/gstudent/sth54/contact.html
>
>
> --
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> ___
> Matplotlib-users mailing list
> Matplotlib-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users


rrer.py
Description: Binary data
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users