Back to the main page.

Bug 255 - topoplotER does not accept 1 dimensional data

Status	CLOSED FIXED
Reported	2010-12-01 16:25:00 +0100
Modified	2011-01-26 15:38:31 +0100
Product:	FieldTrip
Component:	plotting
Version:	unspecified
Hardware:	PC
Operating System:	All
Importance:	P1 normal
Assigned to:	Roemer van der Meij
URL:
Tags:
Depends on:
Blocks:
See also:

Roemer van der Meij - 2010-12-01 16:25:32 +0100

At the moment, topoplotER does not accept data which only has a 'chan' as dimord. Even though this should still be possible to plot, and is expected implicitly.

Jan-Mathijs Schoffelen - 2010-12-27 10:18:29 +0100

What kind of data actually only has a 'chan' dimord? At the moment I am working on the code a bit, to solve a bug which was introduced when ft_selectdata was built-in ;-). I just as well tackle this issue, but could you inform me what high-level function call causes a crash?

Roemer van der Meij - 2010-12-27 12:07:27 +0100

Ft_selectdata? **whistling a tune while looking innocently towards the sky** Form the top of my head, it would only be chan_freq data and chan_time data, that has been averaged during statistics with the cfg.avgoverfreq and cfg.avgovertime options. So, at the moment I can't think of any other examples than output from freg/timelockstatistics (with avg = yes) causing a crash when trying to plot it with zparam = stat.

Jan-Mathijs Schoffelen - 2010-12-27 13:41:46 +0100

it should work now after updating ft_topoplotER. See fieldtrip/testing/test_bug255.m Could you check and close the bug if this is indeed the case?

Robert Oostenveld - 2011-01-26 15:37:11 +0100

I closed all bugs that were resolved prior and including 2011-01-25. All resolved bugs should have been discussed by now, therefore we don't want to see them again in the next meeting. Instead, in the next meeting we want to see the recent improvements and fixes.