-
Notifications
You must be signed in to change notification settings - Fork 86
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
Not compatible with matlab's rsenc/rsdec; only deal with n=255. #2
Comments
as i explained in the readme, i don't understand enough math to patch this myself. if you can send a working patch, i'll happily incorporate it in, but i can't do it (nor do i have the time) on my own. in order to submit a patch, click "fork" on github repo, which will create a separate repo on which you can work. when you're done, create a pull request and send me the patch. it's very easy to do on github. see https://help.github.com/articles/using-pull-requests |
I have also noticed that reedsolo library is not working correctly. Codewords of size 9 (5 data+4 parity) and 62 (30 data+32 parity) seem to work ok. But for size 248 (216 data+32 parity), it fails. According to the readme this should still work, as it's under 255, no? For me, I can just use rscode C library. But I thought I'd document the issue here. edit: |
Where exactly is it failing for you shuffle2? In my experience I could only encode 7-bit strings but could encode 8-bit (i.e. up to 255) byte arrays. Eg:
This is because the library attempts to convert any string into a 7-bit bytearray, but ignores it if it is already a bytearray. Hope that helps with your issue. |
This is the same input codeword as previous pastie:
It should decode correctly with errors in one byte and no erasures. |
At this point, I'm seeing strange behavior with rscode as well :( Nothing makes sense! :( |
Shit, another programmer lost to reed solomon madness... |
mmmph, my comments here can be ignored. Turns out I was generating some data incorrectly, and the codewords with higher parity:data ratio could of course correct my bad data, while the larger codewords had too much bad data (and I wasn't using erasures). |
If you still experience an issue, please try the new release, it has been thoroughly unit tested, or else if it's ok now, please close this thread :) |
Hey buddy, as is said in the mail, I tried to improve this package, but encountered an error in the decoder. The improvements to the encoder may help, so I send it to you, hoping that you (or some one else) can (easily) fix it.
p.s. Source code is not permitted to be attached here.
The text was updated successfully, but these errors were encountered: