Skip to content
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

Run fieldmapless distortion correction on its own #8

Open
KirkGraff opened this issue Jan 14, 2019 · 3 comments
Open

Run fieldmapless distortion correction on its own #8

KirkGraff opened this issue Jan 14, 2019 · 3 comments
Assignees
Labels
effort: high Estimated high effort task enhancement New feature or request impact: low Estimated low impact task T1w-SyN
Milestone

Comments

@KirkGraff
Copy link

Hi all,
I'm trying to compare different ways to preprocess my data, and I'm wondering if it is possible to run only fieldmapless susceptibility distortion correction without all the other steps of fMRIprep? I'm hoping I can input an already skull stripped T1 file and a bold file and obtain a distortion corrected bold file (with a transformation matrix).

Also, would it be better to use an already motion corrected bold file, or the raw bold file?

Thanks!

-Kirk

@effigies
Copy link
Member

Hi @KirkGraff not easily. The steps involve transforming an atlas of average distortions that's in MNI space into the individual space, which requires spatial normalization of the T1w image to already have been run.

You can check out the documentation of that sub-workflow, and see if it's reasonable for you to provide all of the inputs. If so, it wouldn't be too hard to write a small script that would take those inputs and produce those outputs, but your job wouldn't be done, there. That corrects one volume, and provides a transformation that can be applied to any volume in that space. To run it on an entire series of images, you would need to register each volume to the same reference (possibly a single-band reference, or some image derived from the series), and ideally apply the SDC in the same step.

@oesteban oesteban transferred this issue from nipreps/fmriprep Jul 9, 2019
@oesteban oesteban added this to the 1.0.0 milestone Aug 7, 2019
@mattcieslak mattcieslak self-assigned this Aug 8, 2019
@oesteban oesteban modified the milestones: 1.0.0, 1.2.0 Nov 20, 2019
@mattcieslak
Copy link
Collaborator

This would be a great niflow

@oesteban oesteban added T1w-SyN enhancement New feature or request effort: high Estimated high effort task impact: low Estimated low impact task labels Nov 27, 2020
@oesteban
Copy link
Member

We have implemented the first half of the problem - estimation. I'll leave this issue open for the second half, although the priority would be very low at this point.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
effort: high Estimated high effort task enhancement New feature or request impact: low Estimated low impact task T1w-SyN
Projects
None yet
Development

No branches or pull requests

4 participants