Delivered-To: daveyxm@virginmedia.com Received: by 10.50.237.98 with SMTP id vb2csp217202igc; Sun, 9 Feb 2014 03:22:48 -0800 (PST) X-Received: by 10.194.6.8 with SMTP id w8mr17974059wjw.16.1391944967316; Sun, 09 Feb 2014 03:22:47 -0800 (PST) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id ed5si4771701wib.11.2014.02.09.03.22.46 for ; Sun, 09 Feb 2014 03:22:47 -0800 (PST) Received-SPF: neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) client-ip=195.171.43.25; Authentication-Results: mx.google.com; spf=neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) smtp.mail=owner-rsgb_lf_group@blacksheep.org; dkim=pass header.i=@mx.aol.com Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1WCS5G-0005Tt-2W for rs_out_1@blacksheep.org; Sun, 09 Feb 2014 10:57:58 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1WCS5F-0005Tk-Hq for rsgb_lf_group@blacksheep.org; Sun, 09 Feb 2014 10:57:57 +0000 Received: from omr-d09.mx.aol.com ([205.188.108.133]) by relay1.thorcom.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1WCS5C-0002xN-Op for rsgb_lf_group@blacksheep.org; Sun, 09 Feb 2014 10:57:56 +0000 Received: from mtaout-mcb02.mx.aol.com (mtaout-mcb02.mx.aol.com [172.26.50.174]) by omr-d09.mx.aol.com (Outbound Mail Relay) with ESMTP id 16BE17000008E for ; Sun, 9 Feb 2014 05:57:51 -0500 (EST) Received: from White (95-91-237-152-dynip.superkabel.de [95.91.237.152]) by mtaout-mcb02.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id 4092E38000092 for ; Sun, 9 Feb 2014 05:57:48 -0500 (EST) Message-ID: <9C2AD13E5CFD44ABABF8FF80021DED3F@White> From: "Markus Vester" To: References: , <0AE8FCE0012A455E8854CB39126AA62B@White> <00b401cf250e$a4fc9420$6401a8c0@JAYDELL> <52F69E6F.6060300@gmail.com> <984B5BFDBD1644A6B4BC5F22996E9088@White> Date: Sun, 9 Feb 2014 11:57:45 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606 x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20121107; t=1391943471; bh=Zx7PonpEiSYG+erhgFEC0POWlZWYxGS3XzbNI09zpkg=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=YKuplIBUTbesMBcqxiCd31EQu9J/9+uX22IfiWOaEDYZvaO0QiG3+LZU0VC4vrfmJ ekwzTxdhB0dvo0kWxWFlgWlh992OhygPXM650Jy30fzUnA2JQ62lzYKFLjnINoEbfu bQ0dIM7EhbbFHN2Y1RBo7FK+prvT58pQtARc9Q6c= x-aol-sid: 3039ac1a32ae52f75f2c36b6 X-AOL-IP: 95.91.237.152 X-Spam-Score: -0.6 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Bob, Dex, despite suboptimal SNR conditions, the opds-16 correlator produced 6 hits for WG4XRS: http://dl.dropboxusercontent.com/u/26404526/opds.htm In the morning, the carrier from Dex on 74323 became also clearly visible in the 0.95 mHz spectrogram. So I tried to rescan the recorded files with a lower detection threshold just to see how close it was (a sort of deep deep search ;-). Using opds.ini parameters thresholddbcor=11.5 'minimum correlation peak height; default 15 dB, ns1=2 'less smoothing during carrier detection, more sensitive for stable signals; default 5 bins, and pruning out false detections on other frequencies, I ended up with 2 more spots for Bob and 3 for Dex: [...] Content analysis details: (-0.6 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [205.188.108.133 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (markusvester[at]aol.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: b2000330e4064ca60a9f57e731b892da Subject: Re: LF: Re: Can you look for us tonight with OPDS on 74.3213? Content-Type: multipart/alternative; boundary="----=_NextPart_000_0015_01CF258E.255EFE80" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,HTML_MESSAGE, MISSING_OUTLOOK_NAME 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 Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_0015_01CF258E.255EFE80 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Bob, Dex, despite suboptimal SNR conditions, the opds-16 correlator produced 6 = hits for WG4XRS: http://dl.dropboxusercontent.com/u/26404526/opds.htm In the morning, the carrier from Dex on 74323 became also clearly = visible in the 0.95 mHz spectrogram. So I tried to rescan the recorded = files with a lower detection threshold just to see how close it was (a = sort of deep deep search ;-). Using opds.ini parameters thresholddbcor=3D11.5 'minimum correlation peak height; default 15 dB, ns1=3D2 'less smoothing during carrier detection, more sensitive for = stable signals; default 5 bins,=20 and pruning out false detections on other frequencies, I ended up with 2 = more spots for Bob and 3 for Dex: opds16: date time call distance frequency bandwidth = snr correlation 2014-02-09 06:56:21 WG4XRS 6448km 74321.301Hz 5mHz -45.8dBOp 100% = 14.3dB 2014-02-09 06:23:13 WG4XRS 6448km 74321.301Hz 4mHz -47.7dBOp 86% = 15.9dB 2014-02-09 06:17:18 WG5XRS 7214km 74323.000Hz 4mHz -48.0dBOp 95% = 12.0dB 2014-02-09 06:06:40 WG4XRS 6448km 74321.301Hz 4mHz -46.2dBOp 99% = 17.2dB 2014-02-09 06:00:54 WG5XRS 7214km 74323.000Hz 3mHz -49.4dBOp 100% = 11.9dB 2014-02-09 05:50:06 WG4XRS 6448km 74321.301Hz 5mHz -46.3dBOp 98% = 14.8dB 2014-02-09 05:44:31 WG5XRS 7214km 74323.001Hz 3mHz -50.6dBOp 94% = 11.9dB 2014-02-09 05:33:33 WG4XRS 6448km 74321.301Hz 4mHz -48.6dBOp 88% = 15.1dB 2014-02-09 05:16:59 WG4XRS 6448km 74321.301Hz 5mHz -46.5dBOp 97% = 15.1dB 2014-02-09 03:21:06 WG4XRS 6448km 74321.301Hz 4mHz -49.3dBOp 100% = 14.3dB 2014-02-09 02:31:29 WG4XRS 6448km 74321.300Hz 3mHz -50.5dBOp 100% = 12.6dB In past sessions, there were still weak DCF77 artifacts exactly on whole = Hz frequencies. Even though these were not obvious in the higher noise = last night, Dex' carrier might still have been slightly impeded. This = could be cured by a small offset eg. moving 0.1 Hz down. Best 73, Markus (DF6NM) ------=_NextPart_000_0015_01CF258E.255EFE80 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Bob, Dex,
 
