search

alfnie / conn

CONN toolbox, development version (conn-toolbox.org)
http://web.conn-toolbox.org
38 stars 16 forks source link

fmriprep import issue #3

Open smeisler opened 3 years ago

smeisler commented 3 years ago

Hi,

Just wanted to report a bug when importing an fmriprep dataset. An extra .nii is appended to all file names when copied to the derivatives/conn directory, see the image below (sub names have been deliberately cut off). Functionally, it still works, but is inconvenient, especially because any other files you want to include (such as events) also have to have that same naming convention if conn is to find them automatically. image

Best, Steven

alfnie commented 3 years ago

Hi Steve, Thanks for the bug report, I have included a fix for this in one of the latest commits, if you have a chance please let me know if everything seems to be working fine now Thanks again! Alfonso

smeisler commented 3 years ago

It seems to work fine, thanks! However, when I tried this additionally on a dataset I am working with that only has MNIPediatric space outputs from fmriprep, no subjects appear in the data import screen, even though CONN says it found X subjects with Y functional files. Is that because CONN is scanning for MNI2009 space specifically?

alfnie commented 3 years ago

CONN "prefers" MNI152NLin2009cAsym (in the sense that it will pick this if your data is available in this space) but otherwise it will pick the space where CONN finds most subjects' data in. The only constrain is that both your anatomical and functional data need to be available/processed in the same space

bearsun commented 3 weeks ago

CONN "prefers" MNI152NLin2009cAsym (in the sense that it will pick this if your data is available in this space) but otherwise it will pick the space where CONN finds most subjects' data in. The only constrain is that both your anatomical and functional data need to be available/processed in the same space

Sorry I can't find my NITRC account. So I just ask here since it is related. I am importing data from fMRIPrep (24.0.1) to CONN (22.v2407). I have preprocessed data in both native T1w space and MNI152NLin6Asym space. But it seems that CONN imports the native space data and ignores the MNI space data. Is there any way to let CONN prioritize the MNI space data while importing? Thank you!