Back to the main page.
Bug 3084 - ft_connectivityanalysis with cfg.method='psi' fails
| Status | CLOSED FIXED |
| Reported | 2016-03-01 13:16:00 +0100 |
| Modified | 2016-05-05 10:03:53 +0200 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Windows |
| Importance: | P5 normal |
| Assigned to: | Jan-Mathijs Schoffelen |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Johanna - 2016-03-01 13:16:39 +0100
Apologies if this was very recently fixed; I'm using the 20151216 version in prep for the KCLondon toolkit. I also am having temporary issues of updating to the recent version for my own purposes. When calling cfg=[]; cfg.method='psi'; psiout=ft_connectivityanalysis(cfg,mfreq) (using mfreq from http://www.fieldtriptoolbox.org/tutorial/connectivity) I get the error: Reference to non-existent field 'bandwidth'. Error in ft_connectivityanalysis (line 711) nbin = nearest(data.freq, data.freq(1)+cfg.bandwidth)-1; Suddenly on line 711 there seems to be a usage of cfg.bandwidth, but this cfg option doesn't seem to exist anywhere else in the code. Thank you, Johanna
Eelke Spaak - 2016-03-01 13:18:41 +0100
(In reply to Johanna from comment #0) I think psi (phase slope index) has always required the specification of cfg.bandwidth (although I'm not sure).
Jan-Mathijs Schoffelen - 2016-03-07 10:28:25 +0100
Indeed. I think this has always errored when omitting a cfg.bandwidth. I will build in a default.
Johanna - 2016-03-07 10:32:09 +0100
Even if a default value does not make sense, at least an informative check and error message at the top of the function would suffice, as well as advice on how to choose a bandwidth (what it means), would be great. Thanks!