File tree Expand file tree Collapse file tree
Expand file tree Collapse file tree Original file line number Diff line number Diff line change 105105)
106106
107107# %%
108- # Dropping suspicious epochs
108+ # Handling suspicious epochs
109109# --------------------------
110110# Following visual inspection, bad epochs can be discarded using the
111111# :meth:`mne.Epochs.drop` method. Here, we remove the worst scoring epochs (≥ 0.6)
114114#
115115# .. admonition:: Repairing and retaining epochs with artifacts
116116#
117- # In this case, the large frontal deflections are likely blink artifacts, so
118- # dropping is not the only option. For artifacts like these, it can be
119- # preferable to repair the data and keep more epochs, for example with
120- # :ref:`ICA <tut-artifact-ica>` or
121- # :ref:`regression-based artifact correction <tut-artifact-regression>`.
117+ # Dropping epochs is not the only option for handling artifacts. It may also be
118+ # possible to repair the data and retain these epochs. In this case, the large
119+ # deflections are likely blink artifacts, which can be repaired with techniques such
120+ # as :ref:`ICA <tut-artifact-ica>` and :ref:`regression <tut-artifact-regression>`.
122121epochs .drop (np .where (scores >= 0.6 )[0 ])
123122print (f"Epochs remaining after dropping scores ≥ 0.6: { len (epochs )} " )
124123
You can’t perform that action at this time.
0 commit comments