data.table error/warning when using read_vhdr

[stonekate]

For recordings exported from the second lab laptop, I get the following errors/warnings when using read_vhdr:

It's specific to that laptop! Exported data from the main laptop can be imported fine. In case you forgot, the process is: record in .cnt format, export to .eeg format (Brainvision), then import into R with eeguana. I will put 1 example in Dropbox now.

[bnicenboim]

I guess, you can work around this, so it's not urgent. But it seems the file is just not complete. I'll eventually get to this. I'm trying to release a new version of eeguana soon.

[stonekate]

No not urgent, just a minor blip. Cool!

[bnicenboim]

Hi, I just got to this. I don't think the error is eeguana's side. The binary file has the wrong size. Maybe it didn't finish creating the ".eeg" file? Have you tried to export them again?

[stonekate]

No worries... yeah I tried re-exporting. Weird! I'll look into it.

On Thu, 20 Jan 2022 at 15:03, Bruno Nicenboim @.***> wrote:

Hi, I just got to this. I don't think the error is eeguana's side. The binary file has the wrong size. Maybe it didn't finish creating the ".eeg" file? Have you tried to export them again?

— Reply to this email directly, view it on GitHub https://github.com/bnicenboim/eeguana/issues/169#issuecomment-1017533621, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADBFKQMBPYYA275FK4X5PWTUXAIZ7ANCNFSM5F4SR7RQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

[bnicenboim]

could you open those files with Brainvision?

[stonekate]

I can't remember, I'll try it next week

On Thu, 20 Jan 2022 at 15:09, Bruno Nicenboim @.***> wrote:

could you open those files with Brainvision?

— Reply to this email directly, view it on GitHub https://github.com/bnicenboim/eeguana/issues/169#issuecomment-1017538975, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADBFKQK4CXLNKHFASGQ43TDUXAJQBANCNFSM5F4SR7RQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

You are receiving this because you authored the thread.Message ID: @.***>

[stonekate]

(sorry for delayed response) I now checked, they all opened fine in BrainVision Analyzer. So I just exported them as binary .dat files from there and can now import them into eeguana without any problems. So from my side it's resolved :)

[bnicenboim]

wait, so the same files that you can't open with eeguana can be opened with Brainvision? That's strange. Can you send me the two versions of the file to see how BV deals with the incomplete rows?

[stonekate]

oh man, sorry, I wrote down and exported the wrong bloody file numbers.... ignore everything I just said, I'll try again next week. I knew it seemed too easy.

[stonekate]

Ok now I checked the right files: BrainVision could load and export them in a way that eeguana could then load, but either I don't think BV dealt with the issue properly or there is something very wrong with the data (probably the latter). The image attached is the data loaded and filtered in eeguana, but this is also what it looked like in BV. It also looked weird in asalab once I reopened it, but I assume it didn't look like that while being recorded. I've put some files in Dropbox (40 regular and BV export) in case you want to look at why BV could load it but eeguana couldn't, but I think the core problem is something has gone wrong with asalab. Which is not your problem :)

[bnicenboim]

Ok, i conclude that eeguana is doing the right thing then, throwing an error. I don't want to open bad files. Thanks for the detective work!