matplotlib-users Mailing List for matplotlib (Page 5)

How to add number near point of scatter plot?
e.g. I have two point 1 is (1,3) and point 2 (2,4), how can I add 1
and 2 to scatter plot near these two points? Thanks!

import matplotlib.pyplot as plt
x = [1,2]
y = [3,4]
plt.scatter(x, y)
plt.show()

On 04/04/2013 19:00, Mark Lawrence wrote:
> Sadly no :(  I want the day of the month that I'm processing *OR* the
> last day.  The worst case for this is obviously the 31st of each month.
>    The rrule code I've given provides exactly that.  When transferred to
> mpl that doesn't work.

Best seen by changing the lines I gave originally to this.

start = datetime.date(2013, 4, 5)
until = datetime.date(2014, 4, 5)
dates = rrule(MONTHLY, bymonthday=(5, -1), bysetpos=1, until=until)

rrule output as follows.

2013-04-05 10:15:24
2013-05-05 10:15:24
2013-06-05 10:15:24
2013-07-05 10:15:24
2013-08-05 10:15:24
2013-09-05 10:15:24
2013-10-05 10:15:24
2013-11-05 10:15:24
2013-12-05 10:15:24
2014-01-05 10:15:24
2014-02-05 10:15:24
2014-03-05 10:15:24

Plot attached.

>
> On 04/04/2013 17:31, Phil Elson wrote:
>> Hi Mark,
>>
>> Thanks for persevering :-)
>>
>> What is it you want to achieve? Is it that you just want the last day of
>> each month as the located value?
>>
>> Changing your locator to:
>>
>> ax.xaxis.set_major_locator(MonthLocator(bymonthday = -1))
>>
>> Seems to do the trick for me (I've never looked at the mpl date magic,
>> so I can give no guarantees).
>>
>> HTH,
>>
>>
>> On 4 April 2013 17:18, Mark Lawrence
>> <bre...@ya...
>> <mailto:bre...@ya...>> wrote:
>>
>>      On 01/04/2013 14:48, Mark Lawrence wrote:
>>       > On 29/03/2013 15:49, Mark Lawrence wrote:
>>       >> Hi all,
>>       >>
>>       >>    From http://labix.org/python-dateutil
>>       >>
>>       >> "To generate a rrule for the use case of "a date on the
>>      specified day of
>>       >> the month, unless it is beyond the end of month, in which case
>>      it will
>>       >> be the last day of the month" use the following:
>>       >>
>>       >> rrule(MONTHLY, bymonthday=(some_day, -1), bysetpos=1)
>>       >>
>>       >> This will generate a value for every calendar month regardless
>>      of the
>>       >> day of the month it is started from."
>>       >>
>>       >> Using bymonthday with MonthLocator gives ticks on the day given
>>      and the
>>       >> last day of the month, which looks extremely ugly.  Code below
>>      demonstrates.
>>       >>
>>       >> from dateutil.rrule import *
>>       >> import datetime
>>       >> import matplotlib.pyplot as plt
>>       >> from matplotlib.ticker import FormatStrFormatter, MultipleLocator
>>       >> from matplotlib.dates import DateFormatter, MonthLocator, DayLocator
>>       >>
>>       >> start = datetime.date(2013, 3, 29)
>>       >> until = datetime.date(2014, 3, 29)
>>       >> dates = rrule(MONTHLY, bymonthday=(29, -1), bysetpos=1, until=until)
>>       >> for d in dates:print(d)
>>       >>
>>       >> dates = [start, until]
>>       >> values = [0, 1]
>>       >> plt.ylabel('Balance')
>>       >> plt.grid()
>>       >> ax = plt.subplot(111)
>>       >> plt.plot_date(dates, values, fmt = 'rx-')
>>       >> ax.xaxis.set_major_locator(MonthLocator(bymonthday =
>>      (dates[0].day, -1)))
>>       >> ax.xaxis.set_major_formatter(DateFormatter('%d/%m/%y'))
>>       >> ax.yaxis.set_major_formatter(FormatStrFormatter('£%0.2f'))
>>       >> ax.yaxis.set_minor_locator(MultipleLocator(5))
>>       >> plt.axis(xmin=dates[0], xmax=dates[-1])
>>       >> plt.setp(plt.gca().get_xticklabels(), rotation = 45, fontsize = 10)
>>       >> plt.setp(plt.gca().get_yticklabels(), fontsize = 10)
>>       >> plt.show()
>>       >>
>>       >
>>       > Seems an apt date to realise that I didn't say much :(
>>       >
>>       > Assuming that I'm correct would you like an issue raised on the bug
>>       > tracker?  If not please correct the mistake I've made, presumably in
>>       > reading the docs, which I think are excellent by the way.
>>       >
>>
>>      Anybody?
>>
>>      --
>>      If you're using GoogleCrap™ please read this
>>      http://wiki.python.org/moin/GoogleGroupsPython.
>>
>
>


-- 
If you're using GoogleCrap™ please read this 
http://wiki.python.org/moin/GoogleGroupsPython.

Mark Lawrence

Phil and Derek,

I just created this as the following issue

https://github.com/matplotlib/matplotlib/issues/1886

I was wrong about TkAgg having a problem. The default backend for  
Derek and me is MacOSX. Both TkAgg and QT4Agg display correctly for me.

John

Thank You Scott,
                I mistook the values  I assumed .1 to .8 as the total x size and expected half of it should provide me 2 half boxes.
thanks a lot for clarification.
with best regards,
Sudheer
 
