-
Notifications
You must be signed in to change notification settings - Fork 532
[ENH] Refactor VTK and tvtk -based interfaces #973
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
Conversation
Hi @satra, I think this is now like the matplotlib backend configuration but it doesn't look like working out... It seems it's not set when pipelines are included in the |
Conflicts: nipype/pipeline/plugins/base.py
try: | ||
import matplotlib | ||
matplotlib.use('%s') | ||
except ImportError: | ||
can_import_matplotlib = False | ||
pass | ||
except |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what's with this lone "except"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's ugly :( (deleting...).
Thanks for spotting it :)
Could you add info about this variable to the docs? http://nipy.org/nipype/users/config_file.html |
I would not merge this though, I think they are changing this in ETS. I have to check before merging. |
any updates on this? |
I think I'm closing this PR. First of all, in ETS this 'null' plugin is changing its place. Second, even with this config, initialization was not working ok. If somebody else reports problem with ETS, then I will check on this again. |
Conflicts: CHANGES nipype/algorithms/mesh.py nipype/algorithms/tests/test_mesh_ops.py
* upstream/master: Correct versions and consistency in install.rst fix:import utils needed one more dot fix: absolute to relative imports add vtk version checking in fsl interfaces update CHANGES Fix nipy#1218 only, not addressing nipy#973 force setting ETS_TOOLKIT before tvtk nipy#972 Created TVTKBaseInterface. Should fix nipy#1218
Conflicts: CHANGES nipype/algorithms/mesh.py
desc=('Name of file containing initial warp-fields/coefficients (follows premat). This could e.g. be a ' | ||
'fnirt-transform from a subjects structural scan to an average of a group ' | ||
'of subjects.')) | ||
desc='Name of file containing initial warp-fields/coefficients (follows premat). This could e.g. be a ' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are you sure, this works? without the parenthesis? can you check the doc rendering as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed the parenthesis because they raised a pylint warning
Hi @satra, I've been fighting with the settings of VTK6 and the mayavi version you suggested. I am reaching to the conclusion that the effort is not worth (yet). Caveats:
We can move on trusty, and simplify the travis settings, but anyways it has to be on python 2. Should I revert back the code (in the end, it was working before), save the current config to a gist and update it when VTK supports python 3? |
@satra, I finally reverted back the travis config file. I think we should wait for support of python 3 in VTK. In the meantime, this is good to check that it works also without VTK |
some conflicts have risen with all the code that has been merged. @oesteban - do you mean we need to check that it works without VTK? or that you have already checked? |
When python is 2 then the vtk is installed and explicit regression tests (no auto tests) are done. If python is 3 vtk is not installed, and we test that this does not cause any problem. |
Is this ready to go? I would need to merge this before the inputs/outputs refactoring. I finally stalled #1240 and continued outside that PR because the changes were huge. If you want to have a sneak peek on how things are, I am working on this branch: https://github.com/oesteban/nipype/tree/enh/DerivationOfInterfacesRefactoring. This branch could mean a jump to v. 1.5 or similar (I would reserve 2.0 for a version including the workflow patterns). If this branch was merged, then I will withdraw #1240 and #882 since they will not make any sense (for the interfaced workflows, with the new code it will be rather easy to produce the pattern). |
[ENH] Refactor VTK and tvtk -based interfaces
@oesteban - we have merged a bunch of PRs without making any changes to the CHANGES file. can we update it for at least the major ones. |
This PR has ended up as follows:
nipype.interfaces.vtkbase
to encapsulate it).algorithms.mesh
andinterfaces.fsl.utils
.ETS_TOOLKIT=null
(headless operation) before loading tvtk, then leave environment as it was before (close Enthought Tool Suite configuration #972).