Talk:Reed–Solomon error correction
This is the talk page for discussing improvements to the Reed–Solomon error correction article. This is not a forum for general discussion of the article's subject. |
Article policies
|
Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
Archives: 1, 2, 3Auto-archiving period: 12 months |
This level-5 vital article is rated C-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||
|
Shortened DVD
[edit]I am a new to Reed-solomon. Until recent,I am required to implement Reed-Solomon code on FPGAs. This will be used in our DVD project. However, I have some questions puzzling me greatly. In DVD error correction coding ,should RS(208,192,17) and RS(182,172,11) be shortened or puntured Reed-Solomon codes. I have no way to differentiate the two. Meanwhile, I have great eagerness to comminicate and discuss with others about ECC especially Reed-Solomon codes. My email is skycanny@hotmail.com
Regards!
Cross-interleaved coding
[edit]Is CIRC also used on DVDs.
Duality of the two views - inverse transform equation
[edit]Regarding the inverse transform equation for p(x), the equation is correct for non-binary fields , but for binary fields, the equation should be ,
The issue depends if the field is a a non-binary field, such a a field modulo (929) as used in the examples versus a binary based field GF(2^n) where addition is effectively xor. As a simple way to explain this, for a non-binary field: but for a binary field where n is an odd number .
"Error correction" in title
[edit]Is there a good reason to include "error correction" in the title here? The current Applications section focuses on error correction, and those are probably the most notable applications, but there are some applications outside of correction, like key recovery, constructing MDS matrices, and some zero-knowledge argument protocols.
The article's scope already seems broader than error correction (e.g. it can correct up to t erasures
); should we move it to "Reed-Solomon code" to reflect this broader scope? That would seem more WP:CONCISE and WP:CONSISTENT with Reed–Muller code, Algebraic geometry code, Expander code, etc. (which are also error-correcting codes). — xDanielx T/C\R 05:03, 29 July 2024 (UTC)
Duality of the two views
[edit]This section was removed, but I have found something similar. I'm leaving Ylloh's original comment:
- I'm not sure what you are proposing here. The two views result in the same set of codewords, which is what is meant by "equivalence". It does not mean that the encoding functions are identical. Regarding the historical details, if you have more correct information on them, feel free to clarify. ylloh (talk) 19:59, 30 March 2016 (UTC)
Original view RS codewords have maximum length , while BCH view codewords have maximum length , and in this case, the codewords can not be the same. If original view uses sequential powers of the primitive element: as evaluation points, then the resulting codeword of a set of values can be viewed as a set of coefficients to a polynomial , and the roots of will be . [Dual view of Reed Solomon codes]. If using systematic encoding for both original view and BCH view, original view encoding produces the same codewords as BCH view using generator polynomial . If using non-systematic encoding the roots will be the same, but not the codewords. However while original view implementations are normally least significant term first, BCH view implementations are normally most significant term first. In this case, to produce a codeword identical to original view systematic encoding, the roots are inverted, and the generator polynomial is . Rcgldr (talk) 16:45, 7 February 2025 (UTC)
History
[edit]Systematic encoding dates back to 1949 with Golay codes and 1950 with Hamming codes. Reed Solomon's 1960 paper describes a non-systematic encoding, and at that time, decoding required interpolation of all combinations of codeword symbols taken at a time and assuming the most popular result was the correct one. At about the same time, a practical decoder was invented for BCH codes, the Peterson Gorenstein Zierler decoder. Original view encoding was abandoned, and a switch to BCH view compatible encoding occurred. The textbook Error Correction Codes by Peterson and Weldon (1961), the first book about error correction codes, mentions RS codes as a sub-class of BCH codes, with systematic encoding, and there is no mention of the original view encoding. That textbook also covers Golay and Hamming codes. Original view systematic encoding is currently used for list decoders and some erasure codes. Note that with the constraints mentioned in Talk:Reed–Solomon_error_correction#Duality_of_the_two_views, original view encoding can be identical to BCH view encoding. Rcgldr (talk) 17:06, 7 February 2025 (UTC)
- C-Class level-5 vital articles
- Wikipedia level-5 vital articles in Mathematics
- C-Class vital articles in Mathematics
- C-Class Telecommunications articles
- Mid-importance Telecommunications articles
- C-Class Computer science articles
- Mid-importance Computer science articles
- WikiProject Computer science articles