Back to the main page.
Bug 1242 - databrowser time axis is incorrect for timelock input data
| Status | CLOSED FIXED |
| Reported | 2012-01-02 12:47:00 +0100 |
| Modified | 2013-01-17 10:44:45 +0100 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Mac OS |
| Importance: | P3 normal |
| Assigned to: | Roemer van der Meij |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Robert Oostenveld - 2012-01-02 12:47:19 +0100
I am using ft_databrowser to look at a timelocked ERP that starts at -0.5 seconds. The databrowser makes a time axis that starts at 0 seconds. See attached screenshot. to reproduce you can do load timelock.mat cfg = []; cfg.viewmode = 'butterfly'; ft_databrowser(cfg, timelock);
Robert Oostenveld - 2012-01-02 12:48:46 +0100
Created attachment 204 timelocked ERP data structure with 47 channels, time from -0.5 to 0.5 seconds
Boris Reuderink - 2012-01-03 10:47:22 +0100
I can't easily confirm due to bug 1237 (ft_getopt fails). But, since it is a defect by developer, I'll mark this bug as confirmed.
Boris Reuderink - 2012-01-03 11:20:03 +0100
Confirmed on mentat machine.
Jan-Mathijs Schoffelen - 2012-01-27 08:38:56 +0100
assigned bug to get all bugs lined up before the grand bug binge
Jörn M. Horschig - 2012-02-22 09:38:31 +0100
timelock data does only have one trial. If you do not specify cfg.continuous yourself, then by default, the data will be seen as a strip of continuous data, for which, logically, time always starts at 0. two possible ways to deal with the problem 1-keep it as it is 2-make cfg.continuous dependent on the existence of data.time
Roemer van der Meij - 2012-03-02 15:40:19 +0100
Stealing a few bugs ;)
Roemer van der Meij - 2012-08-01 15:43:07 +0200
Fixed by checking with ft_datatype whether the original data is timelock, and then not setting cfg.continous to yes when ntrial==1