Back to the main page.

Bug 1499 - ft_singleplotER does not plot statistical error

Reported 2012-05-31 13:36:00 +0200
Modified 2019-08-10 12:33:12 +0200
Product: FieldTrip
Component: plotting
Version: unspecified
Hardware: PC
Operating System: Mac OS
Importance: P3 enhancement
Assigned to: Martin Vinck
Depends on:
See also:

Martin Vinck - 2012-05-31 13:36:33 +0200

I think, it is desired to have a configuration option for plotting SEMs, 95% conf. levels and STDs.

Martin Vinck - 2012-05-31 13:37:37 +0200

robert you know who to assign this to?

Robert Oostenveld - 2012-05-31 14:10:23 +0200

The ft_plot_vector function has % highlight = a logical vector of size Y, where 1 means that the corresponding values in Y are highlighted (according to the highlightstyle) % highlightstyle = can be 'box', 'thickness', 'saturation', 'difference' (default='box') It makes sense to extend this with highlight = boolean or scalar valued vector of size Y highlightstyle = errorbar, confidence, ... where errorbar would at each data point make an upward and downward whisker line, and confidence would make a grey zone around the line. These low-level options are mapped to cfg.maskstyle and cfg.maskparameter in ft_singleplotER., so that function does not have to be extended (except for the documentation). I suggest you implement it yourself. The switch highlightstyle case 'box' case 'thickness' ... in ft_plot_vector should be easy to extend. Please make a test and demo script and also see fieldtrip/test/test_bug1447.m and bug #1447.

Jan-Mathijs Schoffelen - 2016-02-21 14:26:38 +0100

Change status for now. There was no major progress on this bug, and the reporter did not find it urgent enough to push it. Feel free to re-open once if Martin can assign it to somebody who wants to implement it, or when a git pull request for an improved version of ft_plot_vector is available

Robert Oostenveld - 2019-08-10 12:33:12 +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