interpolate missing channels

[dasdiptyajit]

Reference issue

Example: Fixes #11652

What does this implement/fix?

It answers one straightforward question: “how do I interpolate a sensor that was completely missing from a recording?”

CC @drammock, I did some changes.

[dasdiptyajit]

@larsoner thanks for having a look. I will try to work on this soon.

[dasdiptyajit]

@drammock @larsoner I have created a .json (dict file) that contains channel names and locations. Is it possible to facilitate one extra file that contains channel locations in MNE? If we can do that then the example can run using a single dataset. I have seen a similar file mne/io/artemis123/resources/Artemis123_mneLoc.csv but not sure about its usage. My code is working now with the additional file but I don't know how to read/add it as a standard path. I would appreciate some help.
Plus, if you get some time, have a look at the code. I would love to get some feedback,

thanks!

[larsoner]

I have created a .json (dict file) that contains channel names and locations. Is it possible to facilitate one extra file that contains channel locations in MNE?

Why do you need this file? To me I would just directly create the ch_pos dict to pass to make_dig_montage. Feel free to use json.loads in the example if you want to copy-paste your JSON as a string.

[dasdiptyajit]

I have created a .json (dict file) that contains channel names and locations. Is it possible to facilitate one extra file that contains channel locations in MNE?

Why do you need this file? To me I would just directly create the ch_pos dict to pass to make_dig_montage. Feel free to use json.loads in the example if you want to copy-paste your JSON as a string.

I thought its a clean way to interpolate any missing channel for MEG recordings if there is a separate file to load the channel position. I think make_dig_montage doesn't work for meg data but rather eeg right? Basically, my idea was: for 'eeg' we have standard montage layouts, so it wouldn't be that bad if we have something similar for meg. But, perhaps it's not that important.

Do you want me to copy the ch_pos from a standard dateset in the example? Then I will make the changes.

[larsoner]

Do you want me to copy the ch_pos from a standard dateset in the example? Then I will make the changes.

No my suggestion for MEG (as before) would be to get the channel positions from some other instance. Why do we need a new file?

[dasdiptyajit]

Do you want me to copy the ch_pos from a standard dateset in the example? Then I will make the changes.

No my suggestion for MEG (as before) would be to get the channel positions from some other instance. Why do we need a new file?

Okey. I was thinking earlier.. of having a single file that contains different MEG systems ch_position for user. But it was rather a suggestion. No problem. I will follow your recommendation.

[larsoner]

I'd prefer to avoid adding a new file with positions

[wmvanvliet]

hardcoded path.

[dasdiptyajit]

@wmvanvliet Thanks for having a look. I still need to modify the code based on my last discussion with Eric.
Unfortunately, I am really busy these days. I will get back it soon.