Return-Path: Received: from rly-dd07.mx.aol.com (rly-dd07.mail.aol.com [172.19.141.154]) by air-dd07.mail.aol.com (v121_r4.4) with ESMTP id MAILINDD071-b8b499f47f7274; Fri, 20 Feb 2009 19:17:11 -0500 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by rly-dd07.mx.aol.com (v121_r4.4) with ESMTP id MAILRELAYINDD075-b8b499f47f7274; Fri, 20 Feb 2009 19:16:57 -0500 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1LafXo-0001BZ-4o for rs_out_1@blacksheep.org; Sat, 21 Feb 2009 00:16:36 +0000 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1LafXn-0001BQ-PS for rsgb_lf_group@blacksheep.org; Sat, 21 Feb 2009 00:16:35 +0000 Received: from imr-d02.mx.aol.com ([205.188.157.40]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1LafXm-0006bE-FR for rsgb_lf_group@blacksheep.org; Sat, 21 Feb 2009 00:16:35 +0000 Received: from G0MRF@aol.com by imr-d02.mx.aol.com (mail_out_v39.1.) id l.c25.558c567c (39954) for ; Fri, 20 Feb 2009 19:15:05 -0500 (EST) From: G0MRF@aol.com Message-ID: Date: Fri, 20 Feb 2009 19:15:05 EST To: rsgb_lf_group@blacksheep.org MIME-Version: 1.0 X-Mailer: 9.0 SE for Windows sub 5014 X-Spam-Flag:NO X-Karma: unknown: X-Spam-Score: 0.6 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001,NO_REAL_NAME=0.55 Subject: Re: LF: WSPR Spots Content-Type: multipart/alternative; boundary="-----------------------------1235175305" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: * X-Spam-Status: No, hits=1.1 required=5.0 tests=HTML_30_40,HTML_MESSAGE, NO_REAL_NAME 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-IP: 193.82.116.20 -------------------------------1235175305 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Hi Andy. If the WSPR software has any sort of internal data storage for callsigns, then it may be showing the same 'characteristics' that cause so much trouble within the EME community. JT65 has a list of known EME stations and a mode which uses a 'deep search' algorithm. Problem is, that the software searches a database from small fragments actually received and has a best guess at a call. Many EME stations delete the internal database or turn off the deep search facility so that only correctly decoded transmissions are displayed. Thanks David G0MRF In a message dated 20/02/2009 22:12:10 GMT Standard Time, andy.g4jnt@googlemail.com writes: According to the WSPR Spot database, there is some "interesting" DX being received chez GM4ISM. Is there some carrier or coherent QRM present to generate these false hits? -------------------------------1235175305 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable

Hi Andy.

If the WSPR software has any sort of internal data storage for callsign= s,=20 then it may be showing the same 'characteristics' that cause so much trouble= =20 within the EME community.

JT65 has a list of known EME stations and a mode which uses a 'dee= p=20 search' algorithm.

Problem is, that the software searches a database from small=20 fragments actually received and has a best guess at a call.

Many EME stations delete the internal database or turn off the deep sea= rch=20 facility so that only correctly decoded transmissions are displayed.

Thanks

David G0MRF

In a message dated 20/02/2009 22:12:10 GMT Standard Time,=20 andy.g4jnt@googlemail.com writes:

Acco= rding to the WSPR Spot database, there is some "interesting"=20 DX
being received chez GM4ISM.
Is there some carrier or coherent&nbs= p;=20 QRM present to generate these false hits?

-------------------------------1235175305--