-
Notifications
You must be signed in to change notification settings - Fork 266
RawBinarySignalRawIO: Fix hard-coded dtype during memmap generation #1765
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
Conversation
zm711
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice catch. Looks good to me. Doc error is unrelated. I'm running tests now, but we should be able to merge after that is done!
|
Also once we get this merged would you like to be on our author list? If so could I get the name you want to display and any institutional affiliation that should go with your name. |
h-mayorquin
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
|
Maybe we should add to the todo to add a test that catches this and test other aspects of reading non-int16 binary data with this (say unsigned types) to see if we are not making any assumptions. |
|
I think there is a test like that in spikeinterface where we have caught issues like this before, but since spikeinterface manages its own binary file reading we do a have blind spot for these rawios. |
|
THanks. |
|
@yagui we are about to do a new release. Just let us know if you want to be included in the author list for this release. (We can also add you later if you want :) ) |
|
Thanks, this was just one line. If I ever do a bigger contribution I'll be honored to be in the list. Thank you for this awesome library. |
fix #1764