This is a collaborative space. In order to contribute, send an email to maximilien.chaumon@icm-institute.org
On any page, type the letter L on your keyboard to add a "Label" to the page, which will make search easier.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

DRAFT

Define an EEG datatype

All Apps use the meg/fif datatype when they directly preprocess the file containing the signals. But some app can preprocess both EEG and MEG data (app-notch-filtering, app-resampling, app-temporal-filtering, app-get-events, and app-make-epochs).

Files in fif format can contain both MEG and EEG data: to select EEG, you have to specify it with the parameter param_picks_by_channel_types_or_names (except for the app-get-events, a MNE function pick() may be added to that App).

But for now no EEG datatype we can use exists, so a discussion about EEG datatype is to needed. The apps app-notch-filtering, app-resampling, app-temporal-filtering, app-get-events, and app-make-epochs should run correctly with EEG data stored in a fif file, so maybe it would be interesting to create a eeg/fif datatype. However fif is a format that is not usually used for EEG…

HTML reports

The structure of the report needs to be discussed. It’s important for the App user to be able to visualize easily the signals.

Ideas of improvements:

  • Let the user decide the parameters of the plots (the scaling especially) and the plots to display

  • Add other plots like topoplots

Assess the quality of the correction

We looked for a value to quantify the efficacy of the correction. A SNR computation was found but has to be improve

  • No labels