Locally testable code
A locally testable code is a type of for which it can be determined if a is a in that code by looking at a small (frequently constant) number of bits of the string. In some situations, it is useful to know if the data is corrupted without decoding all of it so that appropriate action can be taken in response. For example, in communication, if the receiver encounters a corrupted code, it can request the data be re-sent, which could increase the accuracy of said data. Similarly, in data storage, these codes can allow for damaged data to be recovered and rewritten properly.
In contrast, locally decodable codes use a small number of bits of the codeword to recover the original information. The fraction of errors determines how likely it is that the decoder correctly recovers the original bit; however, not all locally decodable codes are locally testable.
Clearly, any valid codeword should be accepted as a codeword, but strings that are not codewords could be only one bit off, which would require many (certainly more than a constant number) probes. To account for this, testing failure is only defined if the string is off by at least a set fraction of its bits. This implies words of the code must be longer than the input strings by adding some redundancy.
Contents
Definition
To measure the distance between two strings, the is used
The distance of a string from a code is computed by
Relative distances are computed as a fraction of the number of bits
A code is called -local -testable if there exists a Turing machine M given to an input that makes at most non-adaptive queries of and satisfies the following:
-
- For any and , . In other words, M accepts given access to any codeword of C.
- For such that , . M must reject strings -far from C at least half the time.
Limits
It remains an open question whether there are any locally testable codes of linear size, but there are several constructions that are considered “nearly linear”:
- Polynomial arbitrarily close to linear; for any , .
- Functions of the form , where is a function tending toward 0. This makes n closer to linear as k increases. For example:
- for some
- for
These have both been achieved, even with constant query complexity and a binary , such as with for any . The next nearly linear goal is linear up to a factor; . Nobody has yet to come up with a linearly testable code that satisfies this constraint.
Examples
Hadamard code
One of the most famous error-correcting codes, the Hadamard code is a locally testable code. A codeword x is encoded in the Hadamard code to be the linear function (mod 2). This requires listing out the result of this function for every possible y, which requires exponentially more bits than its input. To test if a string w is a codeword of the Hadamard code, all we have to do is test if the function it encodes is linear. This means simply checking if for x and y vectors (where denotes ).
It is easy to see that for any valid encoding , this equation is true, as that is the definition of a linear function. Somewhat harder, however, is showing that a string that is -far from C will have an upper bound on its error in terms of . One bound is found by the direct approach of approximating the chances of exactly one of the three probes yielding an incorrect result. Let A, B, and C be the events of , , and being incorrect. Let E be the event of exactly one of these occurring. This comes out to
This works for , but shortly after, . With additional work, it can be shown that the error is bounded by
For any given , this only has a constant chance of false positives, so we can simply check a constant number of times to get the probability below 1/2.
Other locally testable codes include (see locally decodable codes for a decoding algorithm), , and the short code.