From: Jorge S. <jor...@ya...> - 2011-02-05 00:30:22
|
Hi, I have some code that's been working for a long time, but it's behaving strange with current (svn) matplotlib. It's too large to post here, so I will try to come up with a minimal version reproducing the problem. Meanwhile, I wanted to ask if anyone would have a clue of what could be going on. The symptoms are that the interaction (keys and mouse clicks) works OK as long as I don't resize the window. Once I do this, the interaction is gone. What happens when the window is resized, that could be related to what I experience. OK, lets see if I can come up with a simple code reproducing this... jorges |
From: Jorge S. <jor...@ya...> - 2011-02-05 18:38:27
|
Jorge Scandaliaris <jorgesmbox-ml@...> writes: < snip > > > The symptoms are that > the interaction (keys and mouse clicks) works OK as long as I don't resize the > window. Once I do this, the interaction is gone. What happens when the window > is > resized, that could be related to what I experience. > > OK, lets see if I can come up with a simple code reproducing this... > I couldn't come up with a simple example showing the problem. My attempts so far ended in working examples. I did find a change in my code that triggers the problem: My code uses a modified version of the lasso_demo example, contains two axes, where I draw an image with imshow and a collection of circles with scatter. Originally scatter was called with a fixed size for all points, and I just changed it so each points gets a different size. Just don't ask me why this seemingly innocent change affects (breaks) the event handling. I hope somebody can give me some hints. I'll keep checking the code to see if I find anything suspicious. jorges |
From: Jorge S. <jor...@ya...> - 2011-02-07 19:39:31
|
Jorge Scandaliaris <jorgesmbox-ml@...> writes: < snip > > I couldn't come up with a simple example showing the problem. My attempts so > far > ended in working examples. I did find a change in my code that triggers the > problem: My code uses a modified version of the lasso_demo example, contains > two > axes, where I draw an image with imshow and a collection of circles with > scatter. Originally scatter was called with a fixed size for all points, and I > just changed it so each points gets a different size. > > Just don't ask me why this seemingly innocent change affects (breaks) the > event > handling. I hope somebody can give me some hints. I'll keep checking the code > to Because I couldn't reproduce the problem on simple examples, and also because I have time constraints related to my work, I decided to go on ignoring this problem (I can always avoid resizing windows...). This afternoon, I realized that the problem had not appeared during the whole day, but then realized that because I was debugging some changes introduced in my code, I had been using very small images. After switching back to normal sizes, the problem came back. So, I modified the lasso_demo, increasing progressively the number polygons drawn. When I reached 100000 polygons, I was able to reproduce the problem. It's true that this a rather large number, but in my code it happens well below this number, maybe because I assign a different color and size to each polygon. So my previous observation that setting different sizes triggered the problem might not be the real picture. It seems as if I was hitting some sort of limit. Anyone would have a clue about what could be happening, or how can I try to debug this? Thanks, jorges |
From: Jorge S. <jor...@ya...> - 2011-02-08 01:09:43
|
Jorge Scandaliaris <jorgesmbox-ml@...> writes: < snip > > So, I modified the lasso_demo, increasing progressively the number polygons > drawn. When I reached 100000 polygons, I was able to reproduce the problem. > It's > true that this a rather large number, but in my code it happens well below this > number, maybe because I assign a different color and size to each polygon. So > my > previous observation that setting different sizes triggered the problem might > not be the real picture. It seems as if I was hitting some sort of limit. > > Anyone would have a clue about what could be happening, or how can I try to > debug this? > Well, I am bit desperate. The event problem definitely is related to the number of polygons, circles, ellipses I draw, as well as to using different colors and sizes. I don't even know how to start debugging this. One step forward, though, is that I checked running the script directly from python, instead of within ipython, and it is running as it should. This is with more than 300 thousand ellipses, whereas within ipython it stops working with as little as 2 thousand ellipses. I am running both matplotlib and ipython development trees. Any expert on how events work out there? And mpl-inpython interaction? Thanks for any hints/suggestions. jorges |
From: Benjamin R. <ben...@ou...> - 2011-02-08 02:01:21
|
On Mon, Feb 7, 2011 at 7:09 PM, Jorge Scandaliaris <jor...@ya...>wrote: > Jorge Scandaliaris <jorgesmbox-ml@...> writes: > > < snip > > > So, I modified the lasso_demo, increasing progressively the number > polygons > > drawn. When I reached 100000 polygons, I was able to reproduce the > problem. > > It's > > true that this a rather large number, but in my code it happens well > below this > > number, maybe because I assign a different color and size to each > polygon. So > > my > > previous observation that setting different sizes triggered the problem > might > > not be the real picture. It seems as if I was hitting some sort of limit. > > > > Anyone would have a clue about what could be happening, or how can I try > to > > debug this? > > > > Well, I am bit desperate. The event problem definitely is related to the > number > of polygons, circles, ellipses I draw, as well as to using different colors > and > sizes. I don't even know how to start debugging this. > > One step forward, though, is that I checked running the script directly > from > python, instead of within ipython, and it is running as it should. This is > with > more than 300 thousand ellipses, whereas within ipython it stops working > with as > little as 2 thousand ellipses. > > I am running both matplotlib and ipython development trees. > > Any expert on how events work out there? And mpl-inpython interaction? > > Thanks for any hints/suggestions. > > jorges > > > Hmm, interesting observation. There is very little in mpl that limits your ability to produce elements for plotting (which is probably why you were getting shrugs from the mailing list...). However, ipython has various "tricks" for caching mpl elements, and can sometimes be a bit excessive in memory usage. This could lead to some issues. Now that you have identified ipython as the culprit, I would suggest taking this to the ipython list and seeing if they can better identify the problem for you. Ben Root |
From: Jorge S. <jor...@ya...> - 2011-02-08 07:56:20
|
2011/2/8 Benjamin Root <ben...@ou...> > > > Hmm, interesting observation. There is very little in mpl that limits your > ability to produce elements for plotting (which is probably why you were > getting shrugs from the mailing list...). However, ipython has various > "tricks" for caching mpl elements, and can sometimes be a bit excessive in > memory usage. This could lead to some issues. > > Now that you have identified ipython as the culprit, I would suggest taking > this to the ipython list and seeing if they can better identify the problem > for you. > > Ben Root > > Thanks, I was thinking of doing that myself. jorges |