Computer forward solution using epoch.info rather than raw.info

External Email - Use Caution

Hi everyone,

This is a naive question but I?d appreciate some clarity from someone who understands in more depth.

I?m currently running source recon MEG data using individual MRIs. I found that when running make_inverse_operator(raw.info, fwd, noise_cov) I was getting an error saying ?no channels match the selection?. I checked in raw.info and no channels were marked as bad, so I tried again using epoch.info (also no bad channels) instead of raw.info and got the same error.

I have diagnosed this further up the pipeline ? I was making the forward solution with:
make_forward_solution(raw.info, trans, src, bem, meg=True, eeg=False)
Thinking that this would pick only the MEG channels. However, my noise covariance is calculated from epochs, not the raw data, and I think that creating a forward solution using raw.info and the covariance using epoch.info resulted in a clash of channels, even though both of them have 270 MEG channels.

To get around this, I am now making the forward solution and inverse operator using epoch.info:
make_forward_solution(epoch.info, trans, src, bem, meg=True, eeg=False)
make_inverse_operator(epoch.info, fwd, noise_cov)

However, the tutorials always use raw.info. So my question is: am I introducing errors into the analysis calculating the forward solution and the inverse operator using epoch.info rather than raw.info? I think that only the channel names/placement are used from .info but I am not sure. In case relevant: I think that some of my channels in the epochs object were repaired/interpolated using autoReject.

Any clarity anyone can give would be appreciated so I don?t introduce errors.

Best,

Amie

P.S. thanks for updating the installation instructions ? I followed them exactly and now have everything working on my virtual machine ?

This message contained a link to a web site whose IP address has recently been associated with malicious activity. Due to that activity, the site is not accessible from within the Partners Healthcare network. The link has been modified in the message below. If you feel this is an error, please contact the IS Service Desk and open a ticket with the network security - phs assignment group.

                                  IS Service Desk
BWH 617-732-5927 BWFH 617-983-7454 BWH-RICS 617-525-0848
DFCI 617-632-3399 LCC 857-307-4150 MCL 781-416-8940
MGH 617-726-5085 NHP 617-643-2020 NSMC 978-354-2014
NWH 617-243-6001 PCPO 781-433-3757 PHH 617-726-0790
PHS 857-282-4357 SRN 617-952-5555 CDHC 413-582-5005