Error Importing EEG data using Brain Vision Amp

Hello everyone,
I am new to Brainstorm and would appreciate feedback.

I am currently trying to import an EEG dataset which is cleaned from artifacts. In the file there's a .dat file, a .vmrk file and a .vmrk file. I converted the .dat file into an .eeg file by opening it in notepad and saving it as an .eeg file. I am trying to open it with Import MEG/EEG>(selected dataset), but I keep running on the following error:
image
If this error has occured to you before, how did you solve it?

Thank you in advance.

Regards,
Kristi

I suggest you not to convert in that way, try to reload the original data in the BrainVision format

Was this file generated by a BrainProducts/BrainVision software?
There might be something missing in the BrainAmp file reader in Brainstorm.

Could you please prepare a small example file (one second would be enough) and share it with us?
Zip all the files together (all the original files, .vhdr and .vmrk included), upload it somewhere (dropbox, google drive, wetransfer) and post the download link here.

Hi everyone,

I'm helping Kristi with his project and I will explain the problem with the dataset a bit more. The dataset we are using comes from : https://osf.io/94c5t/ .

Per subject this contains a .dat,.vhdr and a .vmrk file. The traditional workaround we used before was to convert it using e.g. cartool to a .vhdr .vmrk and a .eeg file, which makes the file importable by brainstorm.

A minimal dataset can be found in the following WeTransfer link: https://we.tl/t-3eYihiAK9Q

Kind regards,
Steven

Maybe you can try to import the file first in EEGlab , save in eeglab format and then load it on BS,

1 Like

@SBeumer @kristi97 Thank you for the example file. I added the support for vectorized binary files: https://github.com/brainstorm-tools/brainstorm3/commit/2b886a9635dfae851105e0e64e04e2f0fe21ea38
Please update Brainstorm and try again.

@tourette95 In general, you should avoid trying to go through multiple steps of conversion. At each conversion, you might lose some interesting information, or force some data type conversion which degrades the quality of the data.

@Francois Great, thanks for the quick support :smiley: !

I see!
thank you for the advice @Francois!
:D!