Submitted by krisfarrant on Wed, 11/05/2014 - 04:27
I am trying to run a voxel-wise seed based functional connectivity analysis in the REST toolbox. I am using the HCP (human connectome project) data which has 1200 volumes and a TR of .72. When I run the analysis I get the error:
Exception occured. ()
Error using rest_spm_read_vols (line 34)
File too small.
Has anybody come across this before? Has anybody used this toolbox with the HCP data set? Is there any potential fixes?
I should mention that I have used this toolbox on smaller data sets and it works just fine. Is there a way to use this toolbox with the large data sets
Best,
Kris
Submitted by LiXun on Thu, 11/06/2014 - 14:52 Permalink
Re: Error message when running functional connectivity analysis
It has no matter with the data size. I am afraid you have a mistake with the input data. Please recheck your input, and make sure every subject's folder include all the volumes.
Submitted by krisfarrant on Fri, 11/07/2014 - 03:08 Permalink
Re: Error message when running functional connectivity analysis
Thanks for your reply. I have checked my data and there are 1200 volumes in each .nii file. I have tried conduction the functional connectivity analaysis with a smaller group of subjects and still receive the same message
Do you have any other suggestions?
p.s. I am using SPM 12
Kris
Submitted by Ruibin on Tue, 05/19/2015 - 17:02 Permalink
Re: Error message when running functional connectivity analysis
Hi Kris and Experts,
I also try to do the voxel wise functional connectivity analysis using HCP data and get the same iusse with you. Do you address this issue? I also get this error. If you did, could you give me a favor? Thanks in advance.
In addition, when I try to use dcm2nii to unpack the 4D data to 3D file, I found that just 11 time points can be extracted. I am so cofusing, and I am looking forward to hearing from you.
Ruibin
Submitted by ZHANG_RESTadmin on Fri, 11/28/2014 - 18:54 Permalink
Re: Error message when running functional connectivity analysis
Hi Kris,
have you met the same error msg if you trying to perform analysis on other datasets? such as those with ordinary TR?
I am wondering if the .72 TR dataset is broken ...