matplotlib-devel Mailing List for matplotlib

I also ran into this problem recently and was disappointed to find that the
notch was based on a normal approximation.
While there are a number of ways to calculate the notch size, it would be
useful to allow the user to supply (either as an optional keyword, or as a
vector input for the notch keyword) their own notch locations. 
For example, I have some code that calculates bootstrapped confidence
intervals - in the case of a significantly non-normal distribution this
would be a better way to find the notch boundaries (which will likely not
even be symmetric). While I'm not advocating building other calculations in,
having the option to supply my own notch locations would be immensely
useful. The default should probably remain as is (IMO) but should also be
mentioned in the documentation as being based on that assumption.
I'm happy to submit an update to do just that if it's seen as a good idea.
Steve.
Andrew Straw wrote:
> 
> Andrew Straw wrote:
>> Also, I think that formula is only for normally distributed data. Which, 
>> especially if you're using boxplots, medians, and quartiles, may not be 
>> a valid assumption.
>>
>> Maybe we should at least raise a warning when someone uses notch=1. The 
>> current implementation seems dubious, at best, IMO.
>> 
> 
> (I sent the previous version of this email a bit too early -- this is
> slightly edited for clarity.)
> 
> I read the following reference:
> 
> McGill, R., Tukey, J.W., and Larsen, W.A. (1978) "Variations of
> Boxplots", The American Statistician, 32:12-16.
> 
> McGill et al. have an entire section devoted to "Choice of Notch Size",
> starting with:
> 
> "In notched box plots, one is, of course, faced with the question of how
> best to determine the widths of the notches. Many methods, both
> classical and non-parametric, might be considered. None will likely be
> best in all cases."
> 
> ...
> 
> 
-- 
View this message in context: http://old.nabble.com/boxplot-notch-tp26798967p27249739.html
Sent from the matplotlib - devel mailing list archive at Nabble.com.

Greetings,
I recently recreated my development environment on my windows machine and
have attempted to build MPL off the SVN trunk. I am able to successfully
compile and build windows installers using both Python 2.5.4 and Python
2.6.4 using MinGW. However, when I install my builds and try to use them I
have some issues.
First, I was unable to build MPL using libpng-1.4.0. I was forced to revert
to libpng-1.2.40
Python 2.5.4
1. After successfully building MPL with GTK support (Yes - I can import GTK
in my Python interpreter with no problems.), I am unable to show or save
figures using MPL. Using IPython, I was able to create the figure instance
but Python quits when trying to display or save said figure instance.
2. After rebuilding MPL without GTK support, I get the same errors.
Python 2.6.4
1. I am able to display figure instances using MPL build with GTK support.
 However, when I try to save the figure (in any format) Python quits.
2. I get the same behavior when I build MPL without GTK support.
I have tried building MPL by building the dependencies myself and also with
using the win32_static/win32_static_mingw32 folders and get the same issues
either way. I am hoping whoever is responsible for building the windows
binaries is willing to work with me to solve these issues. I'd like to be
able to build MPL successfully using both Python 2.5.4 and Python 2.6.4 and
then write up a detailed How-To build on Windows.
Any help would be appreciated.
Thanks,
Patrick
-- 
Patrick Marsh
Ph.D. Student / Graduate Research Assistant
School of Meteorology / University of Oklahoma
Cooperative Institute for Mesoscale Meteorological Studies
National Severe Storms Laboratory
http://www.patricktmarsh.com

Hi,
 I do see strange behavior when using "Zoom to rectangle"
on my figures embedded in gtk through glade.
When clicking on the figure and start drawing the rectangle,
the bottom axis moves up as well as the graph which screw up
the whole figure during the rectangle definition. When releasing
the mouse button the figure looks ok.
I attach a small script together with glade file (slightly modified
from the matplotlib examples) that allows to reproduce the problem:
 -> launch the script, press the "Zoom to rectangle button" and start
drawing the rectangle region on the graph, you will see the issue...
It as to be noticed that pure gtk version (without glade) does work
properly.
I'm on MacOsX 10.5.8 using gtk.gtk_version (2, 18, 6)
and gtk.pygtk_version (2, 16, 0) with python 2.6
Hope someone could help me solving this annoying issue.
Regards,
David