Working with .set file about mvpalab HOT 7 CLOSED

Hi Ravi, thanks for your message.

Could you send your .set file to me in order to reproduce the error you are getting?

David

from mvpalab.

Hi Ravi, thanks for sharing your data. I have check your files. The problem doesn't seem to be related to MVPAlab Toolbox. When I tried to open your .set files with EEGLAB I got the same error. According to EEGLAB documentation, EEG datasets are usually saved in two files, the metadata file (.set) and the data file (.fdt). If you renamed the .set file, please be sure to rename the .fdt as well. Additionally, .set files and .fdt files should be in the same folder in order to be imported by the EEGLAB function.

Please check the following link and if the problem remains contact me again.
https://eeglab.org/tutorials/ConceptsGuide/Data_Structures.html#saved-set-files

David

Edit: This is the error I am getting both in MVPAlab and EEGLAB when I try to open your .set files:

Error using eeg_getdatact (line 209)
file 006CS_minus_Epoched.fdt not found. If you have renamed/moved
the .set file, you must also rename/move the associated data file.

This error is thrown by the EEGLAB function pop_loadset, so the problem should be related to the way you are saving (or renaming) your data. Please let me know if you solved the issue and you are able to import your data into MVPAlab.

from mvpalab.

from mvpalab.

Hi Ravi, it is easier to work with .mat files since they are directly imported to MVPAlab. Contrary, to import .set files the EEGlab function pop_loadset is required. The error you are getting is thrown by this function, so you should not be able to load your .set files into eeglab. Try to export your preprocessed data in EEGlab to .mat files and your problem will be solved.

David

from mvpalab.

from mvpalab.

That's weird. Would you mind sharing some .set and .fdt files with me? I am going to try to reproduce the exact same error. Thanks in advance, David.

from mvpalab.

Hi Ravi, I deleted your previous message to keep your data private. These messages are publicly available on GitHub. Please contact me directly at dlopez[at]ugr[dot]com for sharing the data. Thanks, David.

from mvpalab.