***************************************************************
Sudheer Joseph 
Indian National Centre for Ocean Information Services
Ministry of Earth Sciences, Govt. of India
POST BOX NO: 21, IDA Jeedeemetla P.O.
Via Pragathi Nagar,Kukatpally, Hyderabad; Pin:5000 55
Tel:+91-40-23886047(O),Fax:+91-40-23895011(O),
Tel:+91-40-23044600(R),Tel:+91-40-9440832534(Mobile)
E-mail:sjo...@gm...;sud...@ya...
Web- http://oppamthadathil.tripod.com
***************************************************************


----- Original Message -----
> From: Scott Sinclair <sco...@gm...>
> To: "mat...@li..." <mat...@li...>
> Cc: 
> Sent: Friday, 5 April 2013 6:36 PM
> Subject: Re: [Matplotlib-users] windrose
> 
> On 5 April 2013 03:54, Sudheer Joseph <sud...@ya...> wrote:
>>  Some how I am not getting the trick of the
>>  rect = [0.1, 0.1, 0.8, 0.8]
>> 
>>  I tried
>>  rect1= [0.1,0.1,.4,.4]
>>  and rect2=[.4,.4,.8,.8]
>>  but did not work
> 
> You don't say exactly what you did, and how it didn't work...
> 
> If you read 
> http://matplotlib.org/api/figure_api.html?highlight=add_axes#matplotlib.figure.Figure.add_axes
> it says "Add an axes at position rect [left, bottom, width,
> height]...". So you need to specify sensible values in rect1 and
> rect2.
> 
> The following works fine for me:
> 
> import matplotlib.pyplot as plt
> fig = plt.figure()
> rect1 = [0.1, 0.1, 0.4, 0.4]
> rect2 = [0.55, 0.1, 0.4, 0.4]
> ax1 = fig.add_axes(rect1)
> ax2 = fig.add_axes(rect2)
> ax1.plot(range(3))
> ax2.plot(range(4, 8))
> plt.show()
> 
> So I would expect that you can adapt your original code to something
> like the following (untested):
> 
> from windrose import WindroseAxes
> from matplotlib import pyplot as plt
> from numpy.random import random
> 
> def new_axes(fig, rect):
>     ax = WindroseAxes(fig, rect, axisbg='w')
>     fig.add_axes(ax)
>     return ax
> 
> def set_legend(ax):
>     l = ax.legend(axespad=-0.10)
>     plt.setp(l.get_texts(), fontsize=8)
> 
> #Create wind speed and direction variables
> ws = random(500)*6
> wd = random(500)*360
> ws1 = random(500)*6
> wd1 = random(500)*360
> 
> rect1 = [0.1, 0.1, 0.4, 0.4]
> rect2 = [0.55, 0.1, 0.4, 0.4]
> 
> fig = plt.figure(figsize=(8, 8), dpi=80, facecolor='w', 
> edgecolor='w')
> 
> ax1 = new_axes(fig, rect1)
> ax2 = new_axes(fig, rect2)
> 
> #windrose like a stacked histogram with normed (displayed in percent) results
> ax1.bar(wd, ws, normed=True, opening=0.8, edgecolor='white')
> set_legend(ax1)
> 
> #windrose like a stacked histogram with normed (displayed in percent) results
> ax2.bar(wd1, ws1, normed=True, opening=0.8, edgecolor='white')
> set_legend(ax2)
> 
> plt.show()
> 
> Cheers,
> Scott
> 
> ------------------------------------------------------------------------------
> Minimize network downtime and maximize team effectiveness.
> Reduce network management and security costs.Learn how to hire 
> the most talented Cisco Certified professionals. Visit the 
> Employer Resources Portal
> http://www.cisco.com/web/learning/employer_resources/index.html
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 

Here's the output.  I'm running OS X 10.8.3.  I installed matplotlib
from homebrew.

$HOME=/Users/dect
CONFIGDIR=/Users/dect/.matplotlib
matplotlib data path /usr/local/lib/python2.7/site-packages/matplotlib/mpl-data
loaded rc file /usr/local/lib/python2.7/site-packages/matplotlib/mpl-data/matplotlibrc
matplotlib version 1.2.0
verbose.level helpful
interactive is False
platform is darwin
Using fontManager instance from /Users/dect/.matplotlib/fontList.cache
backend MacOSX version unknown

>>> mpl.__file__
'/usr/local/lib/python2.7/site-packages/matplotlib/__init__.pyc'
>>> mpl.get_backend()
'MacOSX'
>>> mpl.__version__
'1.2.0'
>>> mpl.get_configdir()
'/Users/dect/.matplotlib'

On Fri, Apr 5, 2013 at 2:07 AM, Phil Elson <pel...@gm...> wrote:
> Thanks Derek & John.
>
> Very strange. Here's my setup:
>
>>>> import matplotlib
>>>> matplotlib.__version__
> '1.2.0'
>>>> matplotlib.get_backend()
> 'TkAgg'
>
>
> Would you mind providing all of the relevant details suggested in
> http://matplotlib.org/faq/troubleshooting_faq.html#troubleshooting, along
> with the code to reproduce the problem in a new github issue?
>
> Once I have all of the necessary details, I'd be happy to have a look into
> this to see if I can find a solution.
>
> Cheers,
>
> Phil
>
>
>
> On 5 April 2013 02:02, John Gleeson <jdg...@ma...> wrote:
>>
>>
>> On 2013-04-04, at 10:51 AM, Derek Thomas wrote:
>>
>>> ...screen capture of the display...
>>> <grab.tiff>
>>
>>
>> Derek,
>>
>> I just tried Phil's version of the code on my Mac (MP 1.2.0), and I see
>> exactly the same problem as in your grab.tiff. This is using the default
>> TkAgg backend.
>>
>> I happen to have built MP 1.2.0 with the Qt4 backend option. When I
>> prepend the lines
>>
>>     from matplotlib import use
>>     use("QT4Agg")
>>
>> to use Qt4, I get the expected (correct) display output.
>>
>> Apparently this is a bug somewhere in the chain TkAgg/Tkinter/Tk.
>>
>> John
>>
>

