-
Notifications
You must be signed in to change notification settings - Fork 26
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
Denoise kernel size #22
Comments
Does it make sense to set a target smoothness instead of a straight kernel smoothing, as with 3dBlurToFWHM? Then we're less dependent on the quality of the input data. |
Hopefully, this will not be necessary after #14, but it doesn't hurt to first get this done. |
Putting together the lessons learned in nipreps#30, leveraging nipreps#52 and nipreps#53 (unfolded from nipreps#30 too), and utilizing nipreps#50 and nipreps#51, this workflow adds the phase difference map calculation, considering it one use-case of the general phase-difference fieldmap workflow. On top of this PR, we can continue the discussions held in nipreps#30. Probably, we will want to address nipreps#23 the first - the magnitude segmentation is sometimes really bad (e.g. see the phase1/2 unit test). Another discussion arisen in nipreps#30 is the spatial smoothing of the fieldmap (nipreps#22). Finally, the plan is to revise this implementation and determine whether the subtraction should happen before or after PRELUDE, and whether the arctan2 route is more interesting.
Putting together the lessons learned in nipreps#30, leveraging nipreps#52 and nipreps#53 (unfolded from nipreps#30 too), and utilizing nipreps#50 and nipreps#51, this workflow adds the phase difference map calculation, considering it one use-case of the general phase-difference fieldmap workflow. On top of this PR, we can continue the discussions held in nipreps#30. Probably, we will want to address nipreps#23 the first - the magnitude segmentation is sometimes really bad (e.g. see the phase1/2 unit test). Another discussion arisen in nipreps#30 is the spatial smoothing of the fieldmap (nipreps#22). Finally, the plan is to revise this implementation and determine whether the subtraction should happen before or after PRELUDE, and whether the arctan2 route is more interesting.
I've set 5 as the default for now, and I'm pretty happy with the results. I'm also with @effigies that Finally, we need to investigate the resampling when moving the fieldmap to the target EPI dataset because I'm under the impression that it is introducing some little spikes in it. |
Isn't |
Isolated spikes would be removed with a Gaussian filter easily - median filters are better for salt&pepper kind of noise. It doesn't hurt to try. But yes, you are right - the median filter is just to remove spikes |
This PR finally adds an implementation for B-Spline smoothing and extrapolation of fieldmaps. References: nipreps#71, nipreps#22. Resolves: nipreps#72. Resolves: nipreps#14.
This PR finally adds an implementation for B-Spline smoothing and extrapolation of fieldmaps. References: nipreps#71, nipreps#22. Resolves: nipreps#72. Resolves: nipreps#14.
This PR finally adds an implementation for B-Spline smoothing and extrapolation of fieldmaps. References: nipreps#71, nipreps#22. Resolves: nipreps#72. Resolves: nipreps#14.
This PR finally adds an implementation for B-Spline smoothing and extrapolation of fieldmaps. References: nipreps#71, nipreps#22. Resolves: nipreps#72. Resolves: nipreps#14.
This PR finally adds an implementation for B-Spline smoothing and extrapolation of fieldmaps. References: nipreps#71, nipreps#22. Resolves: nipreps#72. Resolves: nipreps#14.
This PR finally adds an implementation for B-Spline smoothing and extrapolation of fieldmaps. References: nipreps#71, nipreps#22. Resolves: nipreps#72. Resolves: nipreps#14.
This PR finally adds an implementation for B-Spline smoothing and extrapolation of fieldmaps. References: nipreps#71, nipreps#22. Resolves: nipreps#72. Resolves: nipreps#14.
This PR finally adds an implementation for B-Spline smoothing and extrapolation of fieldmaps. References: nipreps#71, nipreps#22. Resolves: nipreps#72. Resolves: nipreps#14.
This PR finally adds an implementation for B-Spline smoothing and extrapolation of fieldmaps. References: nipreps#71, nipreps#22. Resolves: nipreps#72. Resolves: nipreps#14.
This PR finally adds an implementation for B-Spline smoothing and extrapolation of fieldmaps. References: nipreps#71, nipreps#22. Resolves: nipreps#72. Resolves: nipreps#14.
This PR finally adds an implementation for B-Spline smoothing and extrapolation of fieldmaps. References: nipreps#71, nipreps#22. Resolves: nipreps#72. Resolves: nipreps#14.
Superseded by #119. |
I'm finding for some older phase1/phase2 fieldmaps that it's necessary to set the kernel size to 5 for this node: https://github.com/poldracklab/sdcflows/blob/0.0.2/sdcflows/workflows/phdiff.py#L98
Is there a downside to setting the default to 5? Or should we make this a parameter?
The text was updated successfully, but these errors were encountered: