Back to the main page.

Bug 1607 - realigning channel order changes ft_topoplots

Reported 2012-07-09 19:14:00 +0200
Modified 2015-07-15 13:21:17 +0200
Product: FieldTrip
Component: plotting
Version: unspecified
Hardware: PC
Operating System: Linux
Importance: P3 normal
Assigned to: Jim Herring
Depends on:
See also:

jonas van nijnatten - 2012-07-09 19:14:33 +0200

During preprocessing I lost some channels which I got back through ft_channelrepair after which the channel order changed per subject. I realigned the channel order and the associated data structure of each subject to one reference order after which the topoplots look completely different. They look even worse than before realignment. Anybody got a clue where the confusion arises? Attached a script and two data files, one with reference data and one with the to be aligned data.

jonas van nijnatten - 2012-07-09 19:22:53 +0200

Created attachment 292 data with chan reference and to be aligned data

Jörn M. Horschig - 2012-07-10 13:17:36 +0200

I'm gonna have a look and see whether it's a quick fix

Jörn M. Horschig - 2012-07-10 13:33:58 +0200

try doing: nERPdata_nD_left{isubject}.avg(loc,:) = ERPdata_nD_left{isubject}.avg(:,:); % realign data to ref channel order instead then it works fine

Jörn M. Horschig - 2012-08-23 14:02:03 +0200

bug closing time (

Jan-Mathijs Schoffelen - 2012-09-26 13:59:42 +0200

Stephen thinks that it still does not work. He is going to provide a snippet of code and some data so that we can reproduce and fix.

Jan-Mathijs Schoffelen - 2012-10-31 13:49:47 +0100

*** Bug 1800 has been marked as a duplicate of this bug. ***

Diego Lozano Soldevilla - 2013-02-13 13:34:15 +0100

is this still relevant? if not, close please

Jim Herring - 2013-02-27 10:50:59 +0100

Changing channel order by shuffling channels does not result in different topo/multiplots. This bug was possibly related to bug 1986.

Jim Herring - 2013-02-27 10:53:37 +0100

On second thought, the initial 'bug' was no bug and Stephen's second thoughts might have been related to bug1986. Therefore I've changed the status to invalid.