help
help > RE: CONN compatibility with BIDS and fmriprep output
Mar 19, 2019 06:03 PM | Karolina Finc
RE: CONN compatibility with BIDS and fmriprep output
Hi Harris,
I used *confounds.tsv file from fMRIPrep for this, which provides 'FramewiseDisplacement' and 'stdDVARS' values for every data point. I created empty vector of zeros and then I identified time points with FD > 0.5 mm and stdDVARS > +/- 3 SD and set them to ones. Next, I loaded this vector into CONN as confound regressor.
I think that running ART in CONN would also work, but as I know ART looks for for SPM's 6 motion parameters *.txt file so you should also create such file by subsetting *confounds.tsv table and saving it without column names in a .txt file.
Hope this help!
Best,
Karolina
I used *confounds.tsv file from fMRIPrep for this, which provides 'FramewiseDisplacement' and 'stdDVARS' values for every data point. I created empty vector of zeros and then I identified time points with FD > 0.5 mm and stdDVARS > +/- 3 SD and set them to ones. Next, I loaded this vector into CONN as confound regressor.
I think that running ART in CONN would also work, but as I know ART looks for for SPM's 6 motion parameters *.txt file so you should also create such file by subsetting *confounds.tsv table and saving it without column names in a .txt file.
Hope this help!
Best,
Karolina
Threaded View
Title | Author | Date |
---|---|---|
Karolina Finc | Feb 9, 2019 | |
Alfonso Nieto-Castanon | Feb 14, 2019 | |
Karolina Finc | Feb 14, 2019 | |
padma | Jul 12, 2021 | |
omaomae | Jul 12, 2021 | |
padma | Jul 13, 2021 | |
omaomae | Jul 14, 2021 | |
padma | Jul 9, 2021 | |
Harrison Fisher | Mar 13, 2019 | |
Karolina Finc | Mar 19, 2019 | |
David Pagliaccio | Mar 18, 2021 | |
Kylie Isenburg | Jun 11, 2021 | |