Back to the main page.
Bug 1484 - ft_freqbaseline uses cfg.param instead of cfg.parameter (which would be consistent with other functions)
| Status | CLOSED FIXED |
| Reported | 2012-05-21 10:14:00 +0200 |
| Modified | 2012-08-23 14:02:11 +0200 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Windows |
| Importance: | P3 normal |
| Assigned to: | Jörn M. Horschig |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Stephen Whitmarsh - 2012-05-21 10:14:06 +0200
Also, ft_timelockbaseline doesn't seem to support a (or multiple) parameters, at least not in the documentation.
Jörn M. Horschig - 2012-06-13 15:38:54 +0200
svn ci ft_freqanalysis.m ft_timelockbaseline.m -m "bugfix-#1484-freqbaseline works on cfg.parameter now (as it should be, renamed from cfg.param). timelockbaseline does support cfg.parameter as well as ft_freqanalysis does." Sending ft_timelockbaseline.m Transmitting file data . Committed revision 6054. good that you mentioned that btw, the plotting functions have all been changed to cfg.parameter but freqbaseline not, which resulted in freqbaseline in adjusting data.powspctrm instead of data.(cfg.parameter). I also added functionality for ft_timelockanalysis. Does it make sense to support cfg.baselinetype also for timelock-data? I had no real test data for timelockdata, so I hope functionality/output is still correct... Stephen, can you quickly check?
Stephen Whitmarsh - 2012-06-13 16:28:35 +0200
I ran it through my script and tested it on multiple inputs to cfg.parameter - works like a charm. Thanks! S