Return-Path: X-Spam-DCC: paranoid 1233; Body=3 Fuz1=3 Fuz2=3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on lipkowski.org X-Spam-Level: * X-Spam-Status: No, score=1.7 required=5.0 tests=BAYES_00,DNS_FROM_AHBL_RHSBL, FORGED_MUA_OUTLOOK 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 t4LGp3k2000501 for ; Thu, 21 May 2015 18:51:03 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1YvTdi-00057d-4W for rs_out_1@blacksheep.org; Thu, 21 May 2015 17:48:10 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1YvTdh-00057U-Rb for rsgb_lf_group@blacksheep.org; Thu, 21 May 2015 17:48:09 +0100 Received: from rgout0402.bt.lon5.cpcloud.co.uk ([65.20.0.215]) by relay1.thorcom.net with esmtp (Exim 4.85) (envelope-from ) id 1YvTdg-0001BN-2a for rsgb_lf_group@blacksheep.org; Thu, 21 May 2015 17:48:08 +0100 X-OWM-Source-IP: 86.183.229.144(GB) X-OWM-Env-Sender: alan.melia@btinternet.com X-CTCH-RefID: str=0001.0A090202.555E0C45.000A,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0 X-Junkmail-Premium-Raw: score=38/50,refid=2.7.2:2015.5.19.212118:17:38.936,ip=86.183.229.144,rules=__HAS_MSGID, __SANE_MSGID, MSGID_32HEX_LC, INVALID_MSGID_NO_FQDN, __MSGID_32HEX, __HAS_FROM, __PHISH_FROM2, __FRAUD_WEBMAIL_FROM, __TO_MALFORMED_2, __TO_NO_NAME, __REFERENCES, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_PATH, __C230066_P5, __SUBJ_ALPHA_NEGATE, __FORWARDED_MSG, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_2000_2999, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, __URI_NS, SXL_IP_DYNAMIC[144.229.183.86.fur], HTML_00_01, HTML_00_10, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __PHISH_FROM, __OUTLOOK_MUA, __PHISH_SPEAR_STRUCTURE_1, RDNS_SUSP, __FRAUD_WEBMAIL, FORGED_MUA_OUTLOOK, BODY_SIZE_7000_LESS, REFERENCES X-CTCH-Spam: Unknown Received: from gnat (86.183.229.144) by rgout04.bt.lon5.cpcloud.co.uk (8.6.122.06) (authenticated as alan.melia@btinternet.com) id 555B92EE0042699F for rsgb_lf_group@blacksheep.org; Thu, 21 May 2015 17:47:44 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=btcpcloud; t=1432226867; bh=w3B76tgsS6kfzTBg3MQZpeRwQ9YZUW3lcKT1ohZI774=; h=Message-ID:From:To:References:Subject:Date:MIME-Version:X-Mailer; b=ngaP2kOMnc4KfyI5GQJJZJD4DwyBlZq77nhekqZTjNsVkwF97wWMNkHJ2fsZRpKQK3Xub1qlwBaFeajkuOo4PowRkR3mcqRy+zpad0Mq1PKLWhW/7mhdGjCwnQ7thfB/grXjDpoakeo9iZ1Qpxyhx3DYg0qnlKu6JdhUmNqGyeM= Message-ID: From: "Alan Melia" To: References: <555CCC21.4060901@gmx.com> <555E100C.25784.C7C6D2@mike.dennison.ntlworld.com> Date: Thu, 21 May 2015 17:47:50 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5931 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-Scan-Signature: 1bc6486c2865e7dc2ff7578e6d7fc226 Subject: Re: LF: MF 630m: False Decode or Real? 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: 3205 A couple of comments on the statistics......this has little to do with the decode process itself. The timing only goes to show that the "decoded" call sign was active at the time NOT that he was really received, but might have been. Graham thinks that because there were no more false decodes in the previous 24 hours this one MUST be good. Statistics dont work like that ! If it is a million to one for a false decode you must expect at least near to a million decodes before another false one. On the contrary 2 questionable decodes of the same call would be extremely unlikely to be a random correlation so would provide good evidence the call was actually received and decoded properly. The probability of one true decode but not a second due to fading is very (very) low but not impossible. Next though many do not seem to appreciate it, statistics dont "prove" anything, they provide a measure of the probability of an expected outcome. You determine both the probability of the expected outcome and also the probability it could be just random chance. The bigger the difference then the more likely the expected event occured. This is what makes a second decode so powerful. People DO win the lottery every week! So false decodes do happen by chance.....but the same lottery winners rarely win two weeks in succession. Alan G3NYK ----- Original Message ----- From: "Mike Dennison" To: Sent: Thursday, May 21, 2015 5:04 PM Subject: Re: LF: MF 630m: False Decode or Real? > Very likely a false decode. The clue is the two question marks. In my > experience, almost every decode with question marks is false, and > there are very few cases where these particular decodes are useful. I > believe it would be helpful not to display these at all. > > Having said that, the deep search facility in Opera is very useful > and has revealed some very interesting propagation information. But > only using the decodes without the question marks which, again in my > experience, are almost always genuine. > > Mike, G3XDV > =========== > >> Just popped up at my RX: >> >> 17:52 477 VK3ELV de DF1VB/3 Op8 Deep Search ?? 16348 km -37 dB in >> Dortmund with 140w + Top loaded L 18m vert 80m horz >> >> Any comments welcome >> >> 73, Jochen >> >> >> >> -- >> -= DF1VB =- >> -= KH2MM =- >> Jochen Althoff >> +49 171 2020206 >> >> "The wireless telegraph is not difficult to understand. >> The ordinary telegraph is like a very long cat. >> You pull the tail in New York, and it meows in Los Angeles. >> The wireless is the same, only without the cat." >> (Albert Einstein) >> >> >> >> ----- >> No virus found in this message. >> Checked by AVG - www.avg.com >> Version: 2015.0.5941 / Virus Database: 4347/9830 - Release Date: >> 05/21/15 >> > > >