Back to the main page.
Bug 2082 - ft_datatype_timelock: no requirement for .avg?
| Status | CLOSED FIXED |
| Reported | 2013-03-28 10:13:00 +0100 |
| Modified | 2015-01-27 17:15:39 +0100 |
| Product: | FieldTrip |
| Component: | documentation |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Windows |
| Importance: | P3 normal |
| Assigned to: | Johanna |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Jörn M. Horschig - 2013-03-28 10:13:54 +0100
http://fieldtrip.fcdonders.nl/reference/ft_datatype_timelock Required fields: - label, dimord, time that doesn't seem right, .avg is not required? with label, dimord and time, it could also be freq data. also, on top it says: FT_DATATYPE_FREQ describes the FieldTrip MATLAB structure for timelock data
Johanna - 2013-03-28 11:02:05 +0100
Hm. At the moment (of the current code that is), it does seem that .avg should be required. However, if I ever get around to finalizing bug 656 of making it possible that ft_timelockanalysis can compute only a .cov and not an .avg, then .avg should not be required, but rather either a .avg or a .cov required. Certainly the typo in the comments should be changed for the _FREQ thing!
Robert Oostenveld - 2013-03-28 12:57:57 +0100
it can also contain timelock.trial as 3-D array, which has dimord=rpt_chan_time. However, I would indeed expect either avg or trial (not as cell-array as in raw data, but as 3-D array) to be present.