Back to the main page.
Bug 104 - topoplotTFR cannot correctly refer to topoplotER with cfg.inputfile
| Status | CLOSED FIXED |
| Reported | 2010-07-01 16:11:00 +0200 |
| Modified | 2011-02-02 13:27:31 +0100 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Linux |
| Importance: | P1 enhancement |
| Assigned to: | Jan-Mathijs Schoffelen |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Tim Engelkes - 2010-07-01 16:11:51 +0200
TopoplotTFR refers to topoplotER It seems that the data=varargin{1} does not match with more input arguments which is what topoplotTFR recalls upon. However, it seems not correct to build in cfg.inputfile in this function since the data 'is' being checked in topoplotER. The code there sounds counterintuitive as topoplotER has in line 146: % Multiple data sets are not supported for topoplot: if length(varargin)>1 error('Multiple data sets are not supported for topoplotER/topoplotTFR.'); end Thus, with cfg.input data implemented for varargin there is an error concerning multiple and single input arguments? ??? Index exceeds matrix dimensions. Error in ==> ft_topoplotER at 165 data = varargin{1}; Error in ==> ft_topoplotTFR_new at 115 cfg=ft_topoplotER(cfg, varargin{:});
Robert Oostenveld - 2010-12-01 16:13:47 +0100
cfg.interactive=yes causes the multiplot/topoplot and singleplot to call each other. The option inputfile is meant for non-interactive use. cfg.interactive=yes and cfg.inputfile=something should be mutually exclusive.
Robert Oostenveld - 2011-01-16 22:50:48 +0100
changed the status for all ASSIGNED bugs to joint development user (fieldtrip-bugs) to status NEW, otherwise we don't see the in the Wednesday meetings.