Closed GoogleCodeExporter closed 9 years ago
Did you mean line 41/42? Please quote the line as well, because I can hardly
image you mean "line1 = vv.plot(x, y, ms='.', mw=4, lw=2)".
Original comment by almar.klein@gmail.com
on 14 Dec 2012 at 7:07
sorry, my mistake. I wanted to say lines 15/16:
texture2d = vv.imshow(im)
texture2d.interpolate = True # if False the pixels are visible when zooming in
actually the second line never gets called...
Original comment by christop...@gmail.com
on 15 Dec 2012 at 2:26
I suspected it was the 3D volume being rendered in software. But it's the 2D
texture? Strange ...
So if you comment these two lines the example works fine, and you see a volume
too?
Can you try running just:
vv.imshow(vv.imread('lena.png'))
Original comment by almar.klein@gmail.com
on 15 Dec 2012 at 3:05
Yes, when I comment those lines the entire program works fine and I get the
3D rendered pot and the lines that were supposed to go on top of the 2D
texture. Everything works interactive.
the mouse pointer moving) I have to hard shut down.
Original comment by christop...@gmail.com
on 16 Dec 2012 at 7:07
I think some lines did not make it when you send your previous comment.
Original comment by almar.klein@gmail.com
on 16 Dec 2012 at 11:02
Can you print "im.shape" for me, just to be sure?
Original comment by almar.klein@gmail.com
on 16 Dec 2012 at 11:04
In [2]: import visvis
In [3]: im=visvis.imread('/Users/christoph/Desktop/China/P1090293.jpg')
In [4]: im.shape
Out[4]: (3072, 2304, 3)
In [5]:
Original comment by christop...@gmail.com
on 17 Dec 2012 at 11:35
It's still a bit unclear to me ...
Is this the image on which your system hangs? And does it also hang on the Lena
image?
(vv.imread('lena.png') should just work, because the image comes with visvis.)
Original comment by almar.klein@gmail.com
on 18 Dec 2012 at 8:30
sorry, i was installing from pip and did not look for the examples and
resources folder. That's why I used the code from the web site and my own
image.
Running examples/overview.py gives the same hang.
Original comment by christop...@gmail.com
on 18 Dec 2012 at 4:58
Did you say you have to reboot when it happens? This makes testing a bit
awkward. I'll throw some ideas at you. If you feel like testing them, that
would be great. If not, no hard feelings.
You say your whole interface hangs, this smells like a shader program running
for a long time. This would be weird though, as the shader for 2D textures is
not nearly as performance intensive as that for the 3D texture.
Could you try with the shading turned off:
import visvis as vv
im = vv.imread('lena.png')
t = vv.imshow(im)
t.shader._program._usable = False # Turns shader off
app = vv.use()
app.Run()
Run this as a script. Not line by line, otherwise the line following imshow
won't have a chance to execute.
Original comment by almar.klein@gmail.com
on 19 Dec 2012 at 10:17
As you said, I am not very keen on doing a lot of experiments. Hard shutdowns
are nothing nice. Anyway, if I get bored at some point, I will try what you
propose. Yet I find it weird that a library that is part of the OS can make the
entire interface hang... maybe I should file a ticket with apple...
but I like your vvmovie package (which is what I wanted, when I installed your
library in the first place). Nice work.
Cheers,
Christoph
Original comment by christop...@gmail.com
on 20 Dec 2012 at 5:00
Note that the vvmovie part will probably be moved to imageio
(imageio.readthedocs.org) at some point.
Original comment by almar.klein@gmail.com
on 20 Dec 2012 at 10:55
I am now running visvis 1.8 on Python 2.7.3 64bits, Qt 4.8.4, PyQt4 (API v2)
4.9.4 on Darwin. It seems like things have been fixed (somehow...) thanks for
the nice package.
Original comment by christop...@gmail.com
on 16 May 2013 at 10:17
Great! Marking as fixed.
Original comment by almar.klein@gmail.com
on 17 May 2013 at 7:29
Original issue reported on code.google.com by
christop...@gmail.com
on 14 Dec 2012 at 4:38