[Mne_analysis] MEG eye blinks
Alexandre Gramfort
gramfort at nmr.mgh.harvard.edu
Tue Dec 11 14:38:13 EST 2012
hi vincent,
I would not add the events in the raw fif file as it means duplicating
the data on disk
and you need these only to compute an SSP projection.
A simple approach is to use 4s epochs with regularly spaced events and reject
4s windows that violated epochs rejection parameters.
You have a function for this:
https://github.com/mne-tools/mne-python/blob/master/mne/event.py#L262
Once you have epochs you can compute PSD in the source space and more. See
latest examples :
https://github.com/mne-tools/mne-python/tree/master/examples/time_frequency
hope this helps
Alex
On Tue, Dec 11, 2012 at 8:31 PM, Vincent <cloud.ctl at gmail.com> wrote:
> Hello,
>
> We are using the example script plot_find_eog_artifacts.py to find the
> blinks in MEG data and we have been trying to use mne.write_events to save
> the blink markers into the original fif. Part of the reason is that these
> are actually resting data so we wanted to just identify the blinks. If we
> want to use 4 sec epochs to estimate the broadband power spectrum in
> auditory cortex, what would you recommend we do stepwise? If we epoch the
> data first would this fit more naturally with the way blinks are currently
> identified and rejected?
>
> ::vincent
>
>
> _______________________________________________
> Mne_analysis mailing list
> Mne_analysis at nmr.mgh.harvard.edu
> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/mne_analysis
>
>
> The information in this e-mail is intended only for the person to whom it is
> addressed. If you believe this e-mail was sent to you in error and the
> e-mail
> contains patient information, please contact the Partners Compliance
> HelpLine at
> http://www.partners.org/complianceline . If the e-mail was sent to you in
> error
> but does not contain patient information, please contact the sender and
> properly
> dispose of the e-mail.
>
More information about the Mne_analysis
mailing list