Back to the main page.
Bug 1005 - parameter in sourceinterpolate is a string by default whereas the function expects a cell-array
Status | CLOSED FIXED |
Reported | 2011-10-04 11:18:00 +0200 |
Modified | 2011-11-09 14:37:45 +0100 |
Product: | FieldTrip |
Component: | core |
Version: | unspecified |
Hardware: | PC |
Operating System: | Windows |
Importance: | P1 normal |
Assigned to: | Jörn M. Horschig |
URL: | |
Tags: | |
Depends on: | |
Blocks: | |
See also: |
Jörn M. Horschig - 2011-10-04 11:18:54 +0200
no one has tested this functions with the default cfg settings, has someone? ;)
Jörn M. Horschig - 2011-10-05 10:21:24 +0200
hm k, another one ;) what parameters are possible at all? Is there a list of options somewhere?
Jan-Mathijs Schoffelen - 2011-10-06 13:49:04 +0200
Hi Jörn, just committed test_tutorial_beamformer -> seems to run through fine, do your problems still persist?
Jörn M. Horschig - 2011-10-07 08:54:28 +0200
I could run the function without problems yesterday, did something change?
Jan-Mathijs Schoffelen - 2011-10-07 09:04:11 +0200
I don't know? Did you check google code?
Jörn M. Horschig - 2011-10-11 16:37:17 +0200
The problem only occurs if is2Dfun is true. In the for loop of line 206/236/261, it loops from k=1:numel(cfg.parameter) and tries to access cfg.parameter{k}, which it cannot if cfg.parameter = 'all' Adding these lines helps: % select the parameters that should be interpolated cfg.parameter = parameterselection(cfg.parameter, functional); cfg.parameter = setdiff(cfg.parameter, 'inside'); % inside is handled separately that is being done in all the other cases, but not for the two above mentioned cases. Is that a correct fix, does it make sense?