- Notifications
You must be signed in to change notification settings - Fork 536
New interface for Camino dtshape. #704
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
Importantly, i would like to reorganize the Camino interfaces. One of NiPype's great functionality is to facilitate the switch from any software package to another having the same functionality. However several Camino interfaces are mis-categorized, especially the dti.py submodule containing several interfaces (tracking, etc.) which would highly benefit from being allocated to other Camino submodules (tracking.py, etc.). This would be especially useful to see the associated new reorganization in the documentation and make it much easier for new and old NiPype users to switch diffusion MRI interfaces from one package to another. For example switching from a Camino ODF reconstruction (from the odf.py camino submodule i previously created) to an ODF in the MRtrix submodule, switching from one tracking interface to a Camino tracking interface that i would move to a dedicated tracking submodule, etc. |
@satra @chrisfilo what do you think? |
@mick-d - i think that reorganizing the interfaces will be useful. so please do send a PR on that. |
nipype/interfaces/camino/dti.py Outdated
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.
pep8
@satra would it be possible to merge this? I thought it was already merged when i submitted this new PR but luckily this commit is on the same interface. |
@mick-d - could you enable linking your github account to travis: goto settings on the right in your nipype github page and the click service hooks on the left and the click the check box next to Travis. this will automatically run the nipype test suite whenever you push to your repo. |
@satra sorry for the slow reply (ISMRM deadline). I enabled Travis. Before submitting again i run nosetests (which i already run before submitting this PR the first time) but this time got one error, i do not understand why:
Where does the DESIRED component come from? I do not see anything relative to this desired component in the ComputeEigensystem Camino interface (dti.py) so i don't know how to correct this. How to fix this? |
Nipype now auto generated tests. This likely means you changed a trait. Do a make check-before-commmit in the nipype source directory. It will fix the test. |
Thanks Satra, what commands should I run for a check before commit? (Sorry never heard of that before) |
it's actually
|
@satra the |
could you run make test now? i suspect it has changed the autogenerated file and the tests will now pass. so you need to commit and push that change. |
I had indeed to commit and push again (i don't understand why) and |
Ok i understand, the tests change the whitespaces. But then |
it should have also changed: test_auto_ComputeEigensystem.py these are autogenerated tests and the |
Thanks for your help Satra. Unfortunately |
I can confirm same error after running |
After rebasing, making 100% sure everything is in line with nipype/master (except for dti.py) still same error with |
I tried many things but i'm in a clean state and still same error. I'm totally stuck. |
trying to figure out what's happening
|
@satra do you have any idea of what may be going wrong? |
Should be good to go now! This was a lot of work for the DTMetric interface. Many thanks for your help Satra. |
New interface for Camino dtshape.
Minor correction to Camino ComputeEigensystem which required renaming the same test file in several interfaces.