Tagged: "bb.nii does not exist"
-
AuthorPosts
-
12/07/2018 at 4:36 PM #6094ariannafeliceParticipant
Dear all,
I’m trying to run Lead-DBS on my computer. I load the images (ct post, mr pre, mr post) and i choose to run the volume registration and the surface recostruction (I left all the default settings). Now i have this error:
Error using spm_vol_spm_vol_hdr (line 80)
File “C:\Users\azzo\Desktop\dicom dbs\ferola\scrf\bb.nii” does not exist.
Error in spm_vol (line 61)
v = spm_vol_hdr(deblank(P(i,:)));
Error in ea_load_nii (line 35)
nii = spm_vol(fname);
Error in ea_crop_nii (line 49)
nii=ea_load_nii(filename);
Error in ea_refreshscrf>ea_createbbfiles (line 76)
ea_crop_nii([directory,’scrf’,filesep,’bb.nii’]);
Error in ea_refreshscrf>ea_createrefineslice (line 53)
ea_createbbfiles(directory); % needs to unfortunately be done each time since coregistration may have changed.
Error in ea_refreshscrf>ea_loadrefineslice (line 30)
ea_createrefineslice(directory,options,refine);
Error in ea_refreshscrf (line 3)
standardslice=ea_loadrefineslice(directory,options,0);
Error in ea_subcorticalrefine_ea_subcorticalrefine_OpeningFcn (line 66)
ispresent=ea_refreshscrf(options,handles,directory);
Error in gui_mainfcn (line 220)
feval(gui_State.gui_OpeningFcn, gui_hFigure, [], guidata(gui_hFigure), varargin{:});
Error in ea_subcorticalrefine (line 42)
gui_mainfcn(gui_State, varargin{:});
Error in ea_autocoord (line 188)
ea_subcorticalrefine(options);
Error in ea_run (line 96)
ea_autocoord(options);
Error in lead_dbs>run_button_Callback (line 187)
ea_run(‘run’,options);
Error in gui_mainfcn (line 95)
feval(varargin{:});
Error in lead_dbs (line 43)
gui_mainfcn(gui_State, varargin{:});
Error in @(hObject,eventdata)lead_dbs(‘run_button_Callback’,hObject,eventdata,guidata(hObject))
Error while evaluating UIControl CallbackCan you help me?
thank you in advance for your collaboration.
Regards,
Arianna12/07/2018 at 5:03 PM #6096andreashornKeymasterHi Arianna,
the normalization didn’t run through, probably because your computer doesn’t have enough RAM. Please try to normalize with SPM Segment instead (which is equally good and much faster).
Also you need to choose between either postop MRI or CT (using both is not possible), so choose the one with the better resolution (which is usually the CT).
Best, Andy
09/30/2020 at 7:00 AM #11395ColetteParticipantGood Morning
I met the same issue with the new 2.3.2. version
I tested different points so far I did not find the solution
I doubt it is a question of RAM as I use different workstations and still have the issue
I will test again and let you know
BestColette
-
AuthorPosts
- The forum ‘Support Forum (ARCHIVED – Please use Slack Channel instead)’ is closed to new topics and replies.