Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
faq:matlab_version_7.3_2006b_crashes_when_i_try_to_do [2009/02/25 21:01]
127.0.0.1 external edit
faq:matlab_version_7.3_2006b_crashes_when_i_try_to_do [2017/08/17 11:21] (current)
Line 1: Line 1:
 {{tag>​faq matlab}} {{tag>​faq matlab}}
  
-===== Matlab ​version 7.3 (2006b) crashes when I try to do ... =====+===== MATLAB ​version 7.3 (2006b) crashes when I try to do ... =====
  
-This may relate to a known bug in Matlab ​2006b with persistent variables. The bug relates to agressive optimization of for loops introduced in matlab ​2006b, which is incompatible with persistent variables inside the for loop. The progress indicator used in fieldtrip (i.e. the one that is dealing with the cfg.feedback options) is using a persistent variable so that it only updates the progress bar maximum ~100 times, instead of 10000 times (e.g. if you do a dipole scan for 10000 grid points).+This may relate to a known bug in MATLAB ​2006b with persistent variables. The bug relates to agressive optimization of for loops introduced in MATLAB ​2006b, which is incompatible with persistent variables inside the for loop. The progress indicator used in fieldtrip (i.e. the one that is dealing with the cfg.feedback options) is using a persistent variable so that it only updates the progress bar maximum ~100 times, instead of 10000 times (e.g. if you do a dipole scan for 10000 grid points).
  
-You can determine whether this bug is actually the problem for Matlab ​crashing by +You can determine whether this bug is actually the problem for MATLAB ​crashing by 
   starting matlab   starting matlab
   cd fieldtrip-xxx/​private   cd fieldtrip-xxx/​private
   progress('​init'​)   progress('​init'​)
-If Matlab ​crashes, then this is indeed the problem. You can try the following work around.+If MATLAB ​crashes, then this is indeed the problem. You can try the following work around.
  
 First try typing First try typing
   feature accel off   feature accel off
-on the Matlab ​command line and try reproducing the bug (see above). If that indeed solves it, I suggest that you add +on the MATLAB ​command line and try reproducing the bug (see above). If that indeed solves it, I suggest that you add 
   if strcmp(getfield(ver('​MATLAB'​),​ '​Version'​),​ '​7.3'​)   if strcmp(getfield(ver('​MATLAB'​),​ '​Version'​),​ '​7.3'​)
     feature accel off     feature accel off
   end   end
 to your startup.m file. to your startup.m file.
-