Richard Höchenberger

> and the virtual bipolar channel would assume the location of the `ECG-` electrode, which is not really what we want, right? Thinking about it, I guess this would be...

> and it doesn't solve the issue for mne-bids, because MNE-Python just reads the "ECG" channel and has no clue that it was made out of two electrodes that are...

I think I've got an idea how to solve the issue within the existing specs. Starting from the thought about how "ordinary" EEG channels are handled. We always have an...

> I guess the only file format that stores the data (i.e., a row in the channels x timepoints matrix) from **electrodes**, as opposed to from **channels** is Biosemi, as...

> The second part of what you write sounds like you are thinking more about a "read" or "read-BIDS" perspective. And I don't see where you refer to raw files...

> Okay, now I know what you mean --> but the reality is probably (?) that Raw files do _not_ contain data for each electrode. This is fine too. In...

(edited above example channels.tsv a bunch of times)

> Do you think there would be harm in being more permissive with `mne-bids` and applying the hierarchical structure even if it's not supported by BIDS? We don't even really...

> I agree but I think an important caveat is that if it passes the BIDS-validator and has for some time, even if it's not part of the BIDS-specification, I...

> and if users don't do it we keep writing `n/a`? Yeah… I mean, if you will, this follows the principle we're applying to events already: if they are not...