-
Notifications
You must be signed in to change notification settings - Fork 11
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
BV data in int_32 format? #21
Comments
Would you mind sharing a file. We will add support if it not too difficult. |
Thanks! Here is a file. Epoched data was apparently exported using Analyzer's GenericDataExport. https://www.dropbox.com/s/j7mus468a5v4hec/example_BVAexportedData_int32.zip?dl=1 |
Would it be OK to add it to our test cases? |
Since it's collaborator data (not my own), I am unfamiliar with exact restrictions, would be better if not added to unit testing cases (sorry) |
OK, thank you. Ramon said he would look into it in the next few weeks.
|
I had the same issue. I think the problem would be solved by adding here Line 103 in a61a74a
the line |
Exported epoched data from BV-Analyzer and would like to read them in with pop_loadbv.
But exported data is in int 32-bit format, which is not supported by pop_loadbv.
Any solution for this? I did not see an option to change export bit range in BVA or to export as float-32.
Any input appreciated.
The text was updated successfully, but these errors were encountered: