Back to the main page.
Bug 2182 - ft_freqanalysis does not support the method 'mvar'
| Status | CLOSED FIXED |
| Reported | 2013-05-31 14:38:00 +0200 |
| Modified | 2014-01-29 13:39:37 +0100 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Windows |
| Importance: | P3 critical |
| Assigned to: | Roemer van der Meij |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Thomas Wunderle - 2013-05-31 14:38:13 +0200
Example Code: cfg = []; cfg.ntrials = 500; cfg.triallength = 1; cfg.fsample = 200; cfg.nsignal = 3; cfg.method = 'ar'; cfg.params(:,:,1) = [ 0.8 0 0 ;% x y z 0 0.9 0.5 ;% y 0.4 0 0.5];% z cfg.params(:,:,2) = [-0.5 0 0 ; 0 -0.8 0 ; 0 0 -0.2]; cfg.noisecov = [ 0.2 0 0 ; 0 0.2 0 ; 0 0 0.2]; data = ft_connectivitysimulation(cfg); cfg = []; cfg.order = 5; cfg.toolbox = 'bsmart'; mdata = ft_mvaranalysis(cfg, data); cfg = []; cfg.method = 'mvar'; mfreq = ft_freqanalysis(cfg, mdata); the input is mvar data ??? Error using ==> ft_freqanalysis at 294 specified cfg.method is not supported %%%%----------------------------------------------------- I get the same error for my script of real data The data of ft_freqanalysis is from 22.5.2013
Eelke Spaak - 2013-05-31 14:49:21 +0200
@Thomas: apologies for the inconvenience, this is indeed a bug, introduced on May 22. For the time being, you could work around it by either downloading an older FT version, or, probably easier, replacing your copy of ft_freqanalysis with the previous revision: https://fieldtrip.googlecode.com/svn-history/r7462/trunk/ft_freqanalysis.m @Roemer, this was caused by your removal of the pre-specest stuff from ft_freqanalysis. (I tested it with r7462 and it still works there.) I would try to fix it, but I think you could do it better/faster than me, so I'm assigning this to you :)
Roemer van der Meij - 2013-05-31 15:22:57 +0200
@Thomas, for the moment, you can call ft_freqanalysis_mvar directly. The end result should be the same, and you can keep your current version. Sorry, that totally didn't cross my mind when I removed the legacy stuff. Thanks for spotting this and assigning me Eelke. Hmmm, this is something we need to discuss in a meeting with JM (CC'd). Mvar is a bit of an oddball. I don't immediately know how we should deal with this. Keep it? Make it a main function by itself? Let's discuss
Roemer van der Meij - 2013-06-06 15:01:33 +0200
Hi Thomas, We decided to keep the exception for method = 'mvar', you can now call it again via ft_freqanalysis. The changes should be on the ftp server tonight. All the best, Roemer