-
Notifications
You must be signed in to change notification settings - Fork 7
ENH: The unit about building and adding a new EMC method #3
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
arokem
left a comment
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.
A few small comments and suggestions for now.
docs/dmriprep/hmc.md
Outdated
|
|
||
| **Problem**: although most dMRI practitioners employ FSL for the estimation and correction of head-motion and eddy-current distortions, the FSL toolbox has restrictions of commercial use. By using FSL's eddy implementation, *dMRIPrep* inherits those restrictions. | ||
| Therefore, a fully-open implementation of *dMRIPrep* would require eliminating FSL as a dependency. | ||
| In this case, we will provide our own implementation of an algorithm for head-motion and eddy-current-derived distortions. |
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 don't know if I like this framing. Arguably, we want to provide a general, open-source solution that is also best in class. The license issues, though real, seem a bit obscure.
|
Deploy preview for nipreps-book ready! Built with commit 20f21fc |
f0bde2e to
3370307
Compare
Co-authored-by: Ariel Rokem <arokem@gmail.com>
Co-authored-by: Michael Joseph <josephmje.22@gmail.com>
|
@josephmje, I've pushed some of your edits to |
Instead of dumping the documentation scattered around projects, let's have the conversation about EMC here.
@arokem and @dPys, can you please have a look and suggest changes/point out things that seem wrong or even blatantly wrong?