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

Workflow for multiecho data #884

Closed
emdupre opened this issue Dec 7, 2017 · 1 comment
Closed

Workflow for multiecho data #884

emdupre opened this issue Dec 7, 2017 · 1 comment

Comments

@emdupre
Copy link
Collaborator

emdupre commented Dec 7, 2017

I see in #808 that you're encouraging the creation of a unique workflow instead of modifying the init_func_preproc_wf as I've been doing in #875. Do you have a preference for either creating unique workflows for specific cases (like functional-only or multi-echo scans) or modifying existing workflows in place?

@oesteban
Copy link
Member

oesteban commented Dec 7, 2017

Well, I think your route is better. In #808 we took that path because it seemed easier for new contributors to start that way.

In sum, I think you have plenty of experience with nipype that allows you to advance quickly even implementing things the hard way. The way you were driving this PR is preferable (IMHO).

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

No branches or pull requests

3 participants