Content deleted Content added
layout, alpha Tags: Mobile edit Mobile web edit Advanced mobile edit |
Cite and ref CE. |
||
Line 1:
In [[coding theory]], '''Tornado codes''' are a class of [[erasure code]]s that support [[error correction]]. Tornado codes require a constant C more redundant blocks than the more data-efficient [[Reed–Solomon erasure code]]s, but are much faster to generate and can fix erasures faster. Software-based implementations of tornado codes are about 100 times faster on small lengths and about 10,000 times faster on larger lengths than Reed–Solomon erasure codes.
Tornado codes use a layered approach. All layers except the last use an [[LDPC]] error correction code, which is fast but has a chance of failure. The final layer uses a Reed–Solomon correction code, which is slower but is optimal in terms of failure recovery. Tornado codes dictates how many levels, how many recovery blocks in each level, and the distribution used to generate blocks for the non-final layers.
Line 21:
== Patent issues ==
Tornado codes were formerly patented inside the United States of America.
== Citations ==
[[Michael Luby]] created the Tornado codes.
== See also ==
Line 34:
== References ==
* {{cite conference |vauthors=Byers JW, Luby M, Mitzenmacher M, Rege A |date=October 1998 |title=A digital fountain approach to reliable distribution of bulk data |book-title=SIGCOMM '98: Proceedings |conference=ACM SIGCOMM '98 conference on Applications, technologies, architectures, and protocols for computer communication |pages=56–67 |doi=10.1145/285237.285258 |doi-access=free}}
* {{cite journal | ref={{harvid|Mitzenmacher|2004}} | author=[[Michael Mitzenmacher|M. Mitzenmacher]] | title=Digital Fountains: A Survey and Look Forward | journal=Proc. 2004 IEEE Information Theory Workshop (ITW) | year=2004}}▼
* {{cite journal |
* {{cite journal |
▲* {{cite journal |
== External links ==
|