-
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
Symbols other than 8 bit #12
Comments
Yes it should work with the latest version here: https://github.com/lrq3000/reedsolomon There is also various unit tests with different fields orders, so this case should be covered without any problem. These changes to support different fields should be merged in this repo with PR #11 (but @tomerfiliba seems to be away currently...). |
BTW just to precise, the support for other Galois fields was supported already by the core code here, but not the high level API because I forgot to automatically manage the refresh of the data structures. This is fixed in the latest version in #11 and several users reported it works fine :-) |
Fixed with the merge of #11 |
I'm using c_exp=2 and getting and error, is this how it supposed to work?
|
Hi,
I would like to use an alphabet of 2^5 possible symbols (base32 encoding) for my message and code. I tried setting c_exp to 5 and get the following error:
I want to get something like a flight code (length 8 digits/characters) with error correction.
Has anyone tried using different symbols? Is it possible using the base library instead of the hight level API?
Thanks
The text was updated successfully, but these errors were encountered: