-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error with channel location (BIDS dataset #71
Comments
Hi, it seems that the loading of chanlocs file failed. if you already have tsv files with electrode locations in each subject folder, you don’t need to provide a new channel location file or file type. Automagic will find these tsv files on its own. Simply remove both entries. Hope it helps. Otherwise you could send me data of 1 subject and will figure it out for you. |
I tried what you suggested but I keep getting the same error, how can I send you the data of 1 subject? Thank you for your help |
You can use google drive, Dropbox or wetransfer. I will have a look at the data tomorrow. |
thanks! Could you also provide the '*electrodes.tsv' file or a channel location file that contains locations for 'VPVA', 'VNVB', etc. channels? Brainclinics Foundation |
I do not have that file, but I copied can send you the channel location provided in the paper where the dataset was presented: https://drive.google.com/file/d/1QRsFDnVTCZq3nxiZ68IgnkUm6WU5ESQF/view?usp=drive_link |
Thanks! this solved my problem! |
Hello, I have been trying to pre process my data that are stored in BIDS format. These are the settings I am using:
This is the error I get:
In each subject folder I have a .tsv file (that is supposed to have the channel information), a .eeg file with raw eeg data, a .json file and .vhdr and .vmrk files. I have also tried to not provide a channel location document or create one myself and save it as .sfp but I keep getting the same error. I also tried to specify one of the subject's .tsv files as channel location file but it didn't work.
The text was updated successfully, but these errors were encountered: