Back to the main page.
Bug 1103 - 'linear' option missing in interp_ungridded
| Status | CLOSED FIXED |
| Reported | 2011-11-02 11:06:00 +0100 |
| Modified | 2011-11-09 16:43:38 +0100 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Windows |
| Importance: | P1 normal |
| Assigned to: | Jan-Mathijs Schoffelen |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Vladimir Litvak - 2011-11-02 11:06:51 +0100
Dear Johannes, Yes, this is a bug in FT, the only thing I don't get is how it has worked until now. In ft_sourceinterpolate the default interpmethod is 'linear' but it is not one of the method supported by the interpolation function interp_ungridded. Vladimir On Thu, Oct 27, 2011 at 2:08 PM, Johannes Gehrig <JoJo2003@web.de> wrote: Dear Vladimir, I'm testing the beamformer code you have sent him a while ago. Unfortunately the "code crashes" at line 426 calling ft_sourceinterpolate: ??? Error using ==> interp_ungridded at 130 unsupported projection method Error in ==> ft_sourceinterpolate at 221 interpmat = interp_ungridded(functional.pos, warp_apply(anatomical.transform, [X(:) Y(:) Z(:)]), ...
Jan-Mathijs Schoffelen - 2011-11-02 12:16:00 +0100
The original default (when ft_sourceinterpolate still only supported 3D -> 3D interpolation) interpolation method was linear. When doing more exotic interpolations, the function relies on interp_ungridded, which does not support linear as a method. I now made the default specific for each situation (by postponing the definition of the default until the specific situation has been determined).