-
Notifications
You must be signed in to change notification settings - Fork 95
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
Add information about extracting echo-wise preprocessed data from fMRIPrep to FAQ #717
Comments
This script by @JulioAPeraza works for 20.2.1 (at least with the settings we've been using). |
It's probably best to point to a gist that we can easily update: https://gist.github.com/tsalo/83828e0c1e9009f3cbd82caed888afba. We could even embed it in the docs, I think
|
The script seems to work with fMRIPrep 20.2.5 |
Hi there, I've recently tried to run the collect_fmriprep() script on https://tedana.readthedocs.io/en/stable/faq.html#collecting-fmriprepped-data but I could not successfully retrieve the required files needed. I'm currently running fmriprep v21.0.0. For me, the only output seen was the string "Wrangling subject n" and then the script ended almost instantaneously. Any guidance on this? **Update: The first change seems to be changing the following line, where
The next part I believe, has got to do with:
where files in the bf_dir_list do not follow the 'sub-' label. I am not sure how to fix this part as I don't know how the output of the working dir of earlier fmriprep versions look like (first time using!). |
While I understand why you might not want to re-run fMRIPrep on your data, fMRIPrep 21.0.0 does have an option to output the semi-preprocessed echoes ( |
Summary
Our current recommendation when using fMRIPrep + tedana (instead of just t2smap) is to extract echo-wise preprocessed data from the working directory to the output directory, then run tedana on those native-space preprocessed files, and then apply the saved transforms to the native-space denoised data.
Additional Detail
Next Steps
The text was updated successfully, but these errors were encountered: