Papers › Incremental Redundancy, Fountain Codes and Advanced Topics
Incremental Redundancy, Fountain Codes and Advanced Topics
Suayb S. Arslan
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
This document is written in order to establish a common base ground on which the majority of the relevant research about linear fountain codes can be analyzed and compared. As far as I am concerned, there is no unified approach that outlines and compares most of the published linear fountain codes in a single and self-contained framework. This written document has not only resulted in the review of theoretical fundamentals of efficient coding techniques for incremental redundancy and linear fountain coding, but also helped me have a comprehensive reference document and hopefully for many other graduate students who would like to have some background to pursue a research career regarding fountain codes and their various applications. Some background in information, coding, graph and probability theory is expected. Although various aspects of this topic and many other relevant research are deliberately left out, I still hope that this document shall serve researchers' need well. I have also included several exercises to warm up. The presentation style is usually informal and the presented material is not necessarily rigorous. There are many spots in the text that are product of my coauthors and myself, although some of which have not been published yet.
Code
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections