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

SDC-pepolar implementation fails for some participants #10

Closed
markushs opened this issue Mar 15, 2019 · 6 comments
Closed

SDC-pepolar implementation fails for some participants #10

markushs opened this issue Mar 15, 2019 · 6 comments

Comments

@markushs
Copy link
Contributor

Hi,

The SDC-pepolar implementation in fmriprep (1.3.1) has worked fine for most subjects in a dataset we are acquiring. However, for a few, typically older, participants we see very strange results. Interestingly, the spin-echo EPIs with opposing phase encoding (AP/PA) used to estimate fieldmaps also look somewhat strange in the failing participants.

Examples of SE EPIs in a subject that is handled well by fmriprep:
image

SDC results for this subject in fmriprep
image

Examples of SE EPIs in a subject that is not handled well by fmriprep:
image

And the resulting SDC output (note especially how anterior parts of lateral ventricle / corpus callosum get compressed; x = -17)
image

The reason I report this as an issue here (and not as an open question on neurostars) is because these subjects – with "non-prototypical" blip-up/blip-down-images – are handled well when using topup+applytopup to estimate and applying the fieldmap (i.e., the resulting distortion-corrected GRE EPIs align well with the structural scan).

Topup-estimated fieldmap from the second set of SE EPIs shown above (GRE EPI BOLD data with PE-direction AP to the left):
image

Distortion-corrected GRE EPI (applytopup) coregistered with structural T1w (WM-edge from FSL FAST overlaid). Same data as in the second SDC output shown above.
image

I'm wondering if this issue could be related to the limiting of displacement estimation to the target file phase encoding direction (as stated in the documentation for fmriprep.workflows.fieldmap.pepolar.init_pepolar_unwarp_wf). Clearly, in the second set of SE EPIs shown above, some displacements seem to go in the opposite direction of the phase encoding direction. Why this is happening for some subjects, I don't know, but as I wrote initially it seems to be the case mostly for older adults. I have verified that all scanner parameters and .json-info were correct for the relevant scans. Moreover, the "strange" PE-direction effects in some subjects seem to be stable across scanner sessions (we collect several fieldmaps over several days for these participants).

Thanks!
Markus

@markushs
Copy link
Contributor Author

markushs commented Apr 5, 2019

Posted this a general question on neurostars (https://neurostars.org/t/sdc-pepolar-in-fmriprep-rationale-for-limiting-displacement-estimation-direction/4025), so closing this for now.

@markushs markushs closed this as completed Apr 5, 2019
@oesteban
Copy link
Member

oesteban commented Apr 6, 2019

Sorry I dropped the ball with this thread.

Although I have replied to your question on NeuroStars, looking at the bad example I'm going to reopen this issue. However, I'd say that SDC is not working in that case (not that the settings are suboptimal).

Could you provide us with that dataset?

@oesteban oesteban reopened this Apr 6, 2019
@markushs
Copy link
Contributor Author

Hi @oesteban

Sorry for the late response. Our storage server has been down (for 3 weeks!), so I haven't had access to the data until now. But here's an minimal example dataset (2 subjects, T1w, fieldmaps + 100vols fMRI) that should let you recreate the issue.

https://www.dropbox.com/sh/gbkoghsln81zp06/AAAkAYBL2FYsB88O_xINHyEga?dl=0

sub-01 is the worst example I could find of how it looks when it fails
sub-05 should look ok after SDC

Let me know if you need anything else. Thanks!

@oesteban oesteban transferred this issue from nipreps/fmriprep Jul 9, 2019
@markushs
Copy link
Contributor Author

markushs commented Sep 27, 2019

Hi!
I just wanted to follow up on this one. We keep having problems with the SDC-pepolar step in fmriprep/sdcflows. I am quite convinced that the problem does not lie in our data, as a FSL topup-approach to distortion correction produce nice-looking functionals after SDC.

Here's an example:

SDC performed using FSL topup + applytopup (Freesurfer's white surface in green)
image

SDC performed using 3dQwarp+ANTs (through fmriprep v.1.4.0). Compare e.g. the rostral Anterior Cingulates
image

Another example:

FSL topup:
image

3dQwarp+ANTs:
image

We see this issue – "overcompressed" frontal lobes following fmriprep's SDC – all the time, and also with participants with "normal-looking" Spin-echo-EPIs of (i.e., the problem is not limited to the "strange" cases reported in the original post). As mentioned originally, however, topup seems to deal nicely also with the strange cases.

Here's the code used to do the comparison (note that topup is starting with the same input as sdcflows):

image

So the question, I guess, is whether it's possible to incorporate a topup-option in SDCflows, or if you have any ideas for a workaround to ensure good correspondence between functionals and structurals in our case? I should mention that we are collecting data with the HCP/CMRR-multiband-sequence with MB=4 but no acceleration beyond that. So the geometric distortions in the phase-encoding direction (A-->P) are quite strong, and similar to what is seen with HCP-data from the Prisma in general.

Thanks!

@oesteban
Copy link
Member

oesteban commented Oct 3, 2019

Hi @markushs, your request is totally reasonable. There is no topup option for historical reasons, and we should bring it in - can you open an issue explicitly requesting it?

We will also look into 3dQWarp and check what regularization options are there to help alleviate these problems.

@markushs
Copy link
Contributor Author

markushs commented Oct 3, 2019

Thanks, @oesteban.
Sure, I'll open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants