every time single bad epochs dropped

Support & Discussions
1

every time single bad epochs is dropped

2

Hello,

What are we suppose to understand by that single phrase?
If you want help with your MNE-related code and projects, please take the time to correctly describe your problem, ideally by providing a minimally reproducible example, i.e. a code snippet we can copy/paste, that will run locally on our computers and that will exhibit the issue.

Mathieu

1 Like
3

Sorry by mistake i pressed the submit button.

I have 2 sec EEG text data and using mne.io. RawArray i am creating raw data and concatenating it. Then creating epochs using mne.epochs.But every time 1 bad epochs dropped due to TOO-SHORT.

1 Like
4

Hello, this usually means that one of the events used to create the epochs is too close to the beginning or the end of the raw data, hence the epoch would become “too short” and it is therefore dropped.

Richard

5

Thank you Richard foryour quick response,
but i changed the files and tested it. copyied the same file in multiple times and getting the same result (1 bad epochs dropped due to TOO-SHORT).

6

Like I said, it appears that one of the event markers is too close to the end of the file, hence that epoch cannot be created. It would commonly be the very first or very last event.

7

Thank you richard