On Oct 15, 2009, at 2:14 AM, kenji wrote:
Hi, Daniel and Jonathan, thanks your suggestions
Does matplotlib (pylab) work effectively
Yes. pylab.show() works perfectly. But pylab.show() is a function
that should
be called lastly because it doesn't return.
True, although I note that's how you're using mlab in appendix1.
I have used pylab only as a graph viewer, not as an animation
viewer. I guess
that if an animation viewer is needed then I have to use matlab
directly, not
to use pylab front end indirectly.
I don't know whether it's an issue of matplotlib vs. pylab or whether
it's an issue of backends. I think it's the latter, but it's an issue
best taken up with matplotlib's developers. I will say that I did not
used to be able to control Z order or move matplotlib windows on the
Mac while FiPy was solving, but since they introduced the MacOSX
backend, it works fine for me.
But I don't need animation viewers and fipy perfectly separates
solver from
viewer. So I can use other modules as in appendix1 or appendix2 to
view
results calculated by fipy solvers .
As a post-processor, I agree that it doesn't matter as much, although
I would caution you not to rely on
arAt = sc.array(phi).reshape(nx,ny)
always working. We do not promise any particular data ordering.
I'm curious, though; you seem to be using your sf.plotGr(..) as an
animating viewer (updating while the simulation is evolving). If this
viewer works for you on Windows, we would certainly welcome that
contribution to FiPy.
It might be easier for me to abandon animation viewers and to use
other
viewers than to find out the counter measures using the fipy viewer
in Win2k.
Since you have mayavi installed, I will tell you that I've implemented
MayaviViewer that runs as a separate process, which allows complete
interaction with the viewer; at a bare minimum, it should certainly
enable you to control Z ordering of its window.
