Re: [Discuss-gnuradio] matplotlib runtime error

2014-05-18 Thread Activecat
On Mon, May 19, 2014 at 12:52 AM, Tom Rondeau wrote: > On Sun, May 18, 2014 at 9:00 AM, Marcus Müller > wrote: > >> Hi, >> I think real-time and matplotlib kind of contradict in the first place - >> really, matplotlib's performance is terrible. As a rule, it's Assisi >> generally a bad idea to l

Re: [Discuss-gnuradio] matplotlib runtime error

2014-05-18 Thread Tom Rondeau
On Sun, May 18, 2014 at 9:00 AM, Marcus Müller wrote: > Hi, > I think real-time and matplotlib kind of contradict in the first place - > really, matplotlib's performance is terrible. As a rule, it's Assisi > generally a bad idea to let your data file update your GUI. Usually, you > want something

Re: [Discuss-gnuradio] matplotlib runtime error

2014-05-18 Thread Marcus Müller
Hi, I think real-time and matplotlib kind of contradict in the first place - really, matplotlib's performance is terrible. As a rule, it's Assisi generally a bad idea to let your data file update your GUI. Usually, you want something like a check every tenth of a second, if data has arrived, and

Re: [Discuss-gnuradio] matplotlib runtime error

2014-05-08 Thread Tom Rondeau
On Thu, May 8, 2014 at 3:30 AM, Activecat wrote: > > On Fri, May 2, 2014 at 8:56 PM, Tom Rondeau wrote: > >> On Fri, May 2, 2014 at 8:49 AM, Marcus Müller >> wrote: >> >>> Hi Activecat, >>> >>> typical GUI problem; background is that X applications are inherently >>> hard to multithread, which

Re: [Discuss-gnuradio] matplotlib runtime error

2014-05-08 Thread Activecat
On Fri, May 2, 2014 at 8:56 PM, Tom Rondeau wrote: > On Fri, May 2, 2014 at 8:49 AM, Marcus Müller wrote: > >> Hi Activecat, >> >> typical GUI problem; background is that X applications are inherently >> hard to multithread, which basically requires graphical toolkits to run in >> a main loop. Th

Re: [Discuss-gnuradio] matplotlib runtime error

2014-05-02 Thread Tom Rondeau
On Fri, May 2, 2014 at 8:49 AM, Marcus Müller wrote: > Hi Activecat, > > typical GUI problem; background is that X applications are inherently hard > to multithread, which basically requires graphical toolkits to run in a > main loop. This conflicts with every block being run in its own thread. >

Re: [Discuss-gnuradio] matplotlib runtime error

2014-05-02 Thread Marcus Müller
Hi Activecat, typical GUI problem; background is that X applications are inherently hard to multithread, which basically requires graphical toolkits to run in a main loop. This conflicts with every block being run in its own thread. The easiest solution nowadays should be that you generate a QT f

[Discuss-gnuradio] matplotlib runtime error

2014-05-02 Thread Activecat
Gurus, I try to transfer an image file via a pair of USRPs. At the receiver side, the data is fed into a custom block, where it plots the image in realtime using matplotlib's pyplot.imshow(). Unfortunately, in the work() function, the pyplot.draw() causes below runtime error. handler caught excep