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
Fvtk 2.0 PR1 #587
Fvtk 2.0 PR1 #587
Conversation
…n recording becomes too fast
Oh no - wait - you're right. There's one: "No VTK for these tests" in there Let me double check again... On Thu, Oct 29, 2015 at 7:24 PM, Ariel Rokem arokem@gmail.com wrote:
|
OK - I am about ready to say that we can't test some of these things on If you rebase this on master, I can make a PR against your branch with the On Thu, Oct 29, 2015 at 7:45 PM, Ariel Rokem arokem@gmail.com wrote:
|
Run xvfb with screen server-arg
Don't use xvfb in the call to nosetests. Only test the one we are interested in for now. I guess it needs to be included to actually run? Copy over this decorator to test_fvtk_widgets to get it running under xvfb. Are we there yet?
Fvtk2 travis
Add another bot to test on vtk6
…window appears) depth peeling is not supported but if you allow for a quick window to appear then transparent ordering works fine.
…ut it works fine in standard displays. Added if statement to deal with this issue
TST: Add python-imaging
…pdated fast enough
Congratulations @Garyfallidis! A new era of diffusion MRI visualization! |
Let's start making some smaller viz PRs from now on. 👍 |
+1 On Sun, Nov 1, 2015 at 2:04 PM, Eleftherios Garyfallidis <
|
This will make you happy @arokem and @stefanv! Moving forward with the visualization capabilities of DIPY!!! The PR is ready for a review.
This pull request introduces a new API for visualization.
Here are the main characteristics:
a) Allows for testable screenshots and renderers. Which is crucial for quality assurance.
b) It contains 3 main modules (window, actor and widget). These are replacing the current fvtk module but fvtk can be used too for backwards compatibility.
c) In window we have everything related to windowing, rendering and saving screenshots.
d) In actor you will find the actors for lines and streamtubes etc. Not everything has moved yet from fvtk.py so that the PR doesn't become too large. But all actors should move in the next PRs.
e) In widget we have buttons and sliders which can be used directly from inside OpenGL/VTK. No new dependencies.
d) You can save and open file dialogues using Tk which is ported together with Python. No new dependencies.
f) Because they are a lot of new concepts and ideas in this PR I wrote 4 tutorials to help the reviewing process.
Let me know what you think.