-
Notifications
You must be signed in to change notification settings - Fork 533
Inital commit to add niftyfit interfaces #1910
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
Codecov Report
@@ Coverage Diff @@
## master #1910 +/- ##
=========================================
+ Coverage 72.15% 72.2% +0.04%
=========================================
Files 1117 1130 +13
Lines 56456 56918 +462
Branches 8112 8140 +28
=========================================
+ Hits 40736 41095 +359
- Misses 14443 14539 +96
- Partials 1277 1284 +7
Continue to review full report at Codecov.
|
Hi @byvernault all the tests seem to be passing in our settings as well. I also went through the code quickly and overall it looks really good. We are right now in a Nipype workshop for this week so we may not find time for the deep review this deserves, but I'm sure we can get this merged over the next two weeks. Thanks a lot, this is a really valuable contribution and I'm sure it will expose Nifty- tools to a good bunch of new users. |
Hi, I think we are finally good with this branch to add niftyfit interface to nipype. Let me know if you have any question. Kind Regards, |
…n input to select which one to generate.
Hi guys, Thank you for pulling niftyreg and niftyseg request to nipype. Let me know if you think there is other changes to do. Thanks for all your help. Kind Regards, P.S: BTW, do you have an idea when is the next nipype release? |
@byvernault -re: release, i'm hoping tomorrow. |
@satra Great :). Do you think you will have time to add niftyfit before the release? Cheers, |
@byvernault - i ran into an issue with doc building - the ones already pulled in are giving a bunch of errors. i believe they are all from the docstrings, so i'm replacing this
with
you'll need a few more tools to build the docs: sphinx, pydotplus. and then do |
Oops. Ok, I will check that for niftyfit (as well as niftyreg/niftyseg) and fix those issues. Sorry. |
@satra , when I build the doc, It finishes without issue on the build: copying static files... done Build finished. The HTML pages are in _build/html. When I load the index.html and I look at niftyseg.patchmatch, I can see the docsting fine, the only thing is that I am missing a ending line after the first url. What kind of error do you have? I am probably doing something wrong. Cheers, |
@byvernault - do i pushed the changes for master here: #1997 |
Got it. I see the errors. I will edit niftyseg files to fix them in this branch. Is that fine? I don't see any for niftyfit and niftyreg. Do you? |
@satra I think I fixed all the docstring for niftyseg and I didn't see any for the other packages. WDYT? |
@byvernault - #1997 fixes the issues with niftyseg - so you should be able to remove those from here. once that PR gets merged, i would suggest merging with master, running doesn't look like i'll be able to cut a release tonight. so sometime over the weekend. |
@byvernault - if you could merge master and resolve the conflicts that would be great. i think you could replace niftiseg files with the one from master. |
Sorry, I committed from another computer and I changed the author after the commit. I though I did change it for the commit but apparently not. I'm still the author of it. I will try to edit this. Thanks @satra for your help. Kind Regards, |
Dear nipype team,
We are ready to add niftyfit to nipype. I copied all the interfaces we generated for this package as well as the test.
I tested it with python 2 and python 3. It's working on my computer.
Let me know if you see anything not compatible or that I should change in the code.
Kind Regards,
Ben