Bad segments and bad epochs

Hi Marc,

Indeed, this field is not much used in Brainstorm.
It is read from two file formats (EEGLAB .set and EGI .raw) for data that is already fully pre-processed and epoched. These files should not be imported as "raw continuous" but directly as epochs in Brainstorm (using menu "Import MEG/EEG" instead of "Review raw file"), because there is not much that can be done with them otherwise. Therefore I can't see any use case where it would useful for the function GetBadSegment to retreive this info...

When importing EEGLAB .set or EGI .raw files as epochs, the epoch(i).bad info is used to mark the imported trial as good or bad in the Brainstorm database:

The CTF format has such bad epochs (in the file ClassFile.cls) and even bad segments (in the file bad.segments), but they are currently not read by Brainstorm. Is this something we want to do?

No one ever requested this, so I'm not sure it is worth investing time in it.
Do you have any clear use case in which there is some important information that is missing in the CTF recordings as currently processed by Brainstorm?