Back to the main page.
Bug 2327 - stay consistent with cfg.parameter being mandatory for freq-data
| Status | CLOSED WONTFIX |
| 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 |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| 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