From: <hvanesce@comcast.net>
To: <rsgb_lf_group@blacksheep.org>
References: <5860C842.90809@abelian.org>
In-Reply-To: <5860C842.90809@abelian.org>
Date: Mon, 26 Dec 2016 04:18:28 -0500
Message-ID: <069c01d25f59$057d1fe0$10775fa0$@comcast.net>
MIME-Version: 1.0
Thread-Index: AQJBcxK6tgFxE0cJya4aYIAFhPpCvKA7xnPg
Content-Language: en-us
Subject: LF: RE: Article on forward error correction
Content-Type: text/plain;
	charset="utf-8"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Content-Transfer-Encoding: 8bit
Status: O

Paul,

Highly instructive, clear, reader-friendly, makes essential principles understandable.

Also a pleasure to read.

Best by far in capturing the essence, I learned a lot.

Thank you.

Jim AA5BW  

-----Original Message-----
From: owner-rsgb_lf_group@blacksheep.org [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of Paul Nicholson
Sent: Monday, December 26, 2016 2:36 AM
To: rsgb_lf_group@blacksheep.org
Subject: LF: Article on forward error correction


I wrote a non-mathematical introductory article about how forward error correction works.

There's a lot of material on the web about FEC but most of it is very technical and tends to concentrate on one or another particular coding scheme.  I couldn't find anything that demonstrates and really explains in simple terms the essential principle of it.

So I thought I'd try to write something, perhaps to see if I can understand it myself.

The article should appeal to anyone who's wondered how 'coding'
a message, which increases its bandwidth and reduces its S/N, can actually lead to greatly improved communications.

  http://abelian.org/fec/pn161218/

or in pdf format

  http://abelian.org/fec/pn161218.pdf

Whether I've succeeded or not, the reader will have to judge.

--
Paul Nicholson
--