matplotlib-devel Mailing List for matplotlib

Hi all,
sorry, only reporting, no bugfix. I just discovered that an empty plot 
with drawstyle 'steps', 'steps-pre', 'steps-mid' and 'steps-post' fails. 
I am using matplotlib 0.98.5.2.
Example
plot([], [], drawstyle = 'steps')
...
C:\Python25\lib\site-packages\matplotlib\lines.pyc in 
_draw_steps_pre(self, renderer, gc, path, trans)
 784 def _draw_steps_pre(self, renderer, gc, path, trans):
 785 vertices = self._xy
--> 786 steps = ma.zeros((2*len(vertices)-1, 2), np.float_)
 787
 788 steps[0::2, 0], steps[1::2, 0] = vertices[:, 0], 
vertices[:-1, 0
]
...
ValueError: negative dimensions are not allowed
Gregor

Nice to hear about these plans -- and good luck with your surgery.
All that you suggest looks good. I'm personally a fan of svnmerge to do 
this sort of maintenance branch/development branch merging. You can see 
the matplotlib developer docs for instructions on how it's used with 
matplotlib, and you can just adapt the urls for what you're doing.
Mike
Ken McIvor wrote:
> Now that I've got a version of WxMpl that works properly I'd like to 
> transition it over to being a matplotlib toolkit. From poking around 
> in svn, it looks like the correct thing to do would be to import the 
> source directory into '$(SVNROOT)/trunk/toolkits/wxmpl'.
>
> Is that correct?
>
> I'd like to try to get started on version 2.0 before I have my first 
> carpal tunnel release surgery in later March. The goals would be:
>
> 1. Optional full support for MPL events
> 2. API for binding user interactions to selection and zoom behavior 
> (e.g. "I want right-click selections to zoom in and the 'u' key to 
> zoom out, like GNUPLOT")
> 3. API for controlling Axes zoom state
>
> What do you all think would be the best way to do this? Create a 
> branch in '$(SVNROOT)/branches' for 1.3 maintenance?
>
> Ken
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a 600ドル discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Thanks, Fernando. I've applied your patch to matplotlib (branch and trunk).
Mike
Fernando Perez wrote:
> On Mon, Feb 16, 2009 at 3:21 PM, Gael Varoquaux
> <gae...@no...> wrote:
>
> 
>> I am not blaming anyone, just pointing out a non ideal situation. It has
>> already improved a lot with the matplotlib guys and the scipy guys
>> merging some changes in extensions and publishing the extensions in an
>> importable part of their source tree.
>> 
>
> In keeping with the spirit of trying to get all of these extension
> changes upstream so that we can all eventually stop carrying our own
> copies, below is a tiny change I just made to the inheritance diagram
> one. This is needed to ensure that the figure is separated from any
> surrounding text, since otherwise you get hideous off-screen diagrams
> in the rendered PDF.
>
> This has been committed to the nipy trunk already.
>
> Similarly (for the pymvpa crowd), the api autogen code is now a
> module, and it also contains a few small fixes, in particular
> regarding chapter titles. Feel free to grab and update your copy:
>
> http://bazaar.launchpad.net/~nipy-developers/nipy/trunk/annotate/head%3A/tools/apigen.py
>
> I've been told the gods of numpy/sphinx don't like auto-generated
> docs, but I think there's a valid use case for these tools, so
> hopefully in the future it will be possible to include them upstream
> for us lesser mortals to use. If not, I guess we'll just continue to
> carry our copies around :)
>
> Cheers,
>
> f
>
> # diff, inline because it's so trivial:
>
> === modified file 'doc/sphinxext/inheritance_diagram.py'
> --- doc/sphinxext/inheritance_diagram.py	2009年01月30日 02:00:57 +0000
> +++ doc/sphinxext/inheritance_diagram.py	2009年02月20日 21:11:38 +0000
> @@ -370,7 +370,7 @@
>
> graph.run_dot(['-Tpdf', '-o%s' % pdf_path],
> name, parts, graph_options={'size': '"6.0,6.0"'})
> - return '\\includegraphics{%s}' % pdf_path
> + return '\n\\includegraphics{%s}\n\n' % pdf_path
>
> def visit_inheritance_diagram(inner_func):
> """
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a 600ドル discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Thanks for the note on this. It's nice to know who wrote the original 
version. I'll add a note about this in the code comments.
I'm not seeing a noticable change in this regard between 0.98.5 (which 
uses a pretty direct refactoring of your code) to the SVN trunk. The 
trunk does two things rather differently 1) it only ever returns points 
that exist in the original data, and 2) it clips line segments at the 
boundary of the plot. The latter is to get around a shortcoming of Agg 
(and Abode Reader, for that matter) when plotting lines to very 
high-valued coordinates.
But, I'd appreciate you having a comparison look yourself, in case 
you're seeing some detail that I'm missing.
Cheers,
Mike
Allan Haldane wrote:
> a writes:
> 
>> Michael Droettboom <mdroe@...> writes:
>> 
>>> Thanks for the pointers.
>>>
>>> The original simplification code was written by John Hunter (I believe),
>>> and I don't know if it was designed by him also or is a replication of
>>> something published elsewhere. So I take no credit for and have little
>>> knowledge of its original goals.
>>> 
>> I'm not sure on everything it does, but it seems to do clipping and removes
>> line segments where the change in slope is less than some limit. There are
>> probably better algorithms out there, but this one works surprisingly well
>> and is fast and simple. I think it should be a requirement that it returns
>> points which are a subset of the original points- with the change you've
>> made it does this, right?
>> 
>
> Oh Hey! I'm the one who originally wrote the path simplification code. I'd
> have thought it would be gone by now, but I am very happy it turned out to
> be useful. I made it up in order to plot a very large set of noisy data I
> had.
>
> The goal was to simplify two types of plots at once: Smooth curves, as
> well as very noisy data where many lines are 'on top' of each other. (eg
> plot(rand(100000)) ). I noticed both could be taken care of by checking
> for changes in slope.
>
> An important goal (for me) was making sure that the min/max span of the
> points plotted was preserved. (so that eg plot(rand(1000)) spans from the
> lowest to highest point in the data (ie ~ 0 to 1) for any zoom factor).
> I'm not sure if this property survived...: If you do plot(rand(1000)) with
> the latest matplotlib and gradually zoom out on the x axis, you can see
> the top/bottom tips of the plotted line flickering in height, which is
> what I was trying to avoid. I forget whether I actually got it as I wanted
> it though, maybe I gave up.
>
> Allan
>
>
>
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a 600ドル discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA