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

Error occurs when using two phase images and two magnitude images as fieldmap inputs #1169

Closed
wangboc opened this issue Jun 14, 2018 · 10 comments
Assignees
Labels
bug effort: high Estimated high effort task fieldmaps impact: medium Estimated medium impact task
Milestone

Comments

@wangboc
Copy link

wangboc commented Jun 14, 2018

Hi, according to BIDS naming convention, I use two magnitude and phase images as the fieldmap inputs. While, fmriprep failed to run at the beginning. The error infos :

image

And my inputs structure is:
image

@effigies
Copy link
Member

Hi, what version of fMRIPrep are you running?

@wangboc
Copy link
Author

wangboc commented Jun 14, 2018

should be the newest version: 1.1.1
image

@chrisgorgo
Copy link
Contributor

@oesteban does FMRIPREP support phase1/phase2 type of SDC input data? I could not find traces of it in the codebase.

@wangboc
Copy link
Author

wangboc commented Jun 14, 2018

How can I calculate the phase difference image by using the two phase image? I find the fslcomplex is so complex to run... :) @chrisfilo

@mattcieslak
Copy link

So does this mean that BIDS section 8.9.2 isn't currently supported?

@effigies
Copy link
Member

@mattcieslak I believe that's correct. We would be happy to review a patch, however.

@mattcieslak
Copy link

mattcieslak commented Oct 24, 2018

Happy to write a workflow for this. Would it make sense to calculate a phasediff image from the two phases and send that as input to the workflow for 8.9.3-style fieldmaps? Or is there something fundamentally different between derived phasediffs and those that come from scanners?

@effigies
Copy link
Member

I'm not really sure, myself. I have dug into the fieldmap math much less than @oesteban, who might have thoughts here.

@mattcieslak
Copy link

It looks like there is support for phase1/phase2 in the dipy workflow (https://github.com/nipy/nipype/blob/master/nipype/workflows/dmri/fsl/utils.py#L645). Would it make sense to check if the type is "phase" and if so send the two phase images to pha2rads?

Maybe it would be good to change the type from "phase" to "phases" or something more descriptive?

@oesteban
Copy link
Member

oesteban commented Dec 4, 2019

It's been a long way @wangboc, but this has been finally addressed and released with version 1.5.1 (although you should go with the newest 1.5.2).

Could you check whether this is working out for you now? Please reopen if you find any issues.

@oesteban oesteban closed this as completed Dec 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug effort: high Estimated high effort task fieldmaps impact: medium Estimated medium impact task
Projects
None yet
Development

No branches or pull requests

5 participants