Thank you, it works flawlessly now :)


2013/3/31 Juergen Hasch <py...@el...>

> Am 31.03.2013 08:50, schrieb Pawel Chojnacki:
>
>  Thank you very much - hovewer, your solution isn't enough. Adding your
>> lines generate:
>>
>>
> The problem is this:
>
>
>  RuntimeError: LaTeX was not able to process the following string:
>> u''
>> Here is the full report generated by LaTeX:
>>
>>
> Latex doesn't like the empty string. This is caused by the '\n' in your
> title.
> Can you replace your original line:
>         py.title(u'Wyniki eksperymentu pomiaru gęstości ciała
> stałego\n',size='large',**family='serif')
> with the new one, as in the example I sent you:
>
>         py.title(u'Wyniki eksperymentu pomiaru gęstości ciała
> stałego',size='large',family='**serif')
>
>

On 5 April 2013 03:54, Sudheer Joseph <sud...@ya...> wrote:
> Some how I am not getting the trick of the
> rect = [0.1, 0.1, 0.8, 0.8]
>
> I tried
> rect1= [0.1,0.1,.4,.4]
> and rect2=[.4,.4,.8,.8]
> but did not work

You don't say exactly what you did, and how it didn't work...

If you read http://matplotlib.org/api/figure_api.html?highlight=add_axes#matplotlib.figure.Figure.add_axes
it says "Add an axes at position rect [left, bottom, width,
height]...". So you need to specify sensible values in rect1 and
rect2.

The following works fine for me:

import matplotlib.pyplot as plt
fig = plt.figure()
rect1 = [0.1, 0.1, 0.4, 0.4]
rect2 = [0.55, 0.1, 0.4, 0.4]
ax1 = fig.add_axes(rect1)
ax2 = fig.add_axes(rect2)
ax1.plot(range(3))
ax2.plot(range(4, 8))
plt.show()

So I would expect that you can adapt your original code to something
like the following (untested):

from windrose import WindroseAxes
from matplotlib import pyplot as plt
from numpy.random import random

def new_axes(fig, rect):
    ax = WindroseAxes(fig, rect, axisbg='w')
    fig.add_axes(ax)
    return ax

def set_legend(ax):
    l = ax.legend(axespad=-0.10)
    plt.setp(l.get_texts(), fontsize=8)

#Create wind speed and direction variables
ws = random(500)*6
wd = random(500)*360
ws1 = random(500)*6
wd1 = random(500)*360

rect1 = [0.1, 0.1, 0.4, 0.4]
rect2 = [0.55, 0.1, 0.4, 0.4]

fig = plt.figure(figsize=(8, 8), dpi=80, facecolor='w', edgecolor='w')

ax1 = new_axes(fig, rect1)
ax2 = new_axes(fig, rect2)

#windrose like a stacked histogram with normed (displayed in percent) results
ax1.bar(wd, ws, normed=True, opening=0.8, edgecolor='white')
set_legend(ax1)

#windrose like a stacked histogram with normed (displayed in percent) results
ax2.bar(wd1, ws1, normed=True, opening=0.8, edgecolor='white')
set_legend(ax2)

plt.show()

Cheers,
Scott

Thanks Derek & John.

Very strange. Here's my setup:

>>> import matplotlib
>>> matplotlib.__version__
'1.2.0'
>>> matplotlib.get_backend()
'TkAgg'


Would you mind providing all of the relevant details suggested in
http://matplotlib.org/faq/troubleshooting_faq.html#troubleshooting, along
with the code to reproduce the problem in a new github issue?

Once I have all of the necessary details, I'd be happy to have a look into
this to see if I can find a solution.

Cheers,

Phil



On 5 April 2013 02:02, John Gleeson <jdg...@ma...> wrote:

>
> On 2013-04-04, at 10:51 AM, Derek Thomas wrote:
>
>  ...screen capture of the display...
>> <grab.tiff>
>>
>
> Derek,
>
> I just tried Phil's version of the code on my Mac (MP 1.2.0), and I see
> exactly the same problem as in your grab.tiff. This is using the default
> TkAgg backend.
>
> I happen to have built MP 1.2.0 with the Qt4 backend option. When I
> prepend the lines
>
>     from matplotlib import use
>     use("QT4Agg")
>
> to use Qt4, I get the expected (correct) display output.
>
> Apparently this is a bug somewhere in the chain TkAgg/Tkinter/Tk.
>
> John
>
>

Thank you Scott,

Some how I am not getting the trick of the 
rect = [0.1, 0.1, 0.8, 0.8]

I tried 
rect1= [0.1,0.1,.4,.4]
and rect2=[.4,.4,.8,.8] 
but did not work
Sudheer
 
***************************************************************
Sudheer Joseph 
Indian National Centre for Ocean Information Services
Ministry of Earth Sciences, Govt. of India
POST BOX NO: 21, IDA Jeedeemetla P.O.
Via Pragathi Nagar,Kukatpally, Hyderabad; Pin:5000 55
Tel:+91-40-23886047(O),Fax:+91-40-23895011(O),
Tel:+91-40-23044600(R),Tel:+91-40-9440832534(Mobile)
E-mail:sjo...@gm...;sud...@ya...
Web- http://oppamthadathil.tripod.com
***************************************************************


----- Original Message -----
> From: Scott Sinclair <sco...@gm...>
> To: "mat...@li..." <mat...@li...>
> Cc: 
> Sent: Thursday, 4 April 2013 12:37 PM
> Subject: Re: [Matplotlib-users] windrose
> 
> On 4 April 2013 06:45, Sudheer Joseph <sud...@ya...> wrote:
>>            Below is a sample script I got from windrose pack. I would like 
> to place 2 windroses side by side
> ...
>> 
>>  from windrose import WindroseAxes
>>  from matplotlib import pyplot as plt
> ...
>>  def new_axes():
>>      fig = plt.figure(figsize=(8, 8), dpi=80, facecolor='w', 
> edgecolor='w')
>>      rect = [0.1, 0.1, 0.8, 0.8]
>>      ax = WindroseAxes(fig, rect, axisbg='w')
>>      fig.add_axes(ax)
>>      return ax
> 
> I'm not familiar with the windrose package, but it looks like the rect
> parameter to WindroseAxes specifies the size of the generated axes in
> figure co-ordinates (see
> http://matplotlib.org/api/figure_api.html?highlight=add_axes#matplotlib.figure.Figure.add_axes).
> You should be able to pass in a different list of co-ordinates for
> each WindroseAxes to get side-by-side axes on the same figure...
> 
> Cheers,
> Scott
> 
> ------------------------------------------------------------------------------
> Minimize network downtime and maximize team effectiveness.
> Reduce network management and security costs.Learn how to hire 
> the most talented Cisco Certified professionals. Visit the 
> Employer Resources Portal
> http://www.cisco.com/web/learning/employer_resources/index.html
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 

On 2013-04-04, at 10:51 AM, Derek Thomas wrote:

> ...screen capture of the display...
> <grab.tiff>

Derek,

I just tried Phil's version of the code on my Mac (MP 1.2.0), and I  
see exactly the same problem as in your grab.tiff. This is using the  
default TkAgg backend.

I happen to have built MP 1.2.0 with the Qt4 backend option. When I  
prepend the lines

     from matplotlib import use
     use("QT4Agg")

to use Qt4, I get the expected (correct) display output.

Apparently this is a bug somewhere in the chain TkAgg/Tkinter/Tk.

John

Sadly no :(  I want the day of the month that I'm processing *OR* the 
last day.  The worst case for this is obviously the 31st of each month. 
  The rrule code I've given provides exactly that.  When transferred to 
mpl that doesn't work.

On 04/04/2013 17:31, Phil Elson wrote:
> Hi Mark,
>
> Thanks for persevering :-)
>
> What is it you want to achieve? Is it that you just want the last day of
> each month as the located value?
>
> Changing your locator to:
>
> ax.xaxis.set_major_locator(MonthLocator(bymonthday = -1))
>
> Seems to do the trick for me (I've never looked at the mpl date magic,
> so I can give no guarantees).
>
> HTH,
>
>
> On 4 April 2013 17:18, Mark Lawrence
> <bre...@ya...
> <mailto:bre...@ya...>> wrote:
>
>     On 01/04/2013 14:48, Mark Lawrence wrote:
>      > On 29/03/2013 15:49, Mark Lawrence wrote:
>      >> Hi all,
>      >>
>      >>    From http://labix.org/python-dateutil
>      >>
>      >> "To generate a rrule for the use case of "a date on the
>     specified day of
>      >> the month, unless it is beyond the end of month, in which case
>     it will
>      >> be the last day of the month" use the following:
>      >>
>      >> rrule(MONTHLY, bymonthday=(some_day, -1), bysetpos=1)
>      >>
>      >> This will generate a value for every calendar month regardless
>     of the
>      >> day of the month it is started from."
>      >>
>      >> Using bymonthday with MonthLocator gives ticks on the day given
>     and the
>      >> last day of the month, which looks extremely ugly.  Code below
>     demonstrates.
>      >>
>      >> from dateutil.rrule import *
>      >> import datetime
>      >> import matplotlib.pyplot as plt
>      >> from matplotlib.ticker import FormatStrFormatter, MultipleLocator
>      >> from matplotlib.dates import DateFormatter, MonthLocator, DayLocator
>      >>
>      >> start = datetime.date(2013, 3, 29)
>      >> until = datetime.date(2014, 3, 29)
>      >> dates = rrule(MONTHLY, bymonthday=(29, -1), bysetpos=1, until=until)
>      >> for d in dates:print(d)
>      >>
>      >> dates = [start, until]
>      >> values = [0, 1]
>      >> plt.ylabel('Balance')
>      >> plt.grid()
>      >> ax = plt.subplot(111)
>      >> plt.plot_date(dates, values, fmt = 'rx-')
>      >> ax.xaxis.set_major_locator(MonthLocator(bymonthday =
>     (dates[0].day, -1)))
>      >> ax.xaxis.set_major_formatter(DateFormatter('%d/%m/%y'))
>      >> ax.yaxis.set_major_formatter(FormatStrFormatter('£%0.2f'))
>      >> ax.yaxis.set_minor_locator(MultipleLocator(5))
>      >> plt.axis(xmin=dates[0], xmax=dates[-1])
>      >> plt.setp(plt.gca().get_xticklabels(), rotation = 45, fontsize = 10)
>      >> plt.setp(plt.gca().get_yticklabels(), fontsize = 10)
>      >> plt.show()
>      >>
>      >
>      > Seems an apt date to realise that I didn't say much :(
>      >
>      > Assuming that I'm correct would you like an issue raised on the bug
>      > tracker?  If not please correct the mistake I've made, presumably in
>      > reading the docs, which I think are excellent by the way.
>      >
>
>     Anybody?
>
>     --
>     If you're using GoogleCrap™ please read this
>     http://wiki.python.org/moin/GoogleGroupsPython.
>


-- 
If you're using GoogleCrap™ please read this 
http://wiki.python.org/moin/GoogleGroupsPython.

Mark Lawrence

I've been seeing some discrepancy between display and saved figures.  See
attached.  One is the result of the save, the other is the screen capture
of the display.  I'm using 1.2.0 on a mac.


On Thu, Apr 4, 2013 at 9:46 AM, Derek Thomas <der...@gm...> wrote:

> I get a different result.
>
>
> On Thu, Apr 4, 2013 at 9:25 AM, Phil Elson <pel...@gm...> wrote:
>
>> Hi Derek,
>>
>> What are we looking at here?
>>
>> The following code:
>>
>> import matplotlib.pyplot as plt
>> import matplotlib.transforms as mtrans
>> import numpy as np
>>
>> plt.figure()
>> ax = plt.subplot(111)
>> base_trans = ax.transData
>> mtx = np.array([[1,1,0],
>>                 [0,1,0],
>>                 [0,0,1]])
>> tr = mtrans.Affine2D(matrix=mtx) + base_trans
>>
>> plt.plot([1,2,3], [1,2,3], 'gray', transform=tr)
>> plt.scatter([1,2,3], [1,2,3], c='k', marker='D', transform=tr)
>> plt.show()
>>
>> produces the following plot on v1.2.0:
>> [image: Inline images 1]
>> Is this unexpected or are you getting a different result to me?
>>
>> Regards,
>>
>>
>>
>> On 4 April 2013 17:06, Derek Thomas <der...@gm...> wrote:
>>
>>> I posted a related question on stackoverflow
>>> (
>>> http://stackoverflow.com/questions/15815862/apply-affine-transform-to-quiver-in-python-matplotlib
>>> )
>>> but I've produced a simple enough example with strange results that I
>>> think it merits attention here.  I'm trying to apply affine transforms
>>> to quiver and scatter plots.  In all cases that I've considered, the
>>> scatter and quiver plots transform opposite the regular plot.  Here's
>>> a minimal case:
>>>
>>> import matplotlib as mpl
>>> from pylab import figure, subplot, plot, scatter, show, axis
>>>
>>> figure()
>>> ax = subplot(111)
>>> base_trans = ax.transData
>>> tr =  mpl.transforms.Affine2D(matrix =
>>> array([[1,1,0],[0,1,0],[0,0,1]])) + base_trans
>>>
>>>
>>> plot( [1,2,3], [1,2,3], 'k.', transform = tr )
>>> scatter( [1,2,3], [1,2,3], c = 'k', marker = 'D', transform = tr )
>>> axis([0,7,0,7])
>>> show()
>>>
>>> Thanks,
>>>
>>> Derek
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Minimize network downtime and maximize team effectiveness.
>>> Reduce network management and security costs.Learn how to hire
>>> the most talented Cisco Certified professionals. Visit the
>>> Employer Resources Portal
>>> http://www.cisco.com/web/learning/employer_resources/index.html
>>> _______________________________________________
>>> Matplotlib-users mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>>
>>
>>
>

I get a different result.


On Thu, Apr 4, 2013 at 9:25 AM, Phil Elson <pel...@gm...> wrote:

> Hi Derek,
>
> What are we looking at here?
>
> The following code:
>
> import matplotlib.pyplot as plt
> import matplotlib.transforms as mtrans
> import numpy as np
>
> plt.figure()
> ax = plt.subplot(111)
> base_trans = ax.transData
> mtx = np.array([[1,1,0],
>                 [0,1,0],
>                 [0,0,1]])
> tr = mtrans.Affine2D(matrix=mtx) + base_trans
>
> plt.plot([1,2,3], [1,2,3], 'gray', transform=tr)
> plt.scatter([1,2,3], [1,2,3], c='k', marker='D', transform=tr)
> plt.show()
>
> produces the following plot on v1.2.0:
> [image: Inline images 1]
> Is this unexpected or are you getting a different result to me?
>
> Regards,
>
>
>
> On 4 April 2013 17:06, Derek Thomas <der...@gm...> wrote:
>
>> I posted a related question on stackoverflow
>> (
>> http://stackoverflow.com/questions/15815862/apply-affine-transform-to-quiver-in-python-matplotlib
>> )
>> but I've produced a simple enough example with strange results that I
>> think it merits attention here.  I'm trying to apply affine transforms
>> to quiver and scatter plots.  In all cases that I've considered, the
>> scatter and quiver plots transform opposite the regular plot.  Here's
>> a minimal case:
>>
>> import matplotlib as mpl
>> from pylab import figure, subplot, plot, scatter, show, axis
>>
>> figure()
>> ax = subplot(111)
>> base_trans = ax.transData
>> tr =  mpl.transforms.Affine2D(matrix =
>> array([[1,1,0],[0,1,0],[0,0,1]])) + base_trans
>>
>>
>> plot( [1,2,3], [1,2,3], 'k.', transform = tr )
>> scatter( [1,2,3], [1,2,3], c = 'k', marker = 'D', transform = tr )
>> axis([0,7,0,7])
>> show()
>>
>> Thanks,
>>
>> Derek
>>
>>
>> ------------------------------------------------------------------------------
>> Minimize network downtime and maximize team effectiveness.
>> Reduce network management and security costs.Learn how to hire
>> the most talented Cisco Certified professionals. Visit the
>> Employer Resources Portal
>> http://www.cisco.com/web/learning/employer_resources/index.html
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>
>

Hi Mark,

Thanks for persevering :-)

What is it you want to achieve? Is it that you just want the last day of
each month as the located value?

Changing your locator to:

ax.xaxis.set_major_locator(MonthLocator(bymonthday = -1))

Seems to do the trick for me (I've never looked at the mpl date magic, so I
can give no guarantees).

HTH,




On 4 April 2013 17:18, Mark Lawrence <bre...@ya...> wrote:

> On 01/04/2013 14:48, Mark Lawrence wrote:
> > On 29/03/2013 15:49, Mark Lawrence wrote:
> >> Hi all,
> >>
> >>    From http://labix.org/python-dateutil
> >>
> >> "To generate a rrule for the use case of "a date on the specified day of
> >> the month, unless it is beyond the end of month, in which case it will
> >> be the last day of the month" use the following:
> >>
> >> rrule(MONTHLY, bymonthday=(some_day, -1), bysetpos=1)
> >>
> >> This will generate a value for every calendar month regardless of the
> >> day of the month it is started from."
> >>
> >> Using bymonthday with MonthLocator gives ticks on the day given and the
> >> last day of the month, which looks extremely ugly.  Code below
> demonstrates.
> >>
> >> from dateutil.rrule import *
> >> import datetime
> >> import matplotlib.pyplot as plt
> >> from matplotlib.ticker import FormatStrFormatter, MultipleLocator
> >> from matplotlib.dates import DateFormatter, MonthLocator, DayLocator
> >>
> >> start = datetime.date(2013, 3, 29)
> >> until = datetime.date(2014, 3, 29)
> >> dates = rrule(MONTHLY, bymonthday=(29, -1), bysetpos=1, until=until)
> >> for d in dates:print(d)
> >>
> >> dates = [start, until]
> >> values = [0, 1]
> >> plt.ylabel('Balance')
> >> plt.grid()
> >> ax = plt.subplot(111)
> >> plt.plot_date(dates, values, fmt = 'rx-')
> >> ax.xaxis.set_major_locator(MonthLocator(bymonthday = (dates[0].day,
> -1)))
> >> ax.xaxis.set_major_formatter(DateFormatter('%d/%m/%y'))
> >> ax.yaxis.set_major_formatter(FormatStrFormatter('£%0.2f'))
> >> ax.yaxis.set_minor_locator(MultipleLocator(5))
> >> plt.axis(xmin=dates[0], xmax=dates[-1])
> >> plt.setp(plt.gca().get_xticklabels(), rotation = 45, fontsize = 10)
> >> plt.setp(plt.gca().get_yticklabels(), fontsize = 10)
> >> plt.show()
> >>
> >
> > Seems an apt date to realise that I didn't say much :(
> >
> > Assuming that I'm correct would you like an issue raised on the bug
> > tracker?  If not please correct the mistake I've made, presumably in
> > reading the docs, which I think are excellent by the way.
> >
>
> Anybody?
>
> --
> If you're using GoogleCrap™ please read this
> http://wiki.python.org/moin/GoogleGroupsPython.
>
> Mark Lawrence
>
>
>
> ------------------------------------------------------------------------------
> Minimize network downtime and maximize team effectiveness.
> Reduce network management and security costs.Learn how to hire
> the most talented Cisco Certified professionals. Visit the
> Employer Resources Portal
> http://www.cisco.com/web/learning/employer_resources/index.html
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Hi Derek,

What are we looking at here?

The following code:

import matplotlib.pyplot as plt
import matplotlib.transforms as mtrans
import numpy as np

plt.figure()
ax = plt.subplot(111)
base_trans = ax.transData
mtx = np.array([[1,1,0],
                [0,1,0],
                [0,0,1]])
tr = mtrans.Affine2D(matrix=mtx) + base_trans

plt.plot([1,2,3], [1,2,3], 'gray', transform=tr)
plt.scatter([1,2,3], [1,2,3], c='k', marker='D', transform=tr)
plt.show()

produces the following plot on v1.2.0:
[image: Inline images 1]
Is this unexpected or are you getting a different result to me?

Regards,



On 4 April 2013 17:06, Derek Thomas <der...@gm...> wrote:

> I posted a related question on stackoverflow
> (
> http://stackoverflow.com/questions/15815862/apply-affine-transform-to-quiver-in-python-matplotlib
> )
> but I've produced a simple enough example with strange results that I
> think it merits attention here.  I'm trying to apply affine transforms
> to quiver and scatter plots.  In all cases that I've considered, the
> scatter and quiver plots transform opposite the regular plot.  Here's
> a minimal case:
>
> import matplotlib as mpl
> from pylab import figure, subplot, plot, scatter, show, axis
>
> figure()
> ax = subplot(111)
> base_trans = ax.transData
> tr =  mpl.transforms.Affine2D(matrix =
> array([[1,1,0],[0,1,0],[0,0,1]])) + base_trans
>
>
> plot( [1,2,3], [1,2,3], 'k.', transform = tr )
> scatter( [1,2,3], [1,2,3], c = 'k', marker = 'D', transform = tr )
> axis([0,7,0,7])
> show()
>
> Thanks,
>
> Derek
>
>
> ------------------------------------------------------------------------------
> Minimize network downtime and maximize team effectiveness.
> Reduce network management and security costs.Learn how to hire
> the most talented Cisco Certified professionals. Visit the
> Employer Resources Portal
> http://www.cisco.com/web/learning/employer_resources/index.html
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

On 01/04/2013 14:48, Mark Lawrence wrote:
> On 29/03/2013 15:49, Mark Lawrence wrote:
>> Hi all,
>>
>>    From http://labix.org/python-dateutil
>>
>> "To generate a rrule for the use case of "a date on the specified day of
>> the month, unless it is beyond the end of month, in which case it will
>> be the last day of the month" use the following:
>>
>> rrule(MONTHLY, bymonthday=(some_day, -1), bysetpos=1)
>>
>> This will generate a value for every calendar month regardless of the
>> day of the month it is started from."
>>
>> Using bymonthday with MonthLocator gives ticks on the day given and the
>> last day of the month, which looks extremely ugly.  Code below demonstrates.
>>
>> from dateutil.rrule import *
>> import datetime
>> import matplotlib.pyplot as plt
>> from matplotlib.ticker import FormatStrFormatter, MultipleLocator
>> from matplotlib.dates import DateFormatter, MonthLocator, DayLocator
>>
>> start = datetime.date(2013, 3, 29)
>> until = datetime.date(2014, 3, 29)
>> dates = rrule(MONTHLY, bymonthday=(29, -1), bysetpos=1, until=until)
>> for d in dates:print(d)
>>
>> dates = [start, until]
>> values = [0, 1]
>> plt.ylabel('Balance')
>> plt.grid()
>> ax = plt.subplot(111)
>> plt.plot_date(dates, values, fmt = 'rx-')
>> ax.xaxis.set_major_locator(MonthLocator(bymonthday = (dates[0].day, -1)))
>> ax.xaxis.set_major_formatter(DateFormatter('%d/%m/%y'))
>> ax.yaxis.set_major_formatter(FormatStrFormatter('£%0.2f'))
>> ax.yaxis.set_minor_locator(MultipleLocator(5))
>> plt.axis(xmin=dates[0], xmax=dates[-1])
>> plt.setp(plt.gca().get_xticklabels(), rotation = 45, fontsize = 10)
>> plt.setp(plt.gca().get_yticklabels(), fontsize = 10)
>> plt.show()
>>
>
> Seems an apt date to realise that I didn't say much :(
>
> Assuming that I'm correct would you like an issue raised on the bug
> tracker?  If not please correct the mistake I've made, presumably in
> reading the docs, which I think are excellent by the way.
>

Anybody?

-- 
If you're using GoogleCrap™ please read this 
http://wiki.python.org/moin/GoogleGroupsPython.

Mark Lawrence

I posted a related question on stackoverflow
(http://stackoverflow.com/questions/15815862/apply-affine-transform-to-quiver-in-python-matplotlib)
but I've produced a simple enough example with strange results that I
think it merits attention here.  I'm trying to apply affine transforms
to quiver and scatter plots.  In all cases that I've considered, the
scatter and quiver plots transform opposite the regular plot.  Here's
a minimal case:

import matplotlib as mpl
from pylab import figure, subplot, plot, scatter, show, axis

figure()
ax = subplot(111)
base_trans = ax.transData
tr =  mpl.transforms.Affine2D(matrix =
array([[1,1,0],[0,1,0],[0,0,1]])) + base_trans


plot( [1,2,3], [1,2,3], 'k.', transform = tr )
scatter( [1,2,3], [1,2,3], c = 'k', marker = 'D', transform = tr )
axis([0,7,0,7])
show()

Thanks,

Derek

On 4 April 2013 06:45, Sudheer Joseph <sud...@ya...> wrote:
>           Below is a sample script I got from windrose pack. I would like to place 2 windroses side by side
...
>
> from windrose import WindroseAxes
> from matplotlib import pyplot as plt
...
> def new_axes():
>     fig = plt.figure(figsize=(8, 8), dpi=80, facecolor='w', edgecolor='w')
>     rect = [0.1, 0.1, 0.8, 0.8]
>     ax = WindroseAxes(fig, rect, axisbg='w')
>     fig.add_axes(ax)
>     return ax

I'm not familiar with the windrose package, but it looks like the rect
parameter to WindroseAxes specifies the size of the generated axes in
figure co-ordinates (see
http://matplotlib.org/api/figure_api.html?highlight=add_axes#matplotlib.figure.Figure.add_axes).
You should be able to pass in a different list of co-ordinates for
each WindroseAxes to get side-by-side axes on the same figure...

Cheers,
Scott

Dear users,
          Below is a sample script I got from windrose pack. I would like to place 2 windroses side by side so that a comparison can be made. For example I have created additional variables ws1 wd1, and I would like that to be placed in the same row as a 1 row 2 column way. Any help in this regard will be great. (I tried subplot(221) subplot(222) but it do not work as the windrose uses new axis each time.)

from windrose import WindroseAxes
from matplotlib import pyplot as plt
import matplotlib.cm as cm
from numpy.random import random
from numpy import arange

#Create wind speed and direction variables
ws = random(500)*6
wd = random(500)*360
ws1 = random(500)*6
wd1 = random(500)*360
def new_axes():
    fig = plt.figure(figsize=(8, 8), dpi=80, facecolor='w', edgecolor='w')
    rect = [0.1, 0.1, 0.8, 0.8]
    ax = WindroseAxes(fig, rect, axisbg='w')
    fig.add_axes(ax)
    return ax

def set_legend(ax):
    l = ax.legend(axespad=-0.10)
    plt.setp(l.get_texts(), fontsize=8)

#windrose like a stacked histogram with normed (displayed in percent) results
ax = new_axes()
ax.bar(wd, ws, normed=True, opening=0.8, edgecolor='white')
set_legend(ax)

#Another stacked histogram representation, not normed, with bins limits
##print ax._info
plt.show()

 
***************************************************************
Sudheer Joseph 
Indian National Centre for Ocean Information Services
Ministry of Earth Sciences, Govt. of India
POST BOX NO: 21, IDA Jeedeemetla P.O.
Via Pragathi Nagar,Kukatpally, Hyderabad; Pin:5000 55
Tel:+91-40-23886047(O),Fax:+91-40-23895011(O),
Tel:+91-40-23044600(R),Tel:+91-40-9440832534(Mobile)
E-mail:sjo...@gm...;sud...@ya...
Web- http://oppamthadathil.tripod.com
***************************************************************

Hi,

Are there any library which can plot regions and boundaries given
inequalities, using matplotlib?  Inequality can be given as sympy
inequality object, function or data points.  Matplotlib has functions
to fill regions but they are too primitive for my needs.  I will
create my own library to do that using matplotlib if there is nothing
like that, but I thought I'd check it first.  Also, if you have other
forums I better post this question, please let me know (StackOverflow
maybe?).

Best,
Takafumi

Hi guys, 

 

I'm the author of
http://messymind.net/2012/07/making-matplotlib-look-like-ggplot/ which
has gained a bit of interest so I'd like to clean it up and package it
as a module to put on github. I'd like to know if I can control tick
frequency via rcparams or whether there's a way to do it better than my
current approach of

ax.xaxis.set_minor_locator(MultipleLocator((plt.xticks()[0][1]-plt.xtick
s()[0][0]) / 2.0))

This fails in a number of cases like date axes and assumes linear major
tick distribution. 

 

My other question is how should I go about having a function
automatically called on all axes prior to the figures being displayed or
saved. My current implementation requires the user to call rstyle(axis)
prior to rendering, I'd like to abstract this away.

 

Thanks in advance,

Serge.

2013/4/2 Benjamin Root <ben...@ou...>:
>

> I would suggest bringing this issue up with them (that the figure
> gets destroyed at the end of each cell).

The default behaviour of the inline backend is closing figures after cell
execution, but this is configurable[1]

That said you should be able to use the OO approach with oneliners like
this:

surf = plt.gca(projection='3d').plot_surface(...)

Or write you own pyplot-style function. Adding 3d plotting functions to
pyplot might or might not be a good thing, I can't tell. Or there might be
a separate, pyplot-like module for 3d. Does that make sense?

http://ipython.org/ipython-doc/stable/interactive/qtconsole.html#pylab-inline

Goyo

Hi listserve,

I was wondering if anyone had implemented an roipoly function for
matplotlib?  I am looking for a function that will display a plot, accept a
series of left clicks to select an arbitrary number points in a sequence,
draw the polygon as I click, and complete the polygon with a right click on
an appropriate point.  The function would return a mask array indicating
which points are inside the polygon and which are not.

Nick

On Mon, Apr 1, 2013 at 3:51 PM, Michael Aye <mic...@uc...> wrote:

> On 2013-04-01 13:45:07 +0000, Benjamin Root said:
>
> >
> > On Fri, Mar 29, 2013 at 7:30 PM, Michael Aye
> > <mic...@uc...> wrote:
> > Is there a pylab version of ax.plot_surface?
> > I am asking because the following does not work when running an ipython
> > notebook in pylab mode:
> > #0: #create some data ….
> > #1: fig = plt.figure()
> >       ax = fig.gca(projection='3d')
> > #2: surf = ax.plot_surface( …..) # taking the exact command from the
> examples.
> >
> > I have verified that this code only does NOT work when #1 and #2 are
> > executed in different notebook cells. When they are combined in the
> > same cell, it works.
> > As I prefer the flexibility of being able to run everything anywhere, I
> > am asking for pylab versions of plot_surface, as I am mostly running
> > things in the pylab mode of the notebook.
> >
> > Cheers,
> > Michael
> >
> >
> > The reason this does not work in separate cells is that a figure object
> > gets closed at the end of a ipython cell.  An ax object no longer works
> > when its parent figure is closed.  This is not limited to 3d plots.  I
> > would be surprised to see ax.plot() work if a non-3d axes object was
> > made in a different cell.
>
> Sure, but isn't that just the reason why it doesn't work the OO-way?
> That's exactly why I am asking for a pylab version of plot_surface that
> does NOT require to have a 3d axes object available already.
>
>
Huh?  This has nothing to do with the OO approach to matplotlib.  Ryan May
did a tutorial last year on the OO approach to matplotlib using ipython
notebooks.  The issue at hand is that the pylab mode of ipython loads a
special backend, IIRC, that "displays" the figure at the end of each cell.
I have found that if the figure is empty, then nothing shows, but the
figure is still destroyed.  Without a figure object (implicit or
otherwise), you can't display any new plots to the old axes regardless of
the projection.

So, what you really want is something that is not the pylab mode that
doesn't try to do special stuff under the hood.  Fernando and I have
discussed various issues surrounding the ipython's pylab mode.  I never did
get around to submitting my patches (they wouldn't have helped in your case
anyway), but I do wonder if they have made some progress in addressing this
issue.  I would suggest bringing this issue up with them (that the figure
gets destroyed at the end of each cell).

Ben Root

Maybe look into pgf.  It's slow, but looks good.

http://matplotlib.org/users/pgf.html