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 w2NE7CFS008077 for ; Fri, 23 Mar 2018 15:07:14 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1ezND6-0000px-If for rs_out_1@blacksheep.org; Fri, 23 Mar 2018 13:58:24 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1ezND4-0000po-Ju for rsgb_lf_group@blacksheep.org; Fri, 23 Mar 2018 13:58:22 +0000 Received: from rgout0207.bt.lon5.cpcloud.co.uk ([65.20.0.206] helo=rgout02.bt.lon5.cpcloud.co.uk) by relay1.thorcom.net with esmtp (Exim 4.89) (envelope-from ) id 1ezND1-0008Ci-AR for rsgb_lf_group@blacksheep.org; Fri, 23 Mar 2018 13:58:21 +0000 X-OWM-Source-IP: 86.181.245.90 (GB) X-OWM-Env-Sender: alan.melia@btinternet.com X-RazorGate-Vade-Classification: clean X-RazorGate-Vade-Verdict: clean 0 X-VadeSecure-score: verdict=clean score=0/300, class=clean X-SNCR-VADESECURE: CLEAN X-RazorGate-Vade-Verdict: clean 0 X-RazorGate-Vade-Classification: clean X-RazorGate-Vade: gggruggvucftvghtrhhoucdtuddrgedtgedrvddugdehkecutefuodetggdotefrodftvfcurfhrohhfihhlvgemuceutffkvffkuffjvffgnffgvefqofdpqfgfvfenuceurghilhhouhhtmecufedttdenucenucfjughrpefkhffvfhfuffggtgfrigfoqfesrgdtjeepuddtudenucfhrhhomhepfdetlhgrnhcuofgvlhhirgdfuceorghlrghnrdhmvghlihgrsegsthhinhhtvghrnhgvthdrtghomheqnecukfhppeekiedrudekuddrvdeghedrledtnecurfgrrhgrmhephhgvlhhopehgnhgrthdpihhnvghtpeekiedrudekuddrvdeghedrledtpdhmrghilhhfrhhomhepoegrlhgrnhdrmhgvlhhirgessghtihhnthgvrhhnvghtrdgtohhmqeenucevlhhushhtvghrufhiiigvpedt Received: from gnat (86.181.245.90) by rgout02.bt.lon5.cpcloud.co.uk (9.0.019.24-1) (authenticated as alan.melia@btinternet.com) id 5A9D382201B0EA9F for rsgb_lf_group@blacksheep.org; Fri, 23 Mar 2018 13:58:18 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btinternet.com; s=btcpcloud; t=1521813499; bh=0HPj7iBE8E6CBB8q1ezDj10N4QcbNSCNRCzd40ejBTk=; h=Message-ID:From:To:References:Subject:Date:MIME-Version:X-Mailer; b=Fc440kwStOcF9kDt95ZMGYeXVSFvWaz5MFlceTSOx5vTCOVRQDnijUKLekB6CjDmkA1j0btm18rtKyZRvkGvUACZ2BLfjv4oUEWYaLntf4phrJfIMHWwokotx0ZhRoU1qv3kfrBlhE73qBvELQqQsWGiFR+PQd6OjnIbG0HHNUY= Message-ID: From: "Alan Melia" To: References: <579355A36AEE9D4FA555C45D556003ABA3C3C921@servigilant.vigilant.local> <579355A36AEE9D4FA555C45D556003ABA3C3CA5F@servigilant.vigilant.local> Date: Fri, 23 Mar 2018 13:57:59 -0000 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-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: Ok Luis thank you for that, I find it one of the problems with WSPR that one doesnt know when the stations are off-air or spots not loaded, power changed, timing changed. I suppose if one analysed enough data this might not be so important. There are lots of effects that can kill an otherwise seemingly good night, but nothing I have found that will predict them. :-(( [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 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: 01bbe366c6256c79a1025d55a83a32a6 Subject: LF: Re: RE: Re: MF path to Reunion still alive Content-Type: multipart/alternative; boundary="----=_NextPart_000_004B_01D3C2AE.F3C9C0E0" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: * X-Spam-Status: No, hits=1.7 required=5.0 tests=FORGED_MUA_OUTLOOK,HTML_60_70, HTML_MESSAGE 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 This is a multi-part message in MIME format. ------=_NextPart_000_004B_01D3C2AE.F3C9C0E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Ok Luis thank you for that, I find it one of the problems with WSPR that = one doesnt know when the stations are off-air or spots not loaded, power = changed, timing changed. I suppose if one analysed enough data this = might not be so important. There are lots of effects that can kill an = otherwise seemingly good night, but nothing I have found that will = predict them. :-(( The advantage with WSPR is that there are more data than one would get = from visual (or audible) modes. A log of activity of particular pairs of = stations might help. It is the old propagation conundrum ....if no one = transmits nothing is heard so conditions must be bad :-)) Best Wishes Alan G3NYK ----- Original Message -----=20 From: VIGILANT Luis Fern=E1ndez=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Friday, March 23, 2018 11:23 AM Subject: LF: RE: Re: MF path to Reunion still alive Hi Alan =20 Unfortunately I can not keep transmitting every night and go QRT when = strong winds or rain are forecast. So, it becomes an intermitent = activity This week I have been just transmitting for two nights. And will be = QRT again tonight for two more nights L =20 Night from march 21 to 22 did NOT produced any TA spots and NO spots = at Reunion Night from march 22 to 23 was better, unique spot from Pascal and = three from Paul N1BUG, as explained =20 Don't know if there is a way to retrieve long therm WSPR data and = export it to Excel for example, for further analysis Anyone knows how ? =20 73 de Luis EA5DOM=20 =20 De: owner-rsgb_lf_group@blacksheep.org = [mailto:owner-rsgb_lf_group@blacksheep.org] En nombre de Alan Melia Enviado el: viernes, 23 de marzo de 2018 11:57 Para: rsgb_lf_group@blacksheep.org Asunto: LF: Re: MF path to Reunion still alive =20 Hi Luis that is interesting. I presume signal and spotter were active = during the the earlier low Dst period?? =20 I had wondered whether that path might not be so severely affected by = electron precipitation being much further from the poles than the usual = E-W working paths. The profile suggests the Dst is due for a dip later = but have not checked the Solar wind predictions today. Ah there was a = Kp=3D4 just after midnight but that will not affect the path until = probably 23/24th =20 Alan G3NYK ----- Original Message -----=20 From: VIGILANT Luis Fern=E1ndez=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Friday, March 23, 2018 7:27 AM Subject: LF: MF path to Reunion still alive =20 Hi MF=20 =20 Last night I got a unique spot from Pascal, FR5DH. This amazing path = seems to be possible as soon as DST recovers =20 May be this year Pascal can keep the Rx running permanently and can = check what happens during summer in northern hemisphere =20 Only N1BUG reported me for TA, just three spots =20 73 de Luis EA5DOM ------=_NextPart_000_004B_01D3C2AE.F3C9C0E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Ok Luis thank you for that, I find it = one of the=20 problems with WSPR that one doesnt know when the stations are off-air or = spots=20 not loaded, power changed, timing changed. I suppose if one analysed = enough data=20 this might not be so important. There are lots of effects that can kill = an=20 otherwise seemingly good night, but nothing I have found that will = predict them.=20 :-((
 
The advantage with WSPR is that there = are more data=20 than one would get from visual (or audible) modes. A log of activity of=20 particular pairs of stations might help. It is the old propagation = conundrum=20 ....if no one transmits nothing is heard so conditions must be bad=20 :-))
 
Best Wishes
Alan
G3NYK
 
----- Original Message -----
From:=20 VIGILANT = Luis=20 Fern=E1ndez
Sent: Friday, March 23, 2018 = 11:23=20 AM
Subject: LF: RE: Re: MF path to = Reunion=20 still alive

Hi Alan

 

Unfortunately I can not keep transmitting every night and = go QRT=20 when strong winds or rain are forecast. So, it becomes an intermitent=20 activity

This week I have been just transmitting for two nights. = And will be=20 QRT again tonight for two more nights L

 

Night from march 21 to 22 did NOT produced any TA spots = and NO=20 spots at Reunion

Night from march  22 to 23 was better, unique spot = from Pascal=20 and three from Paul N1BUG, as explained

 

Don=92t know if there is a way to retrieve long therm = WSPR data and=20 export it to Excel for example, for further = analysis

Anyone=20 knows how ?

 

73=20 de Luis

EA5DOM=20

 

De:=20 owner-rsgb_lf_group@blacksheep.org = [mailto:owner-rsgb_lf_group@blacksheep.org]=20 En nombre de Alan Melia
Enviado el: viernes, 23 de = marzo de=20 2018 11:57
Para: = rsgb_lf_group@blacksheep.org
Asunto: LF:=20 Re: MF path to Reunion still alive

 

Hi Luis=20 that is interesting. I presume signal and spotter were active during = the the=20 earlier low Dst period??

 

I had=20 wondered whether that path might not be so severely affected by = electron=20 precipitation being much further from the poles than the usual E-W = working=20 paths. The profile suggests the Dst is due for a dip later but  = have not=20 checked the Solar wind predictions today. Ah there was a Kp=3D4 just = after=20 midnight but that will not affect the path until probably = 23/24th

 

Alan

G3NYK

-----=20 Original Message -----

Sent: Friday,=20 March 23, 2018 7:27 AM

Subject: LF: MF=20 path to Reunion still alive

 

Hi MF

 

Last night I got a unique spot from Pascal, FR5DH. This = amazing=20 path seems to be possible

as soon as DST recovers

 

May be this year Pascal can keep the Rx running = permanently and=20 can check what happens during

summer in northern = hemisphere

 

Only N1BUG reported me for TA, just three=20 spots

 

73=20 de Luis

EA5DOM

------=_NextPart_000_004B_01D3C2AE.F3C9C0E0--