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: : mailn 1480; 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 v57J1VGk008989 for ; Wed, 7 Jun 2017 21:01:32 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1dIg8I-0002eW-3I for rs_out_1@blacksheep.org; Wed, 07 Jun 2017 19:56:42 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1dIg8H-0002eN-4r for rsgb_lf_group@blacksheep.org; Wed, 07 Jun 2017 19:56:41 +0100 Received: from omr-a008e.mx.aol.com ([204.29.186.51]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.89) (envelope-from ) id 1dIg8C-0005c7-JQ for rsgb_lf_group@blacksheep.org; Wed, 07 Jun 2017 19:56:39 +0100 Received: from mtaomg-aal01.mx.aol.com (mtaomg-aal01.mx.aol.com [172.27.20.207]) by omr-a008e.mx.aol.com (Outbound Mail Relay) with ESMTP id 92F403800071 for ; Wed, 7 Jun 2017 14:56:33 -0400 (EDT) Received: from core-acb10h.mail.aol.com (core-acb10.mail.aol.com [172.27.24.10]) by mtaomg-aal01.mx.aol.com (OMAG/Core Interface) with ESMTP id C398838000085 for ; Wed, 7 Jun 2017 14:56:31 -0400 (EDT) Received: from 188.192.95.60 by webprd-a27.mail.aol.com (10.72.57.49) with HTTP (WebMailUI); Wed, 07 Jun 2017 14:56:31 -0400 Date: Wed, 7 Jun 2017 14:56:31 -0400 From: Markus Vester To: rsgb_lf_group@blacksheep.org Message-Id: <15c83ea53fb-5674-3a681@webprd-a27.mail.aol.com> In-Reply-To: <59382E2E.5000306@posteo.de> MIME-Version: 1.0 X-MB-Message-Source: WebUI X-MB-Message-Type: User X-Mailer: JAS STD X-Originating-IP: [188.192.95.60] x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20150623; t=1496861793; bh=NgErq3jg8+w+I3tf6GV9umvffWg6Skv/zZ+6qjI0wa8=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=yV1y0ENcZexSSK7UoYftLTIofdeDPEvQpMFbfHZxGT+ASKuko44o0l0PY24n4QG5p y0o1i/B8kUliVfqXb5IUeCFmUOQzoXLCKe1GZ7r2icy1P5P34VUIzPM/DRkC9NDl6q Z3rd77gorvBibuiW0dIWyYOt6aBkldeuIwMLeN5Y= x-aol-sid: 3039ac1b14cf59384c5f1e9f X-Scan-Signature: 0cdfd8d5ce44f1724c623c4ac9f44df6 Subject: Re: LF: Bugfix for ebnaut_ifft utility Content-Type: multipart/alternative; boundary="----=_Part_292095_1461638698.1496861791224" 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: RO X-Status: X-Keywords: X-UID: 11919 ------=_Part_292095_1461638698.1496861791224 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Stefan, this is not easy to say as it depends on a number of circumstances. In your= local test, the difference was quite large (EbN0 =3D 40.25 dB vs 41.57 dB)= , but this is because the lack of external noise emphasized the relatively = small artifact on the signal. In a more realistic scenario the individual s= ymbols are buried in the noise. Considering an EbNaut sequence with e.g. N= =3D1000 symbols, the signal energy is quasi-randomly spread over 1000 frequ= ency bins. Only one of these bins would be affected or "lost", suggesting a= n SNR loss on the order of 0.1% power or 0.004 dB. Best 73, Markus -----Urspr=C3=BCngliche Mitteilung-----=20 Von: DK7FC An: rsgb_lf_group Verschickt: Mi, 7. Jun 2017 18:49 Betreff: Re: LF: Bugfix for ebnaut_ifft utility Thanks Markus,=20 What does minor SNR degradation mean, in dB, and on what does this value d= epend? (e.g. transmission time, symbol length, etc). 73, Stefan Am 07.06.2017 17:59, schrieb Markus Vester:=20 Dear EbNauteers,=20 I recently stumbled upon a bug in my ebnaut_ifft3a utility, which is used t= o convert SpecLab FFT export files to IQ wav files. The first step of the i= nverse FFT is to take the complex conjugate of the data array. Due to the b= ug, the respective loop was executed only N-1 times, leaving a sign error i= n the imaginary part of a single bin next to the center frequency. When fed= with a high-SNR signal close to SpecLab's center frequency, this can produ= ce strange undulation patterns in the phase display and a minor SNR degrada= tion for the decoder. The bug has been fixed in version 3b, available on http://df6nm.bplaced.net/VLF/fec_tests/ebnaut_ifft3b.zip Best regards, Markus (DF6NM) ------=_Part_292095_1461638698.1496861791224 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hi Stefan,

this is not easy to say as it depends = on a number of circumstances. In your local test, the difference was quite = large (EbN0 =3D 40.25 dB vs 41.57 dB), but this is because the la= ck of external noise emphasized the relatively small artifact on the s= ignal. In a more realistic scenario the individual symbols are buried = in the noise. Considering an EbNaut sequence with e.g. N=3D1000 symbol= s, the signal energy is quasi-randomly spread over 1000 frequency bins= . Only one of these bins would be affected or "lost", suggesting an SN= R loss on the order of 0.1% power or  0.004 dB.

Best 73,
Mar= kus

-----Urspr=C3=BCngliche Mitteilung-----
Von: DK7FC <selbe= rdenken@posteo.de>
An: rsgb_lf_group <rsgb_lf_group@blacksheep.org= >
Verschickt: Mi, 7. Jun 2017 18:49
Betreff: Re: LF: Bugfix for eb= naut_ifft utility

Thanks Markus,

What does minor SNR degradation mean, in dB, and on what does this value depend? (e.g. transmission time, symbol length, etc).

73, Stefan

Am 07.06.2017 17:59, schrieb Markus Vester:

Dear EbNauteers,

I recently stumbled upon a bug in my ebnaut_ifft3a utility, which is used to convert SpecLab FFT export files to IQ wav files. The first step of the inverse FFT is to take the complex conjugate of the data array. Due to the bug, the respective loop was executed only N-1 times, leaving a sign error in the imaginary part of a single bin next to the center frequency. When fed with a high-SNR signal close to SpecLab's center frequency, this can produce strange undulation patterns in the phase display and a minor SNR degradation for the decoder.

The bug has been fixed in version 3b, available on
 http://df6nm.bplaced.net/VLF/fec_tests/ebnaut_ifft3b.zip

Best regards,
Markus (DF6NM)

------=_Part_292095_1461638698.1496861791224--