Return-Path: X-Spam-DCC: paranoid 1169; 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=-1.4 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, NO_REAL_NAME 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 t14EiwK8012606 for ; Wed, 4 Feb 2015 15:44:58 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1YJ14E-0001aC-P9 for rs_out_1@blacksheep.org; Wed, 04 Feb 2015 14:36:34 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1YJ14E-0001a3-Cg for rsgb_lf_group@blacksheep.org; Wed, 04 Feb 2015 14:36:34 +0000 Received: from resqmta-ch2-07v.sys.comcast.net ([69.252.207.39]) by relay1.thorcom.net with esmtps (TLSv1.2:DHE-RSA-AES256-SHA:256) (Exim 4.85) (envelope-from ) id 1YJ14B-0001uq-Up for rsgb_lf_group@blacksheep.org; Wed, 04 Feb 2015 14:36:33 +0000 Received: from resomta-ch2-09v.sys.comcast.net ([69.252.207.105]) by resqmta-ch2-07v.sys.comcast.net with comcast id oEcQ1p0042GyhjZ01EcVR9; Wed, 04 Feb 2015 14:36:29 +0000 Received: from JAYDELL ([71.234.119.9]) by resomta-ch2-09v.sys.comcast.net with comcast id oEcU1p00e0CFS1j01EcUBb; Wed, 04 Feb 2015 14:36:29 +0000 X-DKIM-Result: Domain=comcast.net Result=Signature OK Message-ID: <000401d04087$f6307d80$6401a8c0@JAYDELL> From: To: References: <003501d03e26$e235a430$6401a8c0@JAYDELL>, <00b001d03ffc$9136a390$6d01a8c0@DELL4> <54D1F985.8602.39FA77@mike.dennison.ntlworld.com> Date: Wed, 4 Feb 2015 09:36:28 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1423060589; bh=lPWq0fKaLpocYDl1AOGs2kj4bvUi7iuwA5Zf2flKKVM=; h=Received:Received:Message-ID:From:To:Subject:Date:MIME-Version: Content-Type; b=Sbq2NkatlDFl3NR6snfKo2LJaURHxLqnlaPKyVXuf1ptjS6mZn3GMjCcZeiHWLC2A dW004RKisz7dmAoNc/MSXgCUqAcGDWuH2RPQIGG7p5LC7P1teokSBkUWSvFNRnyCK8 cZz6URIgYI2q0ayVrYYCvIxVku/AvnQGxACoxPpEofB9sl7EgM7VtebbxbG/7aW/Su 6+TJNS/zDOr0EqpVY8Pa0HjPloCNYJpUbu7gBcS7v6inIllIG1bjtSdCIKoFj85jDn WM11DEqe1mE7nW0498sQrqVOSoxY+DDE9iB4NQalIHhMYZLYRDolimrw0Htqq1RtXD sCaFT+wUDV6hQ== X-Scan-Signature: fa743f59d022704fe4104ed922c6083c 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: 2233 Mike We agree that OPdynamic spots with ?? should not be uploaded ... but that isn't the case at the moment. The R7NT OPdynamic spot of WD2XNS (10 hours after the transmitter was turned off) shows up right along with all of the genuine spots - it's indistinguishable. This is a problem and seriously undermines the credibility of OPERA. As for callsigns only being held for a short time in the deep search list ... I going to have to disagree. While it may put a bandaid on the serious OPdynamic problem with false spots it makes it far too easy on the correlation detector. It's possible that only one callsign might be on the list! I'd much rather have the DF6NM system where all possible stations (about 30 stations last time I checked) are present all the time. The game sure seems a lot less 'rigged' when the correlation detector has to analyze 30 callsigns rather than just one or maybe two. When you think about it, the DF6NM system must be vastly superior to OPdynamic ... considering the minute number of false spots with 30 callsigns to pick from. OPdynamic produces far more false spots and it only has a few callsigns to choose from at any time. Reducing OPdynamics choices even further (by shortening the 'holding time') would reduce false spots ... but that just points up how inferior OPdynamic really is. Not a good solution in my opinion. Jay W1VD WD2XNS WE2XGR/2 ----- Original Message ----- From: "Mike Dennison" To: Sent: Wednesday, February 04, 2015 5:50 AM 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 >> > > >