[Mne_analysis] Dropping bad epochs

Denis A. Engemann denis-alexander.engemann at inria.fr
Mon Jan 28 15:34:34 EST 2019
Search archives:

        External Email - Use Caution        

Hi Dirk,

can you look into the epochs.drop_log and see what is the reason for rejection?
A common suspect is an event close to the end of a recording where the specified window length is not available.

Denis


> On Jan 28, 2019, at 9:25 PM, Dirk van Moorselaar <dirkvanmoorselaar at gmail.com> wrote:
> 
>        External Email - Use Caution        
> 
> Hi,
> 
> I am using the Epochs function to create a set of epochs. I have made
> sure I don’t make use of any of the reject options as I would like to
> read in all epochs and then run my own preprocessing function to
> select bad epochs (see example code below: currently I am using
> version 15). Yet, it seems in almost all my data sets one epoch is
> automatically dropped as it is marked as bad. While this is not the
> biggest problem in the world, I was wondering why this happens. In
> other words how could I make sure all epochs are actually created
> without droppig any of them??
> 
> Thanks in advance,
> 
> Dirk
> 
> Epochs(raw, events, event_id, tmin, tmax, flt_pad=True,
> baseline=(None, None), picks=None, preload=True,
>                reject=None, flat=None, proj=False, decim=1,
> reject_tmin=None, reject_tmax=None, detrend=None,
>                on_missing='error', reject_by_annotation=False, verbose=None)
> 
> _______________________________________________
> Mne_analysis mailing list
> Mne_analysis at nmr.mgh.harvard.edu
> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis




More information about the Mne_analysis mailing list