Richard Höchenberger

> even if I change the channels.tsv file to have V and not uV it does not > change anything > > > Message ID: ***@***.***> > > > This...

@agramfort > if the units are not present in the edf files we require to pass it on read_raw_edf? I'd say yes; fail hard and force users to specify the...

Closing as addressed upstream in https://github.com/mne-tools/mne-python/pull/11099; actually reading the units from `channels.tsv` is to be addressed in https://github.com/mne-tools/mne-bids/pull/1045

I just realized that the title of this issue is exactly what we want to solve in #1045, so I'm re-opening.

Hello @JonathanVHoecke and thanks for getting in touch! The issue here is that, like you said, all additional columns are kind of arbitrary – the standard allows users to name...

@sappelhoff Do you think we should have a property `BIDSPath.scans` that returns a `DataFrame` of `scans.tsv`? Edit: No, actually, it should only return a `Series` or `dict` with the data...

Since `scans.tsv` provides metadata that's specific to individual recordings, I think the `BIDSPath` of an individual recording should allow easy access to those metadata (i.e., one row of `scans.tsv`) There...

@sappelhoff In BIDS, is there a way to define which electrodes were combined (and how) to form a channel in `channels.tsv`, and to do that in an automatable fashion? For...

What one **could** do is: ``` name type units reference status status_description ECG+ ECG mV ECG- good n/a ``` but this would be an ugly hack, and the virtual bipolar...

cc @adam2392