Making the workflow robust to differences in acquisition protocols about fmriprep HOT 5 CLOSED

@craigmoodie look at you, Github pro! so proud

from fmriprep.

thanks @vsoch! 👍

from fmriprep.

So let's make a nipype pro from a Github pro:
[i] Added #20.
[ii] Added #20 and #21.
[iii] Added #19.

@craigmoodie, Do these cover all the defined use-cases?

from fmriprep.

Hi Osteban, there is also the case where the user will inputs two phase-encoding reversed spin-echo field maps, but this is already implemented in the original workflow that I uploaded. Otherwise, I think those issues should cover all of the other use cases.

from fmriprep.

Cool. Yes, that is the default use-case as you initially implemented it. Actually, that should exactly correspond to this new workflow: https://github.com/poldracklab/preprocessing-workflow/blob/master/fmriprep/workflows/fieldmap.py#L15. For this reason I did not open any other ticket.

Now that this issue is mapped to the 3 elementary tasks (#19, #20 and #21) I will close it.

Thanks for reporting!

from fmriprep.