Hi Alfonso,

Could you help me out by explaining the naming convention used by CONN to store results for different conditions?

I had previously processed my data with a single condition, this provided me with a DATA_SubjectXXX_Condition001.mat file that had a 'softlink' variable pointing to the DATA_SubjectXX_Condition000.matc file containing the actual data.

I added a second condition to process the data with a different bandpass filter, and now I see several more files appearing that don't make much sense to me.

There are the two DATA_SubjectXXX_Condition001.mat and DATA_SubjectXX_Condition000.matc files as described above. Then there is a DATA_SubjectXXX_Condition002.mat but the 'softlink' variable is empty (i.e. '[]'), and there is no DATA_SubjectXXX_Condition001.matc file. Next, there is a DATA_SubjectXXX_Condition003.mat file, but the 'softlink' variable point to the DATA_SubjectXX_Condition000.matc file (same file as used by DATA_SubjectXXX_Condition001.mat). And finally, there is a DATA_SubjectXXX_Condition002.matc file with actual data, but it is not referred to by any of the other mat files.

CONN does generate a niftiDATA_SubjectXXX_Condition000.nii and niftiDATA_SubjectXXX_Condition002.nii files, and the contents of these files are distinct by MD% hash, so I assume the data for the two conditions are there. Which files belong to which condition?

Kind regards,
Jalmar