Richard Höchenberger

> 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. How did you...

> * mark all channels as flat that have flat-annotated segments in 5% of their data Oh wait, that won't work, since the function doesn't return the individual scores. So...

Thanks @jasmainak! Yes definitely do loop me in if you can :) At the most basic level, I think we can agree that it would be good to have automated...

> A potential issue may be that users do not screen their data after MNE's "auto" detection of bad chs and segments --> and then in the resulting dataset, the...

> What we need to "fix" in a larger group with more stakeholders: > > 1. how to annotate "bad segments" for subgroups of channels instead of "ALL" channels -->...

> and also be able to interpolate these time intervals and channels 🤷‍♂️ I think this is what autoreject can do on an Epochs level. But yeah…

> I'd go for **doing**, and marking more bad than strictly necessary. In this case we should definitely discuss adding the equivalent of channel.tsv's `status_description` column to `events.tsv`, so we...

Ok so let's just follow the basic approach @agramfort suggested: problematic channels will be marked as bad (and we'll add a comment to `status_description`), and problematic time segments will get...

Sounds like a job for me! 😁

> Most likely because it's a tsv file, we need to store a separate row for each channel that an event occurs in. I don't understand this. We could simply...