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

fmriprep flags etc #110

Closed
KevinAquino opened this issue Aug 8, 2018 · 3 comments
Closed

fmriprep flags etc #110

KevinAquino opened this issue Aug 8, 2018 · 3 comments
Labels
question issues detailing questions about the project or its direction

Comments

@KevinAquino
Copy link

Hiya!

I am switching over to using fmriprep instead of the Meica.py pipeline -- I was wondering are there any special flags to use or examples of a fmriprep workflow?

thanks! :)

@emdupre
Copy link
Member

emdupre commented Aug 9, 2018

Hi @KevinAquino, sorry for the delay !

Right now the "tedana pipeline" with fmriprep is still a series of independent steps, since I haven't yet had a chance to integrate it directly into the fmriprep codebase. So, the workflow is such that (1) fmriprep is run as best fits your data i.e., with or without fieldmaps, etc (2) minimal preprocessing steps are completed -- that is, dropping the first few volumes for stabilization and applying the brain mask, and (3) running tedana.

This workflow works and in my experience yields similar results, but it is still minimally tested ! It'd be great to get your feedback if you're also using fmriprep + tedana.

One important note -- right now tedana by default implements the ME-ICA 3.2 version of the selection criteria, but we're planning to update to the ME-ICA 2.5 version of the selection criteria and allow 3.2 only as a user-specified option. So, please do note the version of tedana that you run since the selection criteria strongly influence the denoising process.

Hopefully this answers your question ! Let me know if anything else arises, and please know that we also check NeuroStars for any issues there.

@emdupre emdupre added the question issues detailing questions about the project or its direction label Aug 9, 2018
@KevinAquino
Copy link
Author

Thank you for that @emdupre ! so it looks like there is nothing too special that we have to do to get it working!

I will be using this for a range of acquisitions including a 1200 cohort study, so I'll be able to provide some feedback shortly! :)

also you mentioned:

One important note -- right now tedana by default implements the ME-ICA 3.2 version of the selection criteria, but we're planning to update to the ME-ICA 2.5 version of the selection criteria and allow 3.2 only as a user-specified option.

do you mean selection of ICs with the k-daw flag etc?

@emdupre
Copy link
Member

emdupre commented Aug 13, 2018

Yes, exactly ! We have #84 open to document the selection process in a much more accessible way, but effectively, the criteria by which independent components are labelled as e.g., mid-K differ across selection algorithms -- you can see an example of this in #97.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question issues detailing questions about the project or its direction
Projects
None yet
Development

No branches or pull requests

2 participants