-
Notifications
You must be signed in to change notification settings - Fork 272
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
Unified fieldmap #194
Unified fieldmap #194
Conversation
…ion correction scripts into a single script.
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.
This seems to have conflicts with master. Please resolve so that this can be merged. Thanks.
@glasserm |
I get this message "This branch cannot be rebased due to conflicts |
@glasserm How about a regular merge? Or a "squash and merge"? |
Tim has asked that we do rebase and merge, so I'd like his input at this point. |
Why the need for the "erode" step specifically in the Philips case? I wonder if Oxford will want to include that in |
I included the erode step for Philips data, since |
@axkralj990 Makes sense. Thanks for the explanation. |
Looks like he pulled the master with a merge commit to resolve conflicts, after all his changes, instead of doing a rebase. I'll look at what the conflicts would be for a rebase. |
Looks like the philips_fieldmap branch this is based on has pulled from master, so this is problematic to convert to a rebase. We can do this as a normal merge, but I would prefer that branches intended to become pull requests be rebased on master when you want to catch up, and avoid ever doing a pull merge from master. |
I'm not planning on any further review. |
This is only intended to be in a future 4.3.1 release, right? I haven't had confirmation of the current 4.3.0 candidate completing whatever testing is needed before making it the official release. |
Yes. So, we'll need to update |
Hi,
This pull request improves the performance of the distortion correction for Philips B0 map fieldmap scans, by taking the echo difference (deltaTE) into account when computing the fieldmaps. We have also included phase unwrapping and image de-meaning. We followed exactly the same steps as are implemented in the fsl_prepare_fieldmap function for Siemens scanners. The only difference is the additional brain mask erosion step for Philips scans, which results in a cleaner preprocessed fieldmap. A comparison between the current Philips and Siemens steps for fieldmap preparation is shown on the attached figure.
The code has been tested successfully on both structural and functional images from Siemens and Philips scanners. It does not change any other parts of the processing pipelines.
With kind regards,
Grega & Aleksij