Open Genuster opened 1 year ago
Hello! š Thanks for opening your first issue here! ā¤ļø We will try to get back to you soon. š“š½āāļø
First issue (see first screenshot in actual results) was solved by commenting out the following code in the /mne/io/egi/egimff:
I think commenting this out likely causes all the other problems -- this error means we haven't parsed/understood the file correctly, so any reading operation after that is likely to fail.
Hopefully someone can try the file soon!
I think commenting this out likely causes all the other problems
Yeah, I completely understand that this is a poor way to solve the problem. It's just too complicated to debug it with my current level of understanding MNE code and mff structure.
Hopefully someone can try the file soon!
Thank you! I'm looking forward to it. If I can be of any help, please tell me.
I cannot test the file because of the file sharing system you're using. It says "firefox doesn't provide a big enough buffer, use chrome" but then in chrome it says "not enough disk space, you have to use our app or chrome plugin". I'm not going to install an unknown app or browser plugin so please find another way to share the file, or else crop the data so that it's small enough to not have these problems.
@drammock I'm sorry about that, it sounds really nasty. I've uploaded it to the google drive, here is the link. I hope it will work well.
For the first issue, it comes from a mismatch of 2 samples between those 2 variables https://github.com/mne-tools/mne-python/blob/e5086fcb20e891ef1c4ddc2ce2ae16047b496c5f/mne/io/egi/egimff.py#L85-L86 I do recall having some mismatch issues in those 2 lines a while ago, probably while working on https://github.com/mne-tools/mne-bids/pull/1006 but I don't remember what the reason was.
I'll try to have a deeper look in early January, as we are still using heavily the EGI system both for awake and sleep studies in Geneva. FYI, it seems like mffpy
is able to read the file. I was able to access the data array and the main information easily; although I could not load entirely this large array in RAM.
When the reader for MFF files was added, it was not based on mffpy
(#4017). This additional dependency was added to support Evoked (#8354). What do you think of a rework of this reader based on mffpy
which seems to support better the many different version of the MFF format?
I think that would be great!
+1
Description of the problem
I've seen the issue #11188, it seems similar to the error I get, but I haven't quite understand where does the problem come from and if there are any existing solutions. I tried to find some workaround for the problem, that's where I've got so far:
I'm not sure if it's an MNE bug, so I apologise in advance if it's not. Do you have any insight about roots of the issues? Could you please advise how to proceed?
Steps to reproduce
Link to data
Link to the mff (google drive)
Expected results
Load and resample the mff file successfully.
Actual results
Additional information