Normalization problem

[Rafael RodriguezParticipant]

Hi all. I’m trying to run my first LEAD. I am running lead v1.5.0.1 on Matlab 2015a, with SPM 12. In patient directory I have the anat.nii and the postop (tra, cor, sag). After normalize anat using ANTs (I can open the glanat.nii), the following errors pop up on matlab main window:

Warning: No anatomy information found. Please put either anat.nii, anat_t1.nii or anat_pd.nii into subject folder.
> In ea_assignpretra (line 15)
In ea_conv_antswarps (line 24)
In ea_ants_nonlinear (line 161)
In ea_normalize_ants (line 33)
In ea_autocoord (line 82)
In ea_run (line 102)
In lead_dbs>run_button_Callback (line 278)
In gui_mainfcn (line 95)
In lead_dbs (line 43)
In @(hObject,eventdata)lead_dbs(‘run_button_Callback’,hObject,eventdata,guidata(hObject))
Error using fprintf
Invalid file identifier. Use fopen to generate a valid file identifier.

Error in ea_assignpretra (line 26)
fprintf(fs,’%s’,’dcmbiasfielddone’);

Error in ea_conv_antswarps (line 24)
options=ea_assignpretra(options);

Error in ea_ants_nonlinear (line 161)
ea_conv_antswarps(directory);

Error in ea_normalize_ants (line 33)
ea_ants_nonlinear([options.earoot,’templates’,filesep,’mni_hires’,options.primarytemplate,’.nii’],…

Error in ea_autocoord (line 82)
eval([options.normalize.method,'(options)’]); % triggers the normalization function and passes the options struct to it.

Error in ea_run (line 102)
ea_autocoord(options);

Error in lead_dbs>run_button_Callback (line 278)
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 Callback

[andreashornKeymaster]

Hi Rafael,

sorry to hear. I just finished uploading a new release which should fix this issue.
Let me know if it still happens!

Best, Andy

[Rafael RodriguezParticipant]

Dear Andy
I have updated to version v1.5.0.2 and normalization ran perfectly. Thank you very much.

[andreashornKeymaster]

Great, thanks for letting us know!

[Author]

Posts