Return-Path: Received: from mtain-mk08.r1000.mx.aol.com (mtain-mk08.r1000.mx.aol.com [172.29.97.140]) by air-de05.mail.aol.com (v129.4) with ESMTP id MAILINDE051-5eb24d23abf610f; Tue, 04 Jan 2011 18:23:34 -0500 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mk08.r1000.mx.aol.com (Internet Inbound) with ESMTP id 80F27380000A3; Tue, 4 Jan 2011 18:23:33 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1PaGD8-00023g-Qd for rs_out_1@blacksheep.org; Tue, 04 Jan 2011 23:22:38 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1PaGD8-00023X-BP for rsgb_lf_group@blacksheep.org; Tue, 04 Jan 2011 23:22:38 +0000 Received: from mail-iy0-f171.google.com ([209.85.210.171]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1PaGD5-00083X-Rd for rsgb_lf_group@blacksheep.org; Tue, 04 Jan 2011 23:22:38 +0000 Received: by iyj21 with SMTP id 21so13810322iyj.16 for ; Tue, 04 Jan 2011 15:22:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=hIo1KZ3jzLjidebRksHrwuwcGOkYRXoaeoG//fK692o=; b=Xp+Zet6LHi751bTZyLG4k4AFlhtSL3XZQcHe043C/ulRKjHcYymGgyFru/bNrmFbZ0 eXwxuQ8Xx/GNsozMBGHJVjp0zo1CfYaMwIRTwvR17gnWHh5P/HrCWUirM8p1zEbCLTpS CoRW8IwbipDwHShYc8QX/xWIa8sOV7O4+J32Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=H2WPxnr/HsBDpY9PP8LaDUA4jdtkEdg1gVP2OsH1WN3GwR8numbBxVNMG6WialZzjN LSii/sxx1AzpOvrtRPl6ZD9CAR6NJeZGOueOjW4ECN23uNU7nYWE4ofe/wPkVsDtF4in LIp92va+oU8wDivIbWe6seJbeoVyE1wZ3adGs= MIME-Version: 1.0 Received: by 10.231.199.10 with SMTP id eq10mr22213809ibb.112.1294183348909; Tue, 04 Jan 2011 15:22:28 -0800 (PST) Received: by 10.231.200.211 with HTTP; Tue, 4 Jan 2011 15:22:28 -0800 (PST) In-Reply-To: <4D23A78D.90100@toya.net.pl> References: <4D23931B.50505@toya.net.pl> <4D23A78D.90100@toya.net.pl> Date: Tue, 4 Jan 2011 23:22:28 +0000 Message-ID: From: Andy Talbot To: rsgb_lf_group@blacksheep.org DomainKey-Status: good (testing) X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001 Subject: Re: LF: WSPR Reports Content-Type: multipart/alternative; boundary=90e6ba4fc4c6c9367f04990d8a5d X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=HTML_MESSAGE autolearn=no version=2.63 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-aol-global-disposition: G X-AOL-SCOLL-AUTHENTICATION: mail_rly_antispam_dkim-m281.2 ; domain : gmail.com DKIM : pass x-aol-sid: 3039ac1d618c4d23abf51aa1 X-AOL-IP: 195.171.43.25 X-Mailer: Unknown (No Version) --90e6ba4fc4c6c9367f04990d8a5d Content-Type: text/plain; charset=ISO-8859-1 The WSPR software does its own digital filtering to the 200Hz wide input band - with associated passband edges, and calculations are based on the bandwidth defined there. It will therefore work, and noise level calculation will be correct, provided the input signal cointains a flat noise spectrum wider than the internal filter bandwidth and encompasing the roll-off. Signal level is measured in the 1.46Hz FFT bin then just normalised to a convenient reference 2.5kHz bandwidth used for reporting purposes. Chosen because its nar enough an SSB filter's BW It is a pity this bandwidth value was used as it has lead to misunderstandings amongst several ops, but has become the norm and we have to just accept 2.5kHz reference bandwidth for nearly all datamode operation now. Hindsight suggests we should all have normalised to 1Hz, quoting S/N in this width, but what's a constant 34dB offset amongst friends :-) Andy www.g4jnt.com On 4 January 2011 23:04, Piotr Mlynarski wrote: > Andy Talbot pisze: > > >> 300Hz wide CW filters made a fraction of a dB difference, compared with an >> SSB filter used as a reference; >> > well, indeed , in my free time i have to look inside the wspr code .. > i just thought that it was simply 3000 Hz (ssb)/ 300 Hz (cw) = 10 > > > 73, > Piotr, sq7mpj > qth: Lodz /jo91rs/ > > --90e6ba4fc4c6c9367f04990d8a5d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
The WSPR software does its own digital filtering to the 200Hz wide in= put=A0band - with associated passband edges, =A0and calculations are based= on the bandwidth defined=A0=A0there.=A0=A0=A0
It will therefore work, and noise level calculation will be correct,= =A0provided the input signal cointains a flat noise spectrum wider than th= e internal filter bandwidth and encompasing the roll-off.
=A0
Signal level is measured in the 1.46Hz FFT bin then just normalised= to a convenient reference 2.5kHz bandwidth used for reporting purposes.= =A0 Chosen because its nar enough an SSB filter's BW=A0=A0 It is a pit= y this bandwidth value was used as=A0it has lead to misunderstandings=A0am= ongst several ops,=A0but has become the norm and we have to just accept 2.= 5kHz reference bandwidth for nearly all datamode operation now.=A0=A0=A0
=A0
Hindsight suggests we should all have=A0normalised to 1Hz, quoting S/= N in this width, but what's a constant 34dB offset=A0=A0amongst friend= s :-)
=A0
Andy
=A0
=A0
On 4 January 2011 23:04, Piotr Mlynarski <sq7mpj@toya.net.pl> wrote:
Andy Talbot pisze:=20


300Hz wide CW filters made= a fraction of a dB difference, compared with an SSB filter used as a refe= rence;
well, indeed , in my free time i have to look inside th= e wspr code ..
i just thought =A0that it was simply 3000 Hz (ssb)/ 300= Hz (cw) =3D 10=20


=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 =A0 =A0 =A0 73, Piotr, sq7mpj
qth: Lodz /jo91rs/


--90e6ba4fc4c6c9367f04990d8a5d--