Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • How much does MNE rely on the fif file format. Does it make sense to have data readers in all formats, and handle everything in fif internally? Is there a special case for the ctf .ds format? Question asked to Richard Höchenberger: MNE relies on .fif internally.

  • Head position alignment: before, after, independently of Maxfilter?

Discussion with Aina Puce following this meeting

  • Question of creating “data types” for different “data formats” (vendors) and different “types of data” (EEG, MEG, EOG… covariance matrix, calibration file, position file, freesurfer segmentation…)

Suggested “philosophy”:

  1. Several import datatypes depending on vendors convert to toolbox-specific (MNE for now) dataformat

  2. Processing datatypes with specific required files for each processing task

  3. Several export datatypes

Note

MNE can handle multimodal data containing different channel types (magnetometers, gradiometers, EEG, EOG, …), but sometimes we have to rename the channels before analysis. For instance, in Jas et al., 2018, the EEG061 and EEG062 electrodes were set as EOG, EEG063 was set as ECG. If this step is omitted, some preprocessing functions may fall back to potentially less optimal defaults, for example, using the average of the magnetometers instead of the ECG channel when searching for cardiac events.