I also fwd this message to the mne_analysis at nmr.mgh.harvard.edu
Results of .drop_bad in v 0.16.2 (python 3.6.6) and .drop_bad_epochs in
0.12.dev (python 2.7.6) are different.
This is not filtering. I tested performance of the .drop_bad in v 0.16.2
(python 3.6.6) and .drop_bad_epochs in 0.12.dev (python 2.7.6) without any
additional operations on the data. Result is clearly different! The
difference, however, starts only after the 25th epoch.
I can confirm that the good epochs 25-89 (of 97) appear different with
`epochs.plot()`, despite the epochs.events and epochs.selections attributes
being the same. However `epochs.selection` shows that the first of the
original events that would be skipped is the 25th, so this is presumably a
bug with `mne.Epochs` selecting the wrong data under some circumstances.
Given that 0.12 is almost 3 years old now, we have fixed a lot of bugs
since then. It's likely that there is some bug in 0.12 that was fixed in
0.16 (or earlier). Can you provide a minimal script that takes the raw data
you sent (which appears to be identical in both archives?) and creates
`-epo.fif` files that differ between 0.12 and 0.16? The `mne.Epochs`
constructor parameters probably matter here.
Dear Eric,
I attached the scripts.
I am sure that the problem is with v0.16, not with v0.12, because if I use
v0.16, but do the bad epochs rejection manually the result is the same as
with v0.12.