help > RE: unclear error message
Dec 6, 2019  02:12 PM | Alfonso Nieto-Castanon - Boston University
RE: unclear error message
Hi

That's curious indeed. You are right that this error message indicates some problem opening your functional data (e.g. missing files) but if that is the case then this should have been detected earlier when loading your project. Could you please try running the following to see if that helps us better identify the problem here?

files = conn_module('get','functionals');
for nsub=1:numel(files)
   for nses=1:numel(files{nsub})
      fprintf('testing file %s ',files{nsub}{nses});
      try
        a=spm_vol(files{nsub}{nses});
        b=spm_read_vols(a);
        fprintf('ok\n');
      catch me
        fprintf('PROBLEM READING THIS FILE\n');        
        me.rethrow;
      end
   end
end

Thanks
Alfonso
Originally posted by boehm:
Hello,
I repeatedly encounter this error (please find error message included below) although when loading the project no missing files are detected.
Can someone help how to handle this.
Thanx

ERROR DESCRIPTION:

Error using spm_sample_vol
Cant open image file.
Error in spm_get_data (line 46)
Y(i,:) = spm_sample_vol(V(i),XYZ(1,:),XYZ(2,:),XYZ(3,:),0);
Error in conn_create_vol (line 115)
x(nscan,:)=spm_get_data(V1(nscan),pinv(V1(nscan).mat)*xyzs(idx0,:)');
Error in conn_process (line 575)
V=conn_create_vol(filename,Vsource,[],Vref,sfile,Vmask,CONN_x.Setup.analysisunits==1,CONN_x.Setup.spatialresolution==4,0); %CONN_x.Setup.surfacesmoothing);
Error in conn_process (line 16)
case 'setup', conn_disp(['CONN: RUNNING SETUP STEP']); conn_process([0:4,4.5,5]);
Error in conn (line 5262)
else conn_process(processname); ispending=false;
Error in conn_menumanager (line 120)
feval(CONN_MM.MENU{n0}.callback{n1}{1},CONN_MM.MENU{n0}.callback{n1}{2:end});
CONN18.b
SPM12 + DEM FieldMap MEEGtools
Matlab v.2018b
project: CONN18.b
storage: 7209.9Gb available
spm @ /usr/local/MATLAB/toolbox/spm12
conn @ /scratch/igis/processing/conn

Threaded View

TitleAuthorDate
boehm Dec 2, 2019
RE: unclear error message
Alfonso Nieto-Castanon Dec 6, 2019