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 w1QDNaTk001784 for ; Mon, 26 Feb 2018 14:23:37 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1eqIfw-0001ws-5P for rs_out_1@blacksheep.org; Mon, 26 Feb 2018 13:18:40 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1eqIfv-0001wj-1B for rsgb_lf_group@blacksheep.org; Mon, 26 Feb 2018 13:18:39 +0000 Received: from mout01.posteo.de ([185.67.36.65]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89) (envelope-from ) id 1eqIfs-0003y0-80 for rsgb_lf_group@blacksheep.org; Mon, 26 Feb 2018 13:18:37 +0000 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id 0538020F8D for ; Mon, 26 Feb 2018 14:18:33 +0100 (CET) X-DKIM-Result: Domain=posteo.de Result=Signature OK DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1519651114; bh=S/NQ9qp6TxPEno2BHMg5g57hYX1f7DuUoErycgDNJxI=; h=Date:From:To:Subject:From; b=aI7jiM38tXWaOFZxq67y0K00ksIPgl1Ut/LlbDl5yQXmBCUb5YsKxmVr14SpRg/6S uoFWgmPn4jWaivj+KyiyutNuTWvNAs4Y89rsmg5FhYxOlkLTU2v7Qc2XyJzYTwAVRT 6+7Ek8OpLGugPEUTE4626rkOJemGQTJrISVpDKgkKW1iMC+UjvJo4JmctwtVnhsje6 kZpH+KdxTokj+pz76Pbr+SUW5KR7NilqYxTL68g+pm5mZsvIJtEGHfj9nyTGx8znQQ RjDHXkY47n0P8yP5cgRnWWoRUJRpd8m1m4GqBv0AiHJewZxoIXrQ6CJywsS/WFCd7r mOy3HJnp3Xq2A== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 3zqj7r01Rxz9rxK for ; Mon, 26 Feb 2018 14:18:31 +0100 (CET) Message-ID: <5A940927.5020201@posteo.de> Date: Mon, 26 Feb 2018 14:18:31 +0100 From: DK7FC User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <22427f06-486d-f7fd-965f-70ed200d2b8d@n1bug.com> In-Reply-To: <22427f06-486d-f7fd-965f-70ed200d2b8d@n1bug.com> 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: Hello Paul, Thanks for the useful test and encouraging results. Very useful for the community. I will QSY to the new version due to your results. TNX, 73, Stefan [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: 9ca91679b330d65f05d707c2d2b164fe Subject: Re: 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 Hello Paul, Thanks for the useful test and encouraging results. Very useful for the community. I will QSY to the new version due to your results. TNX, 73, Stefan Am 26.02.2018 13:57, schrieb N1BUG: > 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 >