User:Script3r/sandbox
Motivation
There are many codes that have been designed to correct random errors. Sometimes, however, channels may introduce errors which are localized in a short interval. Such errors occur in a burst (called as burst errors because they are occur in many consecutive bits). Examples of burst errors can be found extensively in storage mediums. These errors may be due to physical damage such as scratch on a disc or a stroke of lightning in case of wireless channel. They are not independent; they tend to be spatially concentrated. If one bit has an error, it is likely that the adjacent bits could also be corrupted. The methods used to correct random errors are inefficient to correct burst errors. This motivates burst error correcting codes.
Definitions
A burst of length [8]
Say a codeword is transmitted, and it is received as . Then, the error vector is called a burst of length if the number of nonzero components of is confined to consecutive components. For example, is a burst of length .
Although this definition is sufficient to describe what a burst error is, the majority of the tools developed for burst error correction rely on cyclic codes. This motivates our next definition.
A cyclic burst of length [8]
An error vector is called a cyclic burst error of length if its nonzero components are confined to cyclically consecutive components. For example, the previously considered error vector , is a cyclic burst of length , since we consider the error starting at position and ending at position . Notice the indices are -based, that is, the first element is at position .
For the remainder of this article, we will use the term burst to refer to a cyclic burst, unless noted otherwise.
Burst description [8]
It is often useful to have a compact definition of a burst error, that encompasses not only its length, but also the pattern, and location of such error. We define a a burst description to be a tuple where is the pattern of the error (that is the string of symbols beginning with the first nonzero entry in the error pattern, and ending with the last nonzero symbol), and is the location, on the codeword, where the burst can be found.
For example, the burst description of the error pattern is . Notice that such description is not unique, because is describing the same burst error. In general, if the number of nonzero components in is , then will have different burst descriptions (each starting at a different nonzero entry of ).
We now present a theorem that remedies some of the issues that arise by the ambiguity of burst descriptions.
Theorem: Uniqueness of burst descriptions
If is an error vector of length with two burst descriptions and . If (where is the number of symbols in the error pattern ), then the two descriptions are identical (that is, their components are equivalent) [2]
Proof Let be the weight (or the number of nonzero entries) of . Then has exactly error descriptions. For or , there is nothing prove. So, we consider the cases where . Assume that the descriptions are not identical. We notice that each nonzero entry of will appear in the pattern, and so, the components of not included in the pattern will form a cyclic run of 0's, beginning after the last nonzero entry, and continuing just before the first nonzero entry of the pattern. We call the set of indices corresponding to this run as the zero run. Let's consider the zero runs for the error pattern .
We immediately observe that each burst description has a zero run associated with it. But most importantly, we notice that each zero run is disjoint. Since we have zero runs, and each is disjoint, if we count the number of distinct elements in all the zero runs, we get we have a total of . With this observation in mind, we have a total of zeros in . But, since , this number is , which contradicts that . Thus, the burst error descriptions are identical. A corollary of the above theorem is that we cannot have two distinct burst descriptions for bursts of length Failed to parse (unknown function "\e"): {\displaystyle \textstyle \e (n+1)/2} .