Stefan Appelhoff

I like this suggestion as well :+1:

Thanks for reporting! I assume you are using mne_bids with version `0.2` and NOT the development version? You can check your version by calling `mne_bids --version` from the command line....

> Do I miss something? no, you are right ... but there is a different column in `events.tsv` files called [`value`](https://bids-specification.readthedocs.io/en/latest/04-modality-specific-files/05-task-events.html#task-events) (see the table) which refers to the actual value...

I agree @hstojic. When reading a BIDS `events.tsv` we should use the `values` column as the "value" in a potential `events_id` dictionary ... and the `trial_type` column as the "key"...

I recommend that you use https://github.com/cli/cli ... it simplifies these sorts of things remarkably well. See the following screenshot (upper right corner in the image):  but for the record,...

Is the reference channel listed in the VHDR file? To my knowledge it might show up under "impedances", but not otherwise 🤔 Do you have a `[Coordinates]` section in your...

> yes, I recorded channel positions (with a polhemus fasttrack device, in this case). sorry if this didnt come through! It did come through - thanks for the info on...

IMHO: - `n/a` is kind of a "reserved" value in BIDS. It **always** means: "this data is not available". Maybe we need to clarify this somewhere - optional fields/columns that...

@timonmerk the `raw.filename` attribute is used in MNE-BIDS: - to infer the manufacturer (and then automatically fill in some BIDS fields): https://github.com/mne-tools/mne-bids/blob/4930b7a6787736c115a2d1c93cea3cfd87da25e8/mne_bids/write.py#L110-L111 - if a FIF file is detected, to...

This sounds immensely helpful! AFAIK the MNE detect_flat_chs function also marks segments ... and only if there are too many segments flat, then the whole channel is marked as flat....