Hello,
Having an error listed below when trying to do seed based resting FC. I ran the same options and used the same ROIs with another data set and had no errors so don't think it is my choice of ROIs. I am running DPARSF_V2.1_120101, SPM8, Matlab R2011b.
============
Error using horzcat
CAT arguments dimensions are not consistent.
Error in DPARSFA_run (line 1924)
Covariables=[Covariables,theROITimeCourses];
Error in DPARSFA>pushbuttonRun_Callback (line 1133)
[Error]=DPARSFA_run(handles.Cfg);
Error in gui_mainfcn (line 96)
feval(varargin{:});
Error in DPARSFA (line 31)
gui_mainfcn(gui_State, varargin{:});
Error while evaluating uicontrol Callback
========================
This happened just after my last subject finished with this job : "Extracting ROI timecourses over..." and no FC folders are created in FunImg or in the Results folder.
Thank you, in advance, for your suggestions-
Desmond
Submitted by YAN Chao-Gan on Sun, 10/21/2012 - 10:14 Permalink
Re: horzcat error
Hi,
Could you make sure how many time points you have when you performing realign process (head motion correction). E.g., count how many lines in the rp*.txt file under RealignParameter directory.
Seems the number of the time points in the realign parameter file (rp*.txt) is different from your fMRI data (which you want to perform FC analysis).
Best,
Chao-Gan
Submitted by rajeevkrishnadas on Sat, 12/29/2012 - 15:13 Permalink
Re: horzcat error
Hi sorry to hijack this thread.
I am new to DPARSF. I have a similar problem. I am trying to run the processing demo data. I use SPM8, MatlabR2012b.
I checked the rp*.txt in each of the 3 subjects in the RealignParameter directory. They seem to have 230 lines. This I think corresponds to the number of files in the functional images (after deleting 10 images). I used the motion correction parameters and global mean signal as nuisance covariates. I get this error again.
I would be most grateful if you could give me some advise.
Thankyou.
Rajeev
Submitted by rajeevkrishnadas on Sat, 12/29/2012 - 19:27 Permalink
Re: horzcat error
Sorry about the above... It has been sorted out. The problem was with version 2.1.
Its absolutely ok with the Version 2.2.
Cheers
Rajeev