Back to the main page.

Bug 3476 - ft_multiplot_ER/ ft_singleplot_ER linestyle error

Reported 2019-08-28 10:39:00 +0200
Modified 2019-08-30 12:54:14 +0200
Product: FieldTrip
Component: core
Version: unspecified
Hardware: PC
Operating System: Windows
Importance: P5 normal
Assigned to: Jan-Mathijs Schoffelen
Depends on:
See also:

Jac - 2019-08-28 10:39:05 +0200

Created attachment 884 should load and run code in bug description. 4 lines/ 5 data points I'm using both single and multiplot with the code below. My linestyle is always the 4th style with no error. From going through the multiplot code the line: ft_plot_vector(xval, yval, 'width', chanWidth(m), 'height', chanHeight(m), 'hpos', chanX(m), 'vpos', chanY(m), 'hlim', [xmin xmax], 'vlim', [ymin ymax], 'color', graphcolor, 'style', cfg.linestyle{i}, 'linewidth', cfg.linewidth, 'axis', cfg.axes, 'highlight', mask, 'highlightstyle', cfg.maskstyle); ... is only called when i=4, i.e. the last data set. So the output makes sense, but seems to be a bug. %%%%%%%%% example code load exampledata cfg=[] cfg.layout = 'biosemi64.lay'; = 'no' layout = ft_prepare_layout(cfg); cfg = []; cfg.parameter = 'avg'; = 'all'; cfg.baseline = 'no' ;% FT_TIMELOCKBASELINE cfg.trials = 'all' ; cfg.axes = 'yes'; = 'no'; cfg.showlabels = 'no' ; cfg.showoutline = 'no'; cfg.showscale = 'yes'; cfg.showcomment = 'yes' ; cfg.interactive = 'yes' ; cfg.graphcolor = 'rgbrgb'; cfg.layout = layout; cfg.linestyle={'-','--','-',':'}; %both multi and singleplot ER select : for all lines ft_multiplotER(cfg, erp1{1}, erp1{2}, erp2{1}, erp2{2})

Jan-Mathijs Schoffelen - 2019-08-30 11:08:19 +0200

Created attachment 885 figure output not confirming the issue

Jan-Mathijs Schoffelen - 2019-08-30 11:09:43 +0200

Hi Jac, Thanks for the example code and data. I must say that I cannot reproduce the reported issue. I have attached a figure that I got, while executing the code. Can you confirm that you use a sufficiently recent version of the fieldtrip code?

Jac - 2019-08-30 12:52:46 +0200

Thank you for taking a look - I've updated to 20190828 and the error has resolved The issues is with 20181101 - apologies for not checking that, I did check for any known bugs with earlier versions. I will update fieldtrip post for info.

Jan-Mathijs Schoffelen - 2019-08-30 12:54:14 +0200

No worries. Happy computing! Closing for now.