Richard Höchenberger

@adam2392 > Hmm not sure... Can we add an array to a .tsv file? If so, how does it look? @hoechenberger However you like, I mean, depends on how you...

> This looks good to me! I am okay with enabling this in one go with #928 ? Yes let's do that! :)

> I would just be careful that doing .set_montage(None) will remove head > shape dig points for coregistration. > > Message ID: ***@***.***> > > > Very good point. Then...

... and for M/EEG data we should write _electrodes.tsv, which we currently don't do. @sappelhoff can you confirm?

@agramfort to clarify, all positions stored in _electrodes.tsv will be restored as DigPoints upon reading. That's why I'm suggesting that we drop all EEG DigPoints from the info, and then...

That is indeed a valid point... @sappelhoff @adam2392 @alexrockhill @larsoner What is your opinion on this? The question is: - if data in a BIDS dataset stores information in `info`...

> > ... and for M/EEG data we should write _electrodes.tsv, > > it should ... but only if we know that we don't write template data, but **measured** data....

Hello, thanks for your report! > but when one session has multiple runs, the electrode.tsv get's overwritten, so the electrode tsv created by the upper code is only written out...

Seeing this error message also got me thinking – we removed that in `master`, right? Would @timonmerk run into issues then? 😱

@sappelhoff what I meant is that we now allow a deviation between sidecar and raw channels. I'm wondering if @timonmerk would've even figured something was wrong so easily with master