Back to the main page.

Bug 2772 - color limits are not set correctly by ft_sourceplot in ortho mode on matlab 2014b

Reported 2014-12-04 16:30:00 +0100
Modified 2019-08-10 12:31:20 +0200
Product: FieldTrip
Component: core
Version: unspecified
Hardware: All
Operating System: All
Importance: P5 normal
Assigned to:
Depends on:
See also:

Thomas Hartmann - 2014-12-04 16:30:50 +0100

when i run ft_sourceplot in ortho mode under matlab 2014b, the color limits were only set for the bottom left view. i digged into it and found that this might have something to do with matlab's new graphics system. the caxis function, setting the color limits in line 1464 only applies to the last plotted image. i resolved this by fixing another bug: ft_plot_ortho does not accept 'colorlim' keywords. instead, they are called 'clim'. i created a pull request on git. i do not know if this solves the problem completely, but it works for me.... best, thomas

Jim Herring - 2014-12-10 14:48:41 +0100

Hi Thomas, it seems the issue is still there for me. It appears that the limits are now set correctly but the functional data disappears as soon as the cursors are drawn, this happens starting on line 1501 if opt.crosshair if opt.init hch1 = crosshair([xi 1 zi], 'parent', opt.handlesaxes(1)); hch3 = crosshair([xi yi opt.dim(3)], 'parent', opt.handlesaxes(3)); hch2 = crosshair([opt.dim(1) yi zi], 'parent', opt.handlesaxes(2)); opt.handlescross = [hch1(:)';hch2(:)';hch3(:)']; else crosshair([xi 1 zi], 'handle', opt.handlescross(1, :)); crosshair([opt.dim(1) yi zi], 'handle', opt.handlescross(2, :)); crosshair([xi yi opt.dim(3)], 'handle', opt.handlescross(3, :)); end end I recall that the ordering of layers in images changed in 2014b as well, so I'm guessing it has something to do with linking the crosshairs to axis and this causing the functional data to disappear behind the anatomical data.

Thomas Hartmann - 2014-12-10 15:36:01 +0100

hi jim, i cannot replicate your problem with matlab 2014b on windows. furthermore, it seems to be like this might be a new bug. so i think the best strategy would be to open a new bug report for it. best, thomas

Thomas Hartmann - 2015-06-11 16:03:55 +0200

already fixed

Robert Oostenveld - 2019-08-10 12:31:20 +0200

This closes a whole series of bugs that have been resolved (either FIXED/WONTFIX/INVALID) for quite some time. If you disagree, please file a new issue on