Skip to content

Commit 4e6433d

Browse files
committed
Addressing changes
1 parent 32f2b4e commit 4e6433d

1 file changed

Lines changed: 9 additions & 5 deletions

File tree

examples/preprocessing/plot_epoch_quality.py

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -110,11 +110,15 @@
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)
112112
# which contained strong artifact activity. The remaining good epochs can then be used
113-
# for further analysis. In this case, the large frontal deflections are likely blink
114-
# artifacts, so dropping is not the only option. For artifacts like these, it can be
115-
# preferable to repair the data and keep more epochs, for example with
116-
# :ref:`ICA <tut-artifact-ica>` or
117-
# :ref:`regression-based artifact correction <tut-artifact-regression>`.
113+
# for further analysis.
114+
#
115+
# .. admonition:: Repairing and retaining epochs with artifacts
116+
#
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>`.
118122
epochs.drop(np.where(scores >= 0.6)[0])
119123
print(f"Epochs remaining after dropping scores ≥ 0.6: {len(epochs)}")
120124

0 commit comments

Comments
 (0)