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 w1QD4Pmx001728 for ; Mon, 26 Feb 2018 14:04:27 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1eqINL-0001pv-E1 for rs_out_1@blacksheep.org; Mon, 26 Feb 2018 12:59:27 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1eqINK-0001pm-L7 for rsgb_lf_group@blacksheep.org; Mon, 26 Feb 2018 12:59:26 +0000 Received: from mout.perfora.net ([74.208.4.194]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1eqINH-0003pj-PD for rsgb_lf_group@blacksheep.org; Mon, 26 Feb 2018 12:59:25 +0000 Received: from [192.168.1.129] ([72.224.254.201]) by mrelay.perfora.net (mreueus002 [74.208.5.2]) with ESMTPA (Nemesis) id 0M26jF-1ebwIU1qOp-00tygW; Mon, 26 Feb 2018 13:57:53 +0100 To: "Discussion of the Lowfer (US, European, & UK) and MedFer bands" , 600 / 630 Meter Group <600mrg@w7ekb.com>, "rsgb_lf_group@blacksheep.org" , "rsgb_lf_group@yahoogroups.co.uk" From: N1BUG Message-ID: <22427f06-486d-f7fd-965f-70ed200d2b8d@n1bug.com> Date: Mon, 26 Feb 2018 07:57:51 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Language: en-US X-Provags-ID: V03:K0:QgxjBfKrKqcBb2QGEq9yfLQUHQmIg/BqBCDZmZ+UKtUatAeo7Rs uITRylwb46dmdpefbs0LyissXwmxRONJLDmNVJ5V9T5b1sp4EWWj4EI2uEGbNPqSupvAjpF jAZ0i2emQAjOT6o7jXluyphcvzu6SGfswJijiF5BlgElGIfLYhGigcp6VFChYHPeXrIz4wr KLW9uCssy/bHZwMIectSA== X-UI-Out-Filterresults: notjunk:1;V01:K0:56FW77l4E2M=:y/i96MTYUf7slciQZicqRh fxJ65j2dp4HE8dESHiBSHnGQ8cJevXv5NPq7mOFmFtNIu/H4IeHmVX34E2n3CxN4LYmKX/jSC 74RIHw9mHoFkSP/IhrzNS8AWRIO4sG3uqiR2DVJk5YmxAE7PNMe7+IWmpJK08gW2RWzuA0xHY CdTNKx/9WbVKMSJe1qR/DtF4kqpdU/YbKif+H7jK4ZeIZYT1sMB6TV8VPtZkDigGWyGdHwa5x vymrXJWCM/9UZWI6vmQldDQqZeEq3qgKrPJbimDqqut7munOGP1fzenjZ7HrfWs0ddE5xlimK hILCDqbywdQIwOm8hFVEKGIoOFdzM01wtSIO+tDYxkgjweVFuKlgpLjT2k9n4XHnH9BVrt4sX VAwK49Rq4VaOY/tx29msyQr1HzMina1vO1NpeoQVEEyi7v42Zgoqy40L3isdCiAAU6QGa2ofh v4wVV+kuWgHknx5OXq/XHNK3TQAS66kYvGsIKBLN3tYzINQHGD+dLpB2Np8nNc9Gv1rYJ7RKb UOX8GJju6PGndEBhod7J67NA4seNJ/QbM70kP1rkUotpVwRsPU2sfaYOy92mdWi4QlMvThxJt W0hSQF7Qo6+1tfG7frw+/V6huiRgWp/NvfuE96O27mCMrC/IKJxq0nb0yGludXcM14kPZ2Zfd zI6J1O1sEg2H0MMjWFoKgvg0/ut7e3tf1k6ygj6uKOInmT9wSxbUcXE1cWO9n9i9+ajZPSMNX e9sjBjh6+Vu8lG5PAzbndBx0LhgqpE1a2AuY/+gHIy9Cxve1SJfbNFa/o4k= X-Spam-Score: 0.0 (/) 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: Yesterday's release of WSJT-X 1.9.0rc2 came with this note: "Improved decoding performance for WSPR mode, especially effective at LF and MF". I wanted to put this to the test so overnight I ran four instances of WSJT-X: [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- X-Scan-Signature: 49f0f587e44d6711c57b8a4e950ba850 Subject: LF: WSJT-X 1.9 vs 1.8 WSPR decoding test 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=0.0 required=5.0 tests=none 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 Yesterday's release of WSJT-X 1.9.0rc2 came with this note: "Improved decoding performance for WSPR mode, especially effective at LF and MF". I wanted to put this to the test so overnight I ran four instances of WSJT-X: 1.8.0 on both LF and MF using the call sign N1BUG/1 1.9.0rc2 on both LF and MF using the call sign N1BUG All spots were uploaded to WSPRnet. Both decoders on LF were fed the same audio stream. The setup is a simple SDR providing I/Q input to a physical sound card, HDSDR software output into a virtual audio cable, both versions of WSJT-X taking input from the output of that virtual cable. The MF setup was the same except using a different SDR feeding a different physical sound card. I used identical settings in all four instances of WSJT-X with the exception of different input audio source (virtual cable) for LF and MF. All of this was running in Windows 10. I watched incoming spots very closely for the first several hours. There was not much activity on LF at the time but on MF I saw 1.9 decode many WSPR transmissions that 1.8 failed to decode. Some of these were extreme weak signal down to -32 with barely visible traces on the waterfall. Others were not with some clearly visible and decoding up to -23 in 1.9, yet no decode in 1.8 despite being very clear on the waterfall in that version. I did not see a single instance where 1.8 decoded something that 1.9 failed to decode. This morning I took a quick look at statistics: MF - During a 12 hour period ending 1145z, 1.9 decoded a total of 933 WSPR transmissions while 1.8 decoded only 883. LF - During a 12 hour period ending 1150z, 1.9 decoded 253 WSPR transmissions while 1.8 decoded only 183. In all of this I do not see any obvious spurious decodes from either version. No strange call signs or stations displaced on the map from where you would expect them to be. I was not expecting to see such a large difference. I make no claim that this result is representative of what others will see. I am simply reporting the results of an experiment carried out here. 73, Paul N1BUG