arnodelorme / mffmatlabio

MFF Matlab file importer and exporter
GNU General Public License v3.0
11 stars 15 forks source link

Import Signal issue - Cannot open the signal resource #45

Closed IsaacEGI closed 2 months ago

IsaacEGI commented 1 year ago

Dear Arnaud,

I have a customer reporting an issue importing and MFF file to EEGLAB.

The first thing I saw is that the MFF contents still had the acquiring.xml file (the recording was not stopped properly for some reason). Once I deleted it, it was not being imported to EEGLAB as it was missing the epochs file, and also the event file was reporting the issue: "XML documents structure must start and end...". After checking the XML, the file was missing a closing structure: /eventTrack.

Once I added this structure and created an epoch file using the FileValidator Application of EGI, the mffmatlabio import was reporting a new issue: _"Error using mffimportsignal Error: Can not open the signal resource.\n".

What can be causing this issue on the import? Here is a link to the files: https://electricalgeodesics.sharefile.com/d-seea0430f9e184c99842381eafe25dab1

The description of how the recording was done: "Session takes up to approximately 22 minutes. During the session, the participants are responding with one button on Chronos device. The triggers are the beginning of a trial, stimulus appearance, response if one was made, and TRSP. Three built-in stops exist: at the beginning, at the end of Block A, at the end of Block B, and the recording stops at the end of Block C. It is possible, if necessary, to stop recording using the "P" key, and resuming using any key. I do not know if it happened at the questioned mff file, however, I can say it is unlikely."

Please, if you need more information let me know.

Thank you and best wishes,

Isaac Valls Giménez

arnodelorme commented 1 year ago

Yes, I will look into it.

On Jun 26, 2023, at 2:30 PM, IsaacEGI @.***> wrote:

Dear Arno,

I am one of the support engineers for MagstimEGI and I was helping a customer with an issue importing and MFF file to EEGLAB.

He sent me the file and the first thing I saw is that the MFF contents still had the acquiring.xml file (the recording was not stopped properly for some reason). Once I deleted it, it was not being imported to EEGLAB as it was missing the epochs file, and also the event file was reporting the issue: "XML documents structure must start and end...". After checking the XML, the file was missing a closing structure: .

Once I added this structure and created an epoch file using the FileValidator Application of EGI, the mffmatlabio import was reporting a new issue: "Error using mff_importsignal Error: Can not open the signal resource.\n".

What can be causing this issue on the import? I am attaching the original MFF and the one reporting the last issue on this link: https://electricalgeodesics.sharefile.com/d-s2217ce504b154a039a81a3e710c1c34c

The customer also sent me a description of how the recording was done: "Session takes up to approximately 22 minutes. During the session, the participants are responding with one button on Chronos device. The triggers are the beginning of a trial, stimulus appearance, response if one was made, and TRSP. Three built-in stops exist: at the beginning, at the end of Block A, at the end of Block B, and the recording stops at the end of Block C. It is possible, if necessary, to stop recording using the "P" key, and resuming using any key. I do not know if it happened at the questioned mff file, however, I can say it is unlikely."

Please, if you need more information let me know.

Thank you and best wishes,

Isaac Valls Giménez

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.

arnodelorme commented 2 months ago

Apologies it took so long. The event files were corrupted missing some text. It is likely that the hard drive was full and that when the file was copied an saved, only part of the file was saved. It is easy to see that the file was corrupted. Both files are corrupted in the same way. After removing the corrupted file, I could import them and visualize them.

Screenshot 2024-05-09 at 4 24 11 PM

Screenshot 2024-05-09 at 4 23 16 PM