Back to the main page.
Bug 2071 - ft_postamble history disregards multiple data structures
| Status | CLOSED WORKSFORME |
| Reported | 2013-03-20 16:57:00 +0100 |
| Modified | 2014-03-12 12:21:35 +0100 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Windows |
| Importance: | P3 normal |
| Assigned to: | Jörn M. Horschig |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Jörn M. Horschig - 2013-03-20 16:57:19 +0100
I realized that ft_math fails and found that it fails only for multiple input arguments because ft_selectdata is creating a cfg for the first input data structured but not the second (and possibly also third, fourth, ...). The history bookkeeping is in hands of ft_postamble: ft_postamble history varargout
Robert Oostenveld - 2013-03-22 11:22:26 +0100
fieldtrip functions should not output multiple FT data structures, i.e. it converges from multiple inputs to one output. Ah, I now that it also does not, there is no varargout in the function. So your ft_postamble history varargout should read ft_postamble history varargin for the history obtained from the multiple inputs. Needed here is a test script like data1 = [] data1.label = {'1', '2', '3', '4'}; ... data2 = [] data2.label = {''2', '3', '1', '4'}; % different order ... data3 = [] data3.label = {''3', '4', '1'}; % channel missing ... and then dataout = ft_math(cfg, data1, data2, data3)