Back to the main page.

Bug 2327 - stay consistent with cfg.parameter being mandatory for freq-data

Reported 2013-10-18 13:38:00 +0200
Modified 2016-05-09 08:48:24 +0200
Product: FieldTrip
Component: core
Version: unspecified
Hardware: PC
Operating System: Windows
Importance: P3 minor
Assigned to: Jan-Mathijs Schoffelen
Depends on:
See also:

Jörn M. Horschig - 2013-10-18 13:38:25 +0200

not a real bug, just a bugger sometimes e.g. ft_topoplotTFR automatically assumes .powspctrm to be the default if cfg.parameter is not set ft_appendfreq does no such thing, even if 'standard' freq-structures are handed over with the same time, chans and freqs and .powspctrm present to do: - check such inconsistencies and verify if they do make sense or not. does it make sense to make cfg.parameter dependent on the input? e.g. coherence-data has .cohspctrm, which very likely should be used instead of .powspctrm.

Eelke Spaak - 2014-01-29 15:23:10 +0100

ft_combineplanar also only supports .powspctrm

Jan-Mathijs Schoffelen - 2016-02-24 09:22:47 +0100

insufficient interest in getting this one fixed over the past 2 years, so I suggest to close it right now, and optionally reopen it if the need arises.