Help: Error in using DPARSF

Hi,

I am running DPABI version 2.3 and using the DPARSF 4.3 (Advanced Edition) installed.

I am using Matlab 2014b on a linux machine and got the following error when trying to run the attached batch:

 

Error using DPARSFA_run (line 628)
Job execution failed. The full log of this run can be found
in MATLAB command window, starting with the lines (look for
the line showing the exact #job as displayed in this error
message)
------------------
Running job #1
------------------


Error in DPARSFA>pushbuttonRun_Callback (line 1786)
    [Error]=DPARSFA_run(handles.Cfg);


Error in gui_mainfcn (line 95)
        feval(varargin{:});

Error in DPARSFA (line 30)
    gui_mainfcn(gui_State, varargin{:});

AttachmentSize
Image icon Screenshot-4.png30.59 KB

It looks like the end of my comment got cut off somehow last time. This is how the full error message was supposed to read:

Info: GLDrawableHelper.reshape: pre-exisiting GL error 0x500
Error using DPARSFA_run>(parfor body) (line 1432)
Index exceeds matrix dimensions.
Error in DPARSFA_run (line 1411)
        parfor i=1:AutoDataProcessParameter.SubjectNum
Error in DPARSFA>pushbuttonRun_Callback (line 1786)
    [Error]=DPARSFA_run(handles.Cfg);
Error in gui_mainfcn (line 95)
        feval(varargin{:});
Error in DPARSFA (line 30)
    gui_mainfcn(gui_State, varargin{:});
Error while evaluating UIControl Callback

It seems like this error is coming up during the BET step. DPABI has made folders with an image having "Bet" as the prefix for half the subjects but then stopped with the error seen above.

Also I did just run the command:

"system('bet --help')"

And it returned the expected help text for bet, so it seems that my fsl path is setup correctly.

If anyone has any ideas it would be much appreciated. Thanks!

Erik

FYI for future people who come across this problem:

It turns out I had one of my subjects misnamed so that the subject ID wasn't consistant between FunImg and T1Img.

My job still ended up failing as I had selected the run with and without global signal regression option and I think that gave another problem, but it looks like the results at least finished for without GSR before failing.

FYI for future people who come across this problem:

It turns out I had one of my subjects misnamed so that the subject ID wasn't consistant between FunImg and T1Img.

My job still ended up failing as I had selected the run with and without global signal regression option and I think that gave another problem, but it looks like the results at least finished for without GSR before failing.

Thanks for your note!