Back to the main page.

Bug 2641 - Error in ft_checkconfig using ft_spiketriggeredspectrum

Reported 2014-07-08 19:17:00 +0200
Modified 2015-07-15 13:31:23 +0200
Product: FieldTrip
Component: spike
Version: unspecified
Hardware: PC
Operating System: Linux
Importance: P5 normal
Assigned to: Jan-Mathijs Schoffelen
Depends on:
See also:

Thomas Wunderle - 2014-07-08 19:17:54 +0200

I'm trying to use "ft_spiketriggeredspectrum" to compute the phase of the LFP around a spike for a subsequent PPC analysis. Using the following code, cfg = []; cfg.method = 'mtmconvol'; cfg.foi = [2:2:100] cfg.t_ftimwin = (1./cfg.foi)*3; [sts] = ft_spiketriggeredspectrum(cfg,lfp,FT_Spike); I get the error: ??? Error using ==> ft_checkconfig at 205 The field cfg.progress is not allowed Error in ==> ft_spiketriggeredspectrum_convol at 135 cfg = ft_checkconfig(cfg, 'allowed', {'taper', 'borderspikes', 't_ftimwin', 'foi', 'spikechannel', 'channel', 'taperopt', 'rejectsaturation','tapsmofrq', 'warning'}); Error in ==> LaminarCoherence_Spike1 at 403 [sts] = ft_spiketriggeredspectrum_convol(cfg,lfp,FT_Spike); %%%------------------------------------------------------------------ It seems that in ft_checkconfig the string 'progress' is missing. adding 'progress' to the code below fixes the bug for me -> Code from ft_checkconfig % % check for required fields, give error when missing %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% if ~isempty(allowed) % there are some general options that should always be allowed allowed = union(allowed, { 'trackconfig' 'checkconfig' 'checksize' 'showcallinfo' 'trackcallinfo' 'trackdatainfo' 'trackparaminfo' 'debug' ---> 'progress' }); fieldsused = fieldnames(cfg); [c, i] = setdiff(fieldsused, allowed); if ~isempty(c) error('The field cfg.%s is not allowed\n', c{1}); end end %%%----------------------------------------------------------------------------- Best, Thomas

Thomas Wunderle - 2014-07-10 11:13:02 +0200

P.S. FieldTrip version r8941 does not produce the error.

Jan-Mathijs Schoffelen - 2015-02-11 11:02:06 +0100

It seems that this issue has been fixed with Diego addressing 2674. Closing for now. Please feel free to re-open if the problem persists.