Back to the main page.

Bug 3468 - ft_selectdata forgets to select .trial field of spiketrial data, when selecting trials

Status NEW
Reported 2019-01-10 16:41:00 +0100
Modified 2019-01-10 16:53:30 +0100
Product: FieldTrip
Component: core
Version: unspecified
Hardware: PC
Operating System: Windows
Importance: P5 normal
Assigned to:
URL:
Tags:
Depends on:
Blocks:
See also:

Stephen Whitmarsh - 2019-01-10 16:41:38 +0100

For example, after selecting trials with ft_selectdata, I get the following (look at inconsistency between time/timestamp and trial fields): struct with fields: label: {'temp_0' 'temp_1' 'temp_2' 'temp_3'} samples: {[1×60105 double] [1×50841 double] [1×44124 double] [1×23579 double]} amplitude: {[2×60105 single] [2×50841 single] [2×44124 single] [2×23579 single]} timestamp: {[1×8246 double] [1×7651 double] [1×8386 double] [1×2938 double]} template: [4×5×97 double] template_maxchan: [2 3 4 5] time: {[1×8246 double] [1×7651 double] [1×8386 double] [1×2938 double]} trial: {[1×8252 double] [1×7665 double] [1×8400 double] [1×2939 double]} trialtime: [1885×2 double] trialinfo: [1885×7 double] cfg: [1×1 struct] Cheers, Stephen


Stephen Whitmarsh - 2019-01-10 16:44:15 +0100

Hold it, I got a Warning: could not determine dimord of "trial"... sjorrie


Stephen Whitmarsh - 2019-01-10 16:46:03 +0100

And neither can it determine dimord of pretty much any field. Soooo, I guess selectdata is not yet spikedata compatible?


Stephen Whitmarsh - 2019-01-10 16:47:32 +0100

Oh, it haz FT_SPIKE_SELECT! To at least get something out of this spamming: feature request to integrate FT_SPIKE_SELECT in FT_SELECTDATA peut-etre? Merci! Stephen


Stephen Whitmarsh - 2019-01-10 16:53:30 +0100

Another thing to think of, if that with ft_select_spike the trialtime and trialinfo field are not adjusted. It would make sense to me if it would.