Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id vBTIZMhR010734 for ; Fri, 29 Dec 2017 19:35:23 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1eUzNY-0000Ds-2q for rs_out_1@blacksheep.org; Fri, 29 Dec 2017 18:27:36 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1eUzNX-0000Dj-6p for rsgb_lf_group@blacksheep.org; Fri, 29 Dec 2017 18:27:35 +0000 Received: from [217.72.171.73] (helo=porthos.netcom.co.uk) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1eUzNU-0004PO-DH for rsgb_lf_group@blacksheep.org; Fri, 29 Dec 2017 18:27:33 +0000 X-DKIM-Result: Domain=abelian.org Result=Signature OK DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=abelian.org ; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=rW8+7/LOhz74TNj76EaxQ8XQVVxCjKJ4qVIwq1dh0CM=; b=bRLxiXz4e9SzXaG5ghSVIq/imF bOPJCRc2MndB8QzZtN/9ZhlRS2YjgdHACa+iXk3PL05qvnzJ11+0OG+2TQ9woJOfXQnhUzIJH9mDt Ss/YE2hdL3cSa7mCamJk4coTPMctxaqOB7mf5bx5D3bmAaoyvXaErtfaE4+TvuAn4qZc=; Received: from i-194-106-52-83.freedom2surf.net ([194.106.52.83]:33407 helo=pn.abelian.org) by porthos.netcom.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1eUzNT-0005iv-52 for rsgb_lf_group@blacksheep.org; Fri, 29 Dec 2017 18:27:31 +0000 Received: from [127.0.0.1] (localhost [127.0.0.1]) by pn.abelian.org (Postfix) with ESMTP id 87A9C400068 for ; Fri, 29 Dec 2017 18:27:30 +0000 (UTC) To: rsgb_lf_group@blacksheep.org References: From: Paul Nicholson Message-ID: <29b0445b-bcb6-fc3c-add0-cbba03ad693a@abelian.org> Date: Fri, 29 Dec 2017 18:27:30 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - porthos.netcom.co.uk X-AntiAbuse: Original Domain - blacksheep.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - abelian.org X-Get-Message-Sender-Via: porthos.netcom.co.uk: authenticated_id: catchall@abelian.org X-Authenticated-Sender: porthos.netcom.co.uk: catchall@abelian.org X-Spam-Score: 1.3 (+) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Dex wrote: > New message tonight [27th] > 3 chars 16K21A CRC20 > 30 second symbols > Start 22:30 UT [...] Content analysis details: (1.3 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid 1.3 RDNS_NONE Delivered to internal network by a host with no rDNS X-Scan-Signature: ebba021850e0a5d4120636e52401e975 Subject: Re: LF: 8269.9 kHz EbNaut 27/12/17 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: * X-Spam-Status: No, hits=1.9 required=5.0 tests=FROM_ENDS_IN_NUMS,NO_COST 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 Dex wrote: > New message tonight [27th] > 3 chars 16K21A CRC20 > 30 second symbols > Start 22:30 UT Decoding from 8269.9 Hz, 2017-12-XX_22:30,+27900 vtfilter -h bp,f=8270,w=3000 vtblank -a12 -d0 -t100 ebnaut -dp16K21A -r1 -S30 -k20 -N3 -PU -L500000 -v Todmorden (6194 km) ------------------- 27/28 Eb/N0 +9.2 dB, S/N -22.9 dB/1Hz, phase -140.9 *Decoded* 28/29 Eb/N0 +5.4 dB, S/N -26.7 dB/1Hz, phase 108.7 *Decoded* Bielefeld (6917.7 km) --------------------- 27/28 Eb/N0 -2.6 dB, S/N -34.7 dB/1Hz, phase 71.2; 28/29 Eb/N0 -2.3 dB, S/N -34.4 dB/1Hz, phase -45.2; Fails to decode with stacking, Eb/N0 -5.0 dB due to phase change. Warsaw (7681.3 km) ------------------ 27/28 Eb/N0 -7.4 dB, S/N -39.6 dB/1Hz, phase 143.3; 28/29 Eb/N0 -11.5 dB, S/N -43.7 dB/1Hz, phase 85.6; Cumiana (7173.4 km) ------------------- 27/28 Eb/N0 +0.6 dB, S/N -31.6 dB/1Hz, phase 164.1 *Decoded* 28/29 Eb/N0 -2.1 dB, S/N -34.2 dB/1Hz, phase 63.2; Hawley TX (1816.2 km) --------------------- 27/28 Eb/N0 7.8 dB, S/N -24.3 dB/1Hz, phase -86.3 *Decoded* 28/29 Eb/N0 1.3 dB, S/N -30.8 dB/1Hz, phase -163.5 *Decoded* Forest VA (254.2 km) -------------------- 27/28 Eb/N0 21.2 dB, S/N -10.8 dB/1Hz, phase 115.9 *Decoded* 28/29 Eb/N0 20.4 dB, S/N -11.8 dB/1Hz, phase -14.0 *Decoded* All the rx sites show a similar phase change between the two nights, even Warsaw with the very weak signal. So, do ethics accept a decode claim if it is necessary to use published information about the transmit phase to facilitate stacking? One might argue that knowledge of the tx phase is no different to knowing the tx frequency and start time. Such knowledge does not bypass any propagation. And what about using information published from other sites about the strength and success of the transmission? A problem with stacking is the number of permutations as the number of repeats increases. Eg with four repeats, there are: One run with all four; Four runs with one repeat dropped; Six runs with two repeats dropped; Four runs with single repeats; 15 runs altogether and the operator is obliged to accept the strongest looking decode out of all of them. Each of the 15 runs has the chance of throwing up a false decode which will beat the correct decode. Therefore, knowledge that a particular repeat performed poorly at other sites allows you to drop that one with no cost in terms of false decodes. Pushing this further, once the message is published, the repeats can be selected for stacking based on their cross- correlation. You might for example have 10 repeats and be able to get a decode from the best 5, Without that knowledge you would need 252 full runs of the decoder to go through all permutations of 5 out of 10 repeats, surely enough to suffer a stronger false decode. -- Paul Nicholson --