Return-Path: X-Spam-DCC: paranoid 1002; Body=2 Fuz1=2 Fuz2=2 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on lipkowski.org X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, RCVD_ILLEGAL_IP autolearn=no version=3.1.3 Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by paranoid.lipkowski.org (8.13.7/8.13.7) with ESMTP id t14HWTsZ013099 for ; Wed, 4 Feb 2015 18:32:29 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1YJ3hQ-0002V2-Mb for rs_out_1@blacksheep.org; Wed, 04 Feb 2015 17:25:12 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1YJ3hQ-0002Ut-4F for rsgb_lf_group@blacksheep.org; Wed, 04 Feb 2015 17:25:12 +0000 Received: from smtpout3.wanadoo.co.uk ([80.12.242.59] helo=smtpout.wanadoo.co.uk) by relay1.thorcom.net with esmtp (Exim 4.85) (envelope-from ) id 1YJ3hO-0002g2-0l for rsgb_lf_group@blacksheep.org; Wed, 04 Feb 2015 17:25:11 +0000 Received: from AGB ([2.31.59.175]) by mwinf5d39 with ME id oHR81p00b3mqbNi03HR9Np; Wed, 04 Feb 2015 18:25:09 +0100 X-ME-Helo: AGB X-ME-Date: Wed, 04 Feb 2015 18:25:09 +0100 X-ME-IP: 2.31.59.175 Message-ID: From: "Graham" To: References: <003501d03e26$e235a430$6401a8c0@JAYDELL>, <00b001d03ffc$9136a390$6d01a8c0@DELL4> <54D1F985.8602.39FA77@mike.dennison.ntlworld.com> In-Reply-To: <54D1F985.8602.39FA77@mike.dennison.ntlworld.com> Date: Wed, 4 Feb 2015 17:25:08 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Scan-Signature: 07fee8d4a4e8ea80934a0e0aaa44e788 Subject: Re: LF: OPdynamic false T/A spot Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit 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.56 on 10.1.3.10 Status: O X-Status: X-Keywords: X-UID: 2238 Mike, There is problem with the design of the reporting , dual modes where not envisaged in the original concept and a quick change is not possible , lifer span of the look up list could be reduced , but as not all stations TX with the windows-opera-app , list population would need hard opera data decodes , at the moment , it needs X 2 opera decodes to enter the list or via the web beacon , low level signals may never then be detected , the 8 day rolling cycle was to allow for Lf/MF operating patterns For now , the web-distributed spots are the authoritative output from dynamic system , the psk-map must be viewed as guidance only for low s/n spots 73-Graham -------------------------------------------------- From: "Mike Dennison" Sent: Wednesday, February 04, 2015 10:50 AM To: Subject: Re: LF: OPdynamic false T/A spot > Jay, > > I am inclined to agree with you, but almost all of the Deep Search > spots that have no question marks are genuine. If at all possible, > spots =with= the question marks should not be uploaded to PSK > Reporter as most are false. > > Also, I suggested early on that callsigns are on the database for too > long, and should only be a couple of hours after the last known > 'real' Op decode. > > These steps would of course slightly reduce the number of genuine > weak signals decoded/reported but the result would be far more > accurate and still show a useful increase in sensitivity over Op. > > Mike, G3XDV > ========== > >> Yes, we're all aware that the spots are not checked. The problem is >> PSK Reporter apparently has no way to present the ?? from an OPdynamic >> spot. Since the ?? are not there, the ?? spots look exactly the same >> as real spots. This is a serious problem as there is no way to tell >> the difference! OPdynamic spots should not be unploaded to PSK >> Reporter until this problem is corrected. Until it's corrected all OP >> reports obtained from PSK Reporter should be viewed with a great deal >> of skepticism. >> >> I have no clue as to the point you're trying to get across in the rest >> of your post. It doesn't appear relevant to the bigger problem >> outlined above. >> >> Jay W1VD WD2XNS WE2XGR/2 >> >> >> >> >> >> ----- Original Message ----- >> From: "Graham" >> To: >> Sent: Tuesday, February 03, 2015 3:23 PM >> Subject: Re: LF: OPdynamic false T/A spot >> >> >> > over 10 hours since the >> > transmitter was last on >> > >> > Could of been long path ? >> > >> > Unfortunately , as in any mode , the uploads to the psk-map >> > are not checked , >> > >> > There is something odd about the 15-07 spot as one is -42 >> > and the other -43 , must be x2 opera running with the same >> > audio feed , as there are x 2 spots from the same call >> > >> > X 2 Opera with same audio feed will produce the same results >> > . in this case the system has x2 the same call from the >> > same station , so looks to be real, un expected condition , >> > out side the operating envelope >> > >> > 73-G, >> > >> > -------------------------------------------------- >> > From: >> > Sent: Sunday, February 01, 2015 3:59 PM >> > To: >> > Subject: Re: LF: OPdynamic false T/A spot >> > >> >> According to PSK reporter I now have a spot from R7NT as of 1507 >> >> UTC ... over 10 hours since the transmitter was last on ... and in >> >> broad daylight! Reports generated by PSK reporter do not show ?? >> >> ... they appear an any normal spot and might be accepted as such. >> >> I, and other folks, don't leave OP software running 24/7 so how >> >> are we to know the spots shown on PSK reporter are real or not? I >> >> would say OPdynamic spots should not be forwarded to PSK reporter. >> >> >> >> Maybe I can apply for an award ... most spots collected without the >> >> transmitter even being turned on! ;~) >> >> >> >> Jay W1VD WD2XNS WE2XGR/2 >> >> >> >> >> >> >> >> ----- Original Message ----- >> >> From: "Graham" >> >> To: >> >> Sent: Sunday, February 01, 2015 9:13 AM >> >> Subject: Re: LF: OPdynamic false T/A spot >> >> >> >> >> >>> Jay, >> >>> >> >>> -25 over 1000 Miles , nice going ! >> >>> >> >>> Another 1 dB [ish] would of triggered the opera decoder >> >>> with Mike.. 4 min lag is spot-on SP5 is 100% random , will >> >>> of been flagged '??' on the opera listing >> >>> >> >>> 73-G, >> >>> >> >>> >> >>> >> >>> >> >>> sNR mode MHz rxTime senderCallsign senderLocator >> >>> receiverCallsignreceiverLocator receiverAntennaInformation submode >> >>> OPERA 0.136 01/02/2015 01:05 WD2XNS FN31LS WD2XNS FN31LS Beacon >> >>> Op32 every 00:00 OPERA 0.136 01/02/2015 01:22 WD2XNS FN31LS WD2XNS >> >>> FN31LS Beacon Op32 every 00:00 OPERA 0.136 01/02/2015 01:42 WD2XNS >> >>> FN31LS WD2XNS FN31LS Beacon Op32 every 00:00-17 OPERA 0.136 >> >>> 01/02/2015 01:45 WD2XNS FN31LS KA9CFD EN40OM RX Op326 OPERA 0.136 >> >>> 01/02/2015 01:45 WD2XNS FN31LS W1TAG FN42CH RX Op32 OPERA 0.136 >> >>> 01/02/2015 02:00 WD2XNS FN31LS WD2XNS FN31LS Beacon Op32 every >> >>> 00:00 OPERA 0.136 01/02/2015 02:18 WD2XNS FN31LS WD2XNS FN31LS >> >>> Beacon Op32 every 00:00-23 OPERA 0.136 01/02/2015 02:18 WD2XNS >> >>> FN31LS KA9CFD EN40OM RX Op325 OPERA 0.136 01/02/2015 02:18 WD2XNS >> >>> FN31LS W1TAG FN42CH RX Op32 OPERA 0.136 01/02/2015 02:38 WD2XNS >> >>> FN31LS WD2XNS FN31LS Beacon Op32 every 00:00-27 OPERA 0.136 >> >>> 01/02/2015 02:51 WD2XNS FN31LS KA9CFD EN40OM RX Op326 OPERA 0.136 >> >>> 01/02/2015 02:51 WD2XNS FN31LS W1TAG FN42CH RX Op32 OPERA 0.136 >> >>> 01/02/2015 02:55 WD2XNS FN31LS WD2XNS FN31LS Beacon Op32 every >> >>> 00:00 OPERA 0.136 01/02/2015 03:15 WD2XNS FN31LS WD2XNS FN31LS >> >>> Beacon Op32 every 00:00-23 OPERA 0.136 01/02/2015 03:24 WD2XNS >> >>> FN31LS KA9CFD EN40OM RX Op326 OPERA 0.136 01/02/2015 03:24 WD2XNS >> >>> FN31LS W1TAG FN42CH RX Op32 OPERA 0.136 01/02/2015 03:33 WD2XNS >> >>> FN31LS WD2XNS FN31LS Beacon Op32 every 00:00 OPERA 0.136 >> >>> 01/02/2015 03:53 WD2XNS FN31LS WD2XNS FN31LS Beacon Op32 every >> >>> 00:005 OPERA 0.136 01/02/2015 03:56 WD2XNS FN31LS W1TAG FN42CH RX >> >>> Op32-25 OPERA 0.136 01/02/2015 03:56 WD2XNS FN31LS KA9CFD EN40OM >> >>> RX Op32-31 OPERA 0.136 01/02/2015 03:56 WD2XNS FN31LS K3SIW-2 >> >>> EN52TA RX Op32 OPERA 0.136 01/02/2015 04:11 WD2XNS FN31LS WD2XNS >> >>> FN31LS Beacon Op32 every 00:00 OPERA 0.136 01/02/2015 04:29 WD2XNS >> >>> FN31LS WD2XNS FN31LS Beacon Op32 every 00:00-27 OPERA 0.136 >> >>> 01/02/2015 04:29 WD2XNS FN31LS K3SIW-2 EN52TA RX Op325 OPERA 0.136 >> >>> 01/02/2015 04:29 WD2XNS FN31LS W1TAG FN42CH RX Op32 OPERA 0.136 >> >>> 01/02/2015 04:49 WD2XNS FN31LS WD2XNS FN31LS Beacon Op32 every >> >>> 00:00-22 OPERA 0.136 01/02/2015 05:02 WD2XNS FN31LS K3SIW-2 EN52TA >> >>> RX Op326 OPERA 0.136 01/02/2015 05:02 WD2XNS FN31LS W1TAG FN42CH >> >>> RX Op32-43 OPERA 0.136 01/02/2015 05:06 WD2XNS FN31LS G3XDV IO91VT >> >>> Op32_||||_~36dB >> >>> >> >>> --FALSE---43 OPERA 0.136 01/02/2015 07:30 WD2XNS FN31LS SP5XSB >> >>> KO02LD RX Op32-------------------------------------------------- >> >>> From: Sent: Sunday, February 01, 2015 1:56 >> >>> PM To: Subject: LF: OPdynamic false >> >>> T/A spot >> >>> >> >>>> In checking last night's spots for WD2XNS ... the spot by SP5XSB >> >>>> occured after the WD2XNS transmitter had been off for over two >> >>>> hours. Please >> > >> > >> >> >> >> >> ----- >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2015.0.5646 / Virus Database: 4281/9051 - Release Date: >> 02/03/15 >> > > >