Ah, yes. The code was written with the assumption that the paths were treated as filled (which doesn't really matter whether they are closed or not). I have added a "filled" kwarg to Path.intersects_path and Path.intersects_bbox that when True treats the path(s) as filled, and when False does not. In order to not change existing functionality, this argument defaults to "True". To resolve Evan's problem, one would now explicitly pass "filled=False" to intersects_bbox.
Cheers, Mike Eric Firing wrote: > Michael Droettboom wrote: >> I just added a test of intersects_bbox to SVN that seems to be >> working correctly for short paths containing masked values. It would >> appear that masked values *should* be dealt with correctly (that is, >> in exactly the same way as they are drawn) by the intersection code. >> However, there is probably a side case here that I'm missing. As >> Eric suggests, see if you can break it down into a simple example >> that fails and hopefully the problem and/or solution will be more >> obvious from that. > > Mike, > > I was wrong; it has nothing to do with masked values. It is much > simpler: it appears that for the purpose of this test, the path is > being treated as if it were closed. See attached. I think this > accounts for Evan's mis-identified tracks. > > Eric > -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
