New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
scenes in Jupyter notebook are interleaved #452
Comments
have you tried creating a new figure in the new cell? |
I did this Is it a bug or it's a feature? So should I clear the figure in all my scripts now? |
@thoth291 -- This is the same as what you'd see without the notebook. |
Am closing this issue for now as this is not an issue but how mlab works. |
Unfortunately I'm not the one who did the setup.
This setup works perfectly for us and the only thing which is annoying is that you have to keep remember to prepend this vnc3d script to your command each time you deal with OpenGL... |
@prabhuramachandran , I think this is counter intuitive for Jupyter users. Or at least it should be documented explicitly that one need to do it ( |
@prabhuramachandran , I think this is counter intuitive for Jupyter users.
I have the same feeling.
|
@thoth291 -- thanks for the information on the VirtualGL setup. That looks very interesting and useful. As regards the |
Yeah, that's the confusing part. May be it worth to put a new argument to init_notebook call when user can define what to do. I can imagine that many mlab users would be just fine having figures interleaving (so that they can gradually build a scene) - but the default behavior should be to have independent figures for each cell. |
Hi all, sorry for adding things to this closed issue but I thought this would be a good opportunity to give some feedback to the project. So to recap: different matplotlib backends behave differently with respect to new figure creation. From a user's point of view, it would easier if figures were tied to cells. However, if one follows the %matplotlib notebook suggestion, one could follow this workflow: fig = mlab.figure() # create new figure
s = mlab.test_triangular_mesh() # draw something on it
fig # display figure This actually works, so maybe something worthwhile would be to reformat the example notebook with this way of working, as well as the tips and tricks section which documents jupyter notebooks (http://docs.enthought.com/mayavi/mayavi/tips.html). At any rate, I would like to add that I think it's great that this backend exists. Thank you for the hard work @prabhuramachandran @GaelVaroquaux ! Best regards, |
When I plot one scene after another in my jupyter notebook with with x3d backend - this happens:
What should I do in order to prevent this? (I assume that you see the mesh from Out[2] in the center of the mesh in Out[8])
P.S. May be that's important - I'm running my jupyter notebook server on the remote machine under VirtualGL.
The text was updated successfully, but these errors were encountered: