Back to the main page.
Bug 745 - similar to cfg.trials and cfg.channel, functions should get an option cfg.latency
| Status | CLOSED WONTFIX |
| Reported | 2011-06-08 13:44:00 +0200 |
| Modified | 2014-05-14 20:08:57 +0200 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Windows |
| Importance: | P1 enhancement |
| Assigned to: | Robert Oostenveld |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | 1021 |
| See also: |
Jan-Mathijs Schoffelen - 2011-06-08 13:44:38 +0200
use ft_selectdata for this make consistent with cfg.vartrllength in timelockanalysis
Jan-Mathijs Schoffelen - 2011-08-10 21:49:37 +0200
this needs to apply to functions: ft_preprocessing ft_freqanalysis ft_timelockanalysis ft_XXXgrandaverage ft_XXXstatistics and possibly others
Robert Oostenveld - 2014-04-14 14:00:37 +0200
last week in the FT meeting we discussed whether cfg.latency is needed/desired. I (=Robert) argued against it in general, using the following arguments: 1) time is easy to select in the plot, whereas channels are not so easily selected 2) it does not affect the output of the computations in the window of interest 3) it does not significantly increase the size of the output data 4) it does not significantly increase the computational costs 5) functions that need it, presently rely on ft_definetrial/ft_preprocessing. The latest implementation of ft_selectdata allows for selections of latency for all supported inputs. So the user can do it him/herself as a separate step. There is presently not a need to implement this in all FT functions.