Back to the main page.

Bug 2550 - ER tutorial says padding is only possible for continuous data

Reported 2014-04-30 09:40:00 +0200
Modified 2019-08-10 12:29:26 +0200
Product: FieldTrip
Component: documentation
Version: unspecified
Hardware: PC
Operating System: Windows
Importance: P5 normal
Assigned to:
Depends on:
See also:

Jörn M. Horschig - 2014-04-30 09:40:41 +0200

quote "Padding can only be done on data that is stored in continuous format, therefore it is not used here. " This is outdated and should be changed, but how to? Refer to the documentation of the padding function?

Robert Oostenveld - 2014-04-30 10:00:55 +0200

data padding is only possible if there is data around the defined trials. The Subject01 dataset was recorded in epoched mode, i.e. it consists of 900 sample segments with gaps in between. The trial function defines these 900 sample segments, reading more data around it would result in discontinuous jumps at sample -300 and +600.

Jörn M. Horschig - 2014-04-30 10:14:25 +0200

ah right, I see. Then I misunderstood the quote. I was thinking along the lines that we now have mirror padding, edge padding, etc, which could be used (in theory). Also, maybe information about the epoched mode should be added, because it is not explained in the tutorial nor in the dataset description

Robert Oostenveld - 2014-04-30 10:51:33 +0200

I have added The MEG data are stored as epochs or trials of fixed length around each stimulus trigger, i.e. the file does not represent a continuous record of the data and the data in the inter-trial-interval is not stored. The consequence is that the data cannot be represented as a continuous record, as at the epoch boundaries there is a discontinuity. See also the background on the CTF system. to the shared documentation, and also some text to the getting_started/ctf section.

Robert Oostenveld - 2019-08-10 12:29:26 +0200

This closes a whole series of bugs that have been resolved (either FIXED/WONTFIX/INVALID) for quite some time. If you disagree, please file a new issue describing the issue on