despite suboptimal = SNR=20 conditions, the opds-16 correlator produced 6 hits for=20 WG4XRS: http://dl.d= ropboxusercontent.com/u/26404526/opds.htm
 
In the morning, the = carrier from=20 Dex on 74323 became also clearly visible in the 0.95 mHz = spectrogram.=20 So I tried to rescan the recorded files with a lower detection threshold = just to=20 see how close it was (a sort of deep deep search ;-).
Using opds.ini=20 parameters
 thresholddbcor=3D11.5 =20 'minimum correlation peak height; default 15 dB,
 ns1=3D2  = 'less=20 smoothing during carrier detection, more sensitive for stable=20 signals; default 5 bins, 
and pruning out false detections on = other frequencies,=20 I ended up with 2 more spots for Bob and 3 for = Dex:
 
opds16: date  = time       =20 call    =20 distance     frequency   bandwidt= h =20 snr        correlation
 
2014-02-09 06:56:21 WG4XRS  = 6448km =20 74321.301Hz   5mHz -45.8dBOp 100% 14.3dB
2014-02-09 = 06:23:13=20 WG4XRS  6448km  74321.301Hz   4mHz -47.7dBOp  = 86%=20 15.9dB
2014-02-09 06:17:18 WG5XRS  7214km  = 74323.000Hz  =20 4mHz -48.0dBOp  95% 12.0dB
2014-02-09 06:06:40 WG4XRS  = 6448km =20 74321.301Hz   4mHz -46.2dBOp  99% 17.2dB
2014-02-09 = 06:00:54=20 WG5XRS  7214km  74323.000Hz   3mHz -49.4dBOp 100%=20 11.9dB
2014-02-09 05:50:06 WG4XRS  6448km  = 74321.301Hz  =20 5mHz -46.3dBOp  98% 14.8dB
2014-02-09 05:44:31 WG5XRS  = 7214km =20 74323.001Hz   3mHz -50.6dBOp  94% 11.9dB
2014-02-09 = 05:33:33=20 WG4XRS  6448km  74321.301Hz   4mHz -48.6dBOp  = 88%=20 15.1dB
2014-02-09 05:16:59 WG4XRS  6448km  = 74321.301Hz  =20 5mHz -46.5dBOp  97% 15.1dB
2014-02-09 03:21:06 WG4XRS  = 6448km =20 74321.301Hz   4mHz -49.3dBOp 100% 14.3dB
2014-02-09 = 02:31:29=20 WG4XRS  6448km  74321.300Hz   3mHz -50.5dBOp 100%=20 12.6dB
In past sessions,=20 there were still weak DCF77 artifacts exactly on whole Hz = frequencies. Even=20 though these were not obvious in the higher noise last night, Dex' = carrier might=20 still have been slightly impeded. This could be cured by a small = offset eg.=20 moving 0.1 Hz down.
 
Best = 73,
Markus = (DF6NM)
 
------=_NextPart_000_0015_01CF258E.255EFE80--