loading -ave.fif between mne versions

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

Dear Talitha,

Please post every single line of code you executed leading up to the error you report. Oh, and whether this is data recorded on a VectorView (older) or Triux (newer) system.

Best,

Chris

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

Thanks Alex (sorry for the late reply).

Your solution worked :slight_smile:

Cheers,
Talitha

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

Dear Alex,

I have revisited this today and am finding the same error despite commenting out the section of code you have suggested. My version of MNE is 0.13.1. Please find attached the screenshot of the original error (before I started commenting out info._check_consistency().

Cheers,

Talitha
[cid:5577FC49-E253-4EC9-AAB6-F1BC3B60F9A7 at swin.edu.au]

hi Talitha,

can you try commenting out the lines 238 to 240 in the meas_info.py file.

Alex

Dear Alex,

I have revisited this today and am finding the same error despite
commenting out the section of code you have suggested. My version of MNE is
0.13.1. Please find attached the screenshot of the original error (before I
started commenting out info._check_consistency().

Cheers,

Talitha

Thanks Alex (sorry for the late reply).

Your solution worked :slight_smile:

Cheers,
Talitha

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

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
Mne_analysis Info Page

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
MyComplianceReport.com: Compliance and Ethics Reporting . 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.

_______________________________________________
Mne_analysis mailing list
Mne_analysis at nmr.mgh.harvard.edu
Mne_analysis Info Page

_______________________________________________
Mne_analysis mailing list
Mne_analysis at nmr.mgh.harvard.edu
Mne_analysis Info Page

_______________________________________________
Mne_analysis mailing list
Mne_analysis at nmr.mgh.harvard.edu
Mne_analysis Info Page

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
MyComplianceReport.com: Compliance and Ethics Reporting . 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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.nmr.mgh.harvard.edu/pipermail/mne_analysis/attachments/20170217/6bd12154/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bad_channel_error.png
Type: image/png
Size: 158373 bytes
Desc: not available
Url : http://mail.nmr.mgh.harvard.edu/pipermail/mne_analysis/attachments/20170217/6bd12154/attachment-0001.png