[Mne_analysis] loading -ave.fif between mne versions
Alexandre Gramfort
alexandre.gramfort at telecom-paristech.fr
Wed Aug 10 09:07:39 EDT 2016
hi Talitha,
I've seen this in the past. Previously we were keeping the bad
channels in the info even if these channels were removed eg during
epoching with exclude='bads'.
the way out is (I think) to comment out the call to :
info._check_consistency()
in function read_meas_info in meas_info.py
when you've saved again all your files you can put this line back.
Let me know if this works.
HTH
Alex
On Wed, Aug 10, 2016 at 3:28 AM, Talitha Ford <tcford at swin.edu.au> wrote:
> Hi everyone,
>
> Sorry if I have missed something.
> I’m having some issues with compatibility between versions of mne. I have done all the preprocessing of my MEG data in mne 0.9.0, but now want to use the dipole fitting functions in mne 0.12.0 and 0.13.dev0. When I read in my -ave.fif I get RuntimeError: bad channel(s) [u'MEG2622', u'MEG0513', u'MEG1522', u'MEG0121', u'MEG0343', u'MEG0122', u'MEG1212', u'MEG2612', u'MEG1213', u'MEG1543', u'MEG0342', u'MEG0923', u'MEG1432', u'MEG0143', u'MEG2623', u'MEG0523', u'MEG0313', u'MEG0123'] marked do not exist in info.
>
> Is there a way to rectify this without having to go back and preprocess all the data again in version 0.13.0?
>
> Cheers,
> Talitha
>
> _______________________________________________
> 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