Re: [matplotlib-devel] Passing errorbar width arguments to bar/barh ?

2010-06-03 Thread Fernando Perez
On Wed, Jun 2, 2010 at 1:44 PM, Eric Firing efir...@hawaii.edu wrote: Done in svn 8369.  Its usage is illustrated in barchart_demo.py. Partially following your lead with subplots, I spelled it error_kw. Fabulous, much appreciated! Regards, f

Re: [matplotlib-devel] Passing errorbar width arguments to bar/barh ?

2010-06-02 Thread John Hunter
On Wed, Jun 2, 2010 at 8:01 AM, John Hunter jdh2...@gmail.com wrote: While this is certainly a bug that needs to be fixed (and Eric is right that these functions are heavily overworked and hairy), there is a better workaround than the one you tried.  From the errorbar docstring: Ignore me

Re: [matplotlib-devel] Passing errorbar width arguments to bar/barh ?

2010-06-02 Thread Benjamin Root
I am curious as to why bar() should even be acting like errorbar(). As a user, I would expect bar() to do bar graphs and errorbar() to do error bar graphs. Is there some sort of use-case that I am missing where it makes sense to generate errorbars from a bar() function? Ben Root On Wed, Jun 2,

Re: [matplotlib-devel] Passing errorbar width arguments to bar/barh ?

2010-06-02 Thread John Hunter
On Wed, Jun 2, 2010 at 9:48 AM, Benjamin Root ben.r...@ou.edu wrote: I am curious as to why bar() should even be acting like errorbar().  As a user, I would expect bar() to do bar graphs and errorbar() to do error bar graphs.  Is there some sort of use-case that I am missing where it makes

Re: [matplotlib-devel] Passing errorbar width arguments to bar/barh ?

2010-06-02 Thread Eric Firing
On 06/01/2010 03:33 PM, Fernando Perez wrote: On Tue, Jun 1, 2010 at 4:35 PM, Eric Firingefir...@hawaii.edu wrote: it seems to me that the solution is for bar to take a kwarg, say errorkw, which is a dict that will be passed to errorbar via **errorkw, and that can have any valid errorbar

Re: [matplotlib-devel] Passing errorbar width arguments to bar/barh ?

2010-06-02 Thread Benjamin Root
On Wed, Jun 2, 2010 at 10:26 AM, John Hunter jdh2...@gmail.com wrote: On Wed, Jun 2, 2010 at 9:48 AM, Benjamin Root ben.r...@ou.edu wrote: I am curious as to why bar() should even be acting like errorbar(). As a user, I would expect bar() to do bar graphs and errorbar() to do error bar

[matplotlib-devel] Passing errorbar width arguments to bar/barh ?

2010-06-01 Thread Fernando Perez
Hi all, I just spent some time digging through the matplotlib code, and I see that the errorbar line width argument isn't passed through to the underlying call. In axis.bar, we have this code: if xerr is not None or yerr is not None: if orientation == 'vertical':

Re: [matplotlib-devel] Passing errorbar width arguments to bar/barh ?

2010-06-01 Thread Eric Firing
On 06/01/2010 01:17 PM, Fernando Perez wrote: Hi all, I just spent some time digging through the matplotlib code, and I see that the errorbar line width argument isn't passed through to the underlying call. In axis.bar, we have this code: if xerr is not None or yerr is not None:

Re: [matplotlib-devel] Passing errorbar width arguments to bar/barh ?

2010-06-01 Thread Benjamin Root
I just took a look at bar() and errorbar(). bar() has linewidth and uses it properly (I believe), except in the case where one specifies yerr/xerr (it doesn't pass on kwargs nor does it apply the linewidth parameter). Then looking at errorbar(), there is a kwarg called 'elinewidth' which

Re: [matplotlib-devel] Passing errorbar width arguments to bar/barh ?

2010-06-01 Thread Fernando Perez
On Tue, Jun 1, 2010 at 4:35 PM, Eric Firing efir...@hawaii.edu wrote: it seems to me that the solution is for bar to take a kwarg, say errorkw, which is a dict that will be passed to errorbar via **errorkw, and that can have any valid errorbar kwargs in it.  There is some precedent for this