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 wACMknOV029335 for ; Mon, 12 Nov 2018 23:46:56 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gMKt1-0005Db-WA for rs_out_1@blacksheep.org; Mon, 12 Nov 2018 22:40:51 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gMKst-0005DS-Pa for rsgb_lf_group@blacksheep.org; Mon, 12 Nov 2018 22:40:43 +0000 Received: from omr-a018e.mx.aol.com ([204.29.186.64]) by relay1.thorcom.net with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.91_59-0488984) (envelope-from ) id 1gMKsr-00034X-IF for rsgb_lf_group@blacksheep.org; Mon, 12 Nov 2018 22:40:42 +0000 Received: from mtaomg-aam01.mx.aol.com (mtaomg-aam01.mx.aol.com [172.27.19.147]) by omr-a018e.mx.aol.com (Outbound Mail Relay) with ESMTP id B63993800082; Mon, 12 Nov 2018 17:40:39 -0500 (EST) Received: from core-aba06b.mail.aol.com (core-aba06.mail.aol.com [172.27.22.6]) by mtaomg-aam01.mx.aol.com (OMAG/Core Interface) with ESMTP id 7AB4F38000081; Mon, 12 Nov 2018 17:40:39 -0500 (EST) Received: from 99.34.193.140 by webjas-vad028.srv.aolmail.net (10.96.35.31) with HTTP (WebMailUI); Mon, 12 Nov 2018 17:40:39 -0500 Date: Mon, 12 Nov 2018 17:40:39 -0500 From: James Hollander To: rsgb_lf_group@blacksheep.org, 600MRG@mailman.qth.net Message-Id: <1670a157bca-1ec2-4867@webjas-vad028.srv.aolmail.net> In-Reply-To: <1542060256183.45653@kuleuven.be> References: <1542060256183.45653@kuleuven.be> MIME-Version: 1.0 X-MB-Message-Source: WebUI X-MB-Message-Type: User X-Mailer: JAS STD X-Originating-IP: [99.34.193.140] x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20150623; t=1542062439; bh=D/4HIMD96vCmRudQByEr/tNNOcbZ2caE37x0l6yEiJU=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=3FMyWmfgMYvox34yHhT7hAk4KEswRvTSc7RoEmXKohjT5kGrwmIapKMQ8T2o0KiTh ZqgaVoDeVTtK7r8/HbeL48lkJY9XtJWg5OfKY7T/DvKLJYiX5w6z5qY/JquxGii60e BQ45hJUm/7YHrbAPRC94RfSHp8CeT02qXvHOYgd8= x-aol-sid: 3039ac1b13935bea01670085 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 @@CONTACT_ADDRESS@@ for details. Content preview: Rik, all, So, as I understand it, on someordinary night a MF station would/could run at least two software instances ofJT9—one instance set to decode 2 minute slow JT9, and the other instancedecoding 1 minute JT9 concurrently. [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [204.29.186.64 listed in list.dnswl.org] -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -0.0 SPF_PASS SPF: sender matches SPF record 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mrsocion[at]aol.com) 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: ae3221d431bd19e5880aa98eda07ece4 Subject: LF: SlowJT9 v0.9.02: Decode simultaneous Content-Type: multipart/alternative; boundary="----=_Part_24520_1952530547.1542062439368" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_40_50, HTML_FONTCOLOR_UNKNOWN,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 ------=_Part_24520_1952530547.1542062439368 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Rik, all, So, as I understand it, on someordinary night a MF station= would/could run at least two software instances ofJT9=E2=80=94one instance= set to decode 2 minute slow JT9, and the other instancedecoding 1 minute J= T9 concurrently. =20 =20 The 1st s/w instance is set for slow JT9. If the station you want to cal= l or haverespond to a CQ is low-SNR like a QRP, transcontinental, or transo= ceanicstation, then you activate your transmission using the slow JT9 softw= areinstance. If low-SNR stations comprisethe only intended reception, the= n slow JT9 is all you use and forget the 2nds/w instance. You get deep-SN= R receptions and QSOs thatregular JT9 can=E2=80=99t deliver. =20 The 2nd s/w instanceis set for regular JT9. Suppose the station you want to= call or have respond toa CQ is likely above, say, the 50% decode probabili= ty, at least SNR -27 dB mostof the time. Then you activate your transmissio= n on-the-fly instead with regular JT9 usingthat 2nd s/w instance. Thatway,= you either get a reply after 1 minute or have the chance to repeat yourtra= nsmission. =20 The nimble operator usesthe 1st or 2nd s/w instance that=E2=80=99s simult= aneously running asconditions and as sought-after stations warrant. No nee= d to change TX frequency. The DX may be on some other frequency thanyou, b= ut that=E2=80=99s fine. You call them with slow JT9 or regular JT9 as you = decide on-the-fly withoutchanging your frequency and they will see you on t= heir PC display if they can. =20 =20 Other stations may berunning either slow JT9 or regular JT9 at any given ti= me, and that=E2=80=99s fine toobecause you can receive them either way. You= =E2=80=99ll see stations TXing slow JT9 on one decoder window and stations = TXingregular JT9 on the other decoder window. If a station sends slow JT9 f= or awhile and then regular JT9 for a while, you=E2=80=99ll see that station= go from onedecoder window to the other.=20 =20 If a station is alreadyrunning regular JT9 diversity with two RX antennas a= nd two regular JT9 decodersconnected to SDR sub-RXs, you just add two more = decoders for slow JT9 diversityas well. Depending on your PC, use a PC powe= rful enough to run the s/winstances concurrently. =20 =20 Feel free to clarify ifI=E2=80=99m missing anything important. Very intere= sting! 73, Jim H W5EST =20 -----Original Message----- From: Rik Strobbe To: rsgb_lf_group ; rsgb_lf_group Sent: Mon, Nov 12, 2018 4:05 pm Subject: Re: LF: SlowJT9 v0.9.02 Hi Paul,it seems that we will have to make a choice: - either the old JT9-2= and JT9-5 standard and only decoding one mode at a time- or keeping the cu= rrent JT9-2 and JT9-5 parameters and keep the option open to decode all JT9= submodes simultanious.I tend to go for the second option, but everyone is = welcome to convince me otherwise.73, Rik ON7YD - OR7T_____________________= ___________________Van: owner-rsgb_lf_group@blacksheep.org namens N1BUG Verzonden: maandag 12 nov= ember 2018 22:43Aan: rsgb_lf_group@blacksheep.org; rsgb_lf_group@yahoogroup= s.co.ukOnderwerp: Re: LF: SlowJT9 v0.9.02I can confirm something similar. M= y CPU is running around 30% (it'sa VERY busy system with many apps running)= . When SlowJT9 invokes thedecoder I see a short spike to 50%, sometimes as = high as 55%.73,Paul N1BUGOn 11/12/18 4:13 PM, Rik Strobbe wrote:> I just ha= d a look at the CPU usage of my computer:> it is wobbeling between 2% and 5= % but peaks to 40% if the JT9 decoder is invoked.> I am afraid that invokin= g 3 instances of the JT9 decoder at (almost) the same time is not a good id= ea.>> 73, Rik ON7YD - OR7T ------=_Part_24520_1952530547.1542062439368 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Rik, all,        S= o, as I understand it, on some ordinary night a MF station would/could run at least two software instances= of JT9=E2=80=94one instance set to decode 2 minute slow JT9, and the other ins= tance decoding 1 minute JT9 concurrently. = ;
 
The 1st  s/w instance is set for slow J= T9.   If the station yo= u want to call or have respond to a CQ is low-SNR like a QRP, transcontinental, or transoceanic station, then you activate your transmission using the slow JT9 software instance.   If low-SNR = stations comprise the only intended reception, then slow JT9 is all you use and forget the 2<= sup>nd s/w instance.   You get deep-SNR receptions and QSOs t= hat regular JT9 can=E2=80=99t deliver.
 
The 2nd s/w= instance is set for regular JT9. Suppose the station you want to call or have respon= d to a CQ is likely above, say, the 50% decode probability, at least SNR -27 dB = most of the time. Then you activate your transmission on-the-fly instead wi= th regular JT9 using that 2nd s/w instance.  = That way, you either get a reply after 1 minute or have the chance to repeat you= r transmission.
 
The nimble operator us= es the 1st  or 2nd  s/w instance that= =E2=80=99s simultaneously running as conditions and as sought-after stations warrant.  No need to change TX frequency.  The DX may be on some other frequency than you, but that=E2=80=99s fine.  You call them with slow JT9 or regular JT9 as you decide on-th= e-fly without changing your frequency and they will see you on their PC display if they c= an. 
 
Other stations may be running either slow JT9 or regular JT9 at any given time, and that=E2=80=99= s fine too because you can receive them either way.=   You=E2=80=99ll see stations TXing slow JT9 on one decoder window and= stations TXing regular JT9 on the other decoder window. If a station sends slow JT9 for a while and then regular JT9 for a while, you=E2=80=99ll see that station go = from one decoder window to the other.
 
If a station is alread= y running regular JT9 diversity with two RX antennas and two regular JT9 deco= ders connected to SDR sub-RXs, you just add two more decoders for slow JT9 diver= sity as well. Depending on your PC, use a PC powerful enough to run the s/w instances concurrently. 
 
Feel free to clarify i= f I=E2=80=99m missing anything important. =  Very interesting!  73, Jim H  W5EST
&nbs= p;
 
-----Original Message-----
From: Rik Strobbe <rik.strobbe@kuleuven.be>
To: rsgb_lf_group <rsgb_lf_group@blacksheep.org>; rsgb_lf_group <r= sgb_lf_group@yahoogroups.co.uk>
Sent: Mon, Nov 12, 2018 4:05 pm
Subject: Re: LF: SlowJT9 v0.9.02

Hi Paul, it seems that we will have to make a choice:=20 - either the old JT9-2 and JT9-5 standard and only decoding one mode at a t= ime - or keeping the current JT9-2 and JT9-5 parameters and keep the option ope= n to decode all JT9 submodes simultanious. I tend to go for the second option, but everyone is welcome to convince me = otherwise. 73, Rik ON7YD - OR7T ________________________________________ Van: owner-rsgb_lf_group@blacksheep.org <owner-rsgb_lf_group@blacksheep.org> na= mens N1BUG <paul@n1b= ug.com> Verzonden: maandag 12 november 2018 22:43 Aan: rsgb= _lf_group@blacksheep.org; rsgb_lf_group@yahoogroups.co.uk Onderwerp: Re: LF: SlowJT9 v0.9.02 I can confirm something similar. My CPU is running around 30% (it's a VERY busy system with many apps running). When SlowJT9 invokes the decoder I see a short spike to 50%, sometimes as high as 55%. 73, Paul N1BUG On 11/12/18 4:13 PM, Rik Strobbe wrote: > I just had a look at the CPU usage of my computer: > it is wobbeling between 2% and 5% but peaks to 40% if the JT9 decoder = is invoked. > I am afraid that invoking 3 instances of the JT9 decoder at (almost) t= he same time is not a good idea. > > 73, Rik ON7YD - OR7T
------=_Part_24520_1952530547.1542062439368--