question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Document EEG reference

See original GitHub issue

We keep getting questions of users that are confused with MNE’s EEG referencing behavior. This is not surprising, as the documentation does not cover this topic. At the very least, we need to add a note that for EEG data, a reference must be specified at all times. If the user does nothing, MNE will add an average reference. If another reference is desired, the user should use the mne.io.set_eeg_reference function to specify this.

[Edit by Eric89GXL: also, need to add a tutorial]

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Reactions:1
  • Comments:12 (12 by maintainers)

github_iconTop GitHub Comments

4reactions
larsonercommented, Aug 29, 2016

This is really a dup of #3410, but I’ll close that one since this one has a richer discussion.

Both of these are almost a dup of #2727, which highlights how we have done some inconsistent things with add_egg_ref for a long time.

I agree with @agramfort (now) that we should add a method. But I would go a step further and make it the only way to add an EEG reference. It’s more pythonic than having add_eeg_ref args, sometimes defaulting to True, sporadically placed in our code – which is what we have now. So I’d actually really prefer deprecating all add_eeg_ref args. Perhaps more importantly, it forces people to be more explicit about when the average reference gets added. We already have safeguards against inversion without average ref, so we should be safe to do this.

1reaction
agramfortcommented, Aug 29, 2016

+1 to add such documentation. Any suggestion where?

also the more I get questions about EEG reference the more I feel that:

mne.io.set_eeg_reference

is not easy to find and the io module is clearly not a naturally place to look.

2 options:

  • move mne.io.set_eeg_reference to mne.set_eeg_reference
  • add a set_eeg_reference method to the data containers. I know I was opposed to this to keep the number of methods low but it’s true that it’s a quite general use case…
Read more comments on GitHub >

github_iconTop Results From Across the Web

Setting the EEG reference — MNE 1.3.dev0 documentation
Setting the EEG reference#. This tutorial describes how to set or change the EEG reference in MNE-Python. As usual we'll start by importing ......
Read more >
Re-reference EEG and iEEG data - FieldTrip toolbox
EEG and intracranial EEG (iEEG) data, which includes sEEG and ECoG, is often recorded relative to a reference electrode that is good for...
Read more >
b. Re-referencing - EEGLAB Wiki
REST (Reference Electrode Standardization Technique) is a re-reference technique for translating multichannel EEG to a new dataset with reference at Infinity ...
Read more >
Re-Referencing EEG data - CREx
Re-referencing only applies to EEG data, MEG is reference-free. In EEG, voltages recorded at each electrode are relative to voltages recorded at other ......
Read more >
Reference System
Thus, the reference is either along the midline, or is a combination of symmetrical sites in both hemispheres (usually either the mastoid behind...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found