Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,RCVD_IN_DNSWL_MED, SPF_PASS,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0 X-Spam-DCC: EATSERVER: mailn 1166; Body=2 Fuz1=2 Fuz2=2 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by lipkowski.org (8.14.4/8.14.4/Debian-8+deb8u1) with ESMTP id uBQEMWiw020313 for ; Mon, 26 Dec 2016 15:22:33 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1cLW6U-0002h3-8e for rs_out_1@blacksheep.org; Mon, 26 Dec 2016 14:18:18 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1cLW6T-0002gu-Mf for rsgb_lf_group@blacksheep.org; Mon, 26 Dec 2016 14:18:17 +0000 Received: from mail-yb0-x22e.google.com ([2607:f8b0:4002:c09::22e]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from ) id 1cLW6Q-0004bG-ED for rsgb_lf_group@blacksheep.org; Mon, 26 Dec 2016 14:18:16 +0000 Received: by mail-yb0-x22e.google.com with SMTP id d59so103116516ybi.1 for ; Mon, 26 Dec 2016 06:18:14 -0800 (PST) X-DKIM-Result: Domain=gmail.com Result=Good and Known Domain DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=NfNFr30/Gg9TdganHTwNnY5SbQlbER1mpFf/p6uD204=; b=YDqACdI14pjXaGsJ+pYwJ2/n20SwQohqxOsgGtYp6h2cjpaRe3qJ35KfiP0nzFtGg2 ad3l7Nv4Q3llPdJN+2TfpYcrV46FxEF9y9gLsz1M+xjUxT1NMEfbE98obl0J2ExABw5y yjJPo18lJXydwNjBsOF6QswyDGRXK91BaNI2OgvlCBPGNbXNa1KI0HvcX2/apE/07Kyx 9fnildnX0wsKsqScTjFIbLAEFgdOmJXGOcmwZUdTa0GfEMBp0aHgbAJ2Sa7AwKSQwoGi YNdhZJSHi3V16Rg7KR/4Ib4D/RkhALu4M1fbttn2BTMfvkBco4eV88oZtjoim1CPtkLw h4XA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=NfNFr30/Gg9TdganHTwNnY5SbQlbER1mpFf/p6uD204=; b=s6Vs2HCf5tF0TyQfUwYe5ZFsoAfQ6E3q2TAfuAgSwbPU6NtKaOWO/ifUIDg+RKzeWs iEe4OEvI0o5Y9cjfRSmcCtCm3ykuhHwzx6nG8CdPT7jsSk0UNsiwpLrGb01YEOW7zs1X DRuL1ITUQoC12xTSUZdVD4ws+suqC7/MSG2cDrIksghobQOoXm3Qrj6cK23PcygMl+YN VkhiNUXSRs9WFOKQ8DsDPdZ93oSp3waBTNugHtk2ScURBdAQvqWOaCdDyrJqTvR7UNBn 7a7diJWdwAnAfrO9paksc0MiucA+DmgBEYeLu+I1zAaxdoG/vNj18SCCpcig3PRlDqZz xS7Q== X-Gm-Message-State: AIkVDXJNTiMl4yT9d4cjkS6pyPau8hQT6OCrGf9yO+QjBpP0O8E/xfabOv8HPQg3jRVjrQKVW7btkfEWo06Z3Q== X-Received: by 10.37.165.6 with SMTP id h6mr18484236ybi.34.1482761892134; Mon, 26 Dec 2016 06:18:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.129.165.87 with HTTP; Mon, 26 Dec 2016 06:18:11 -0800 (PST) In-Reply-To: <5860C842.90809@abelian.org> References: <5860C842.90809@abelian.org> From: Andy Talbot Date: Mon, 26 Dec 2016 14:18:11 +0000 Message-ID: To: rsgb_lf_group@blacksheep.org X-Scan-Signature: 1bc6486c2865e7dc2ff7578e6d7fc226 Subject: Re: LF: Article on forward error correction Content-Type: multipart/alternative; boundary=94eb2c19fdeede0404054490679d X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false X-Scanned-By: MIMEDefang 2.75 Status: O X-Status: X-Keywords: X-UID: 9958 --94eb2c19fdeede0404054490679d Content-Type: text/plain; charset=UTF-8 Absolutely brilliant. The best overall description of FEC I've ever read. Andy G4JNT On 26 December 2016 at 07:35, Paul Nicholson wrote: > > 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 > -- > > --94eb2c19fdeede0404054490679d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Absolutely brilliant. The best overall description of FEC = I've ever read.

Andy =C2=A0G4JNT

On 26 December 2016 at 07= :35, Paul Nicholson <vlf0403@abelian.org> wrote:

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.=C2=A0 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.

=C2=A0http://abelian.org/fec/pn161218/

or in pdf format

=C2=A0http://abelian.org/fec/pn161218.pdf

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

--
Paul Nicholson
--


--94eb2c19fdeede0404054490679d--