Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-dl01.r1000.mx.aol.com (Internet Inbound) with ESMTP id C683138000086; Sun, 28 Oct 2012 09:25:03 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1TSSqg-0001mg-8u for rs_out_1@blacksheep.org; Sun, 28 Oct 2012 13:24:18 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1TSSqf-0001mX-BV for rsgb_lf_group@blacksheep.org; Sun, 28 Oct 2012 13:24:17 +0000 Received: from out1.ip07ir2.opaltelecom.net ([62.24.128.243]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1TSSqc-0000OB-MM for rsgb_lf_group@blacksheep.org; Sun, 28 Oct 2012 13:24:16 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhYKAKQxjVBOk8jd/2dsb2JhbABEgkqtfpENA4EGgQmCGQUBAQ0BAQMgIQgCIQsBAQgCAQMRBAEBCjkBBBgCBgwIAg4PBAEJAQICAQEBCwSHUwMTB7EuA4lei3WBLoUvA4gkhUqJIIgthnuCbw X-IronPort-AV: E=Sophos;i="4.80,665,1344207600"; d="scan'208,217";a="51926435" Received: from host-78-147-200-221.as13285.net (HELO xphd97xgq27nyf) ([78.147.200.221]) by out1.ip07ir2.opaltelecom.net with SMTP; 28 Oct 2012 13:24:02 +0000 Message-ID: <004f01cdb50f$7eba5510$0501a8c0@xphd97xgq27nyf> From: "mal hamilton" To: "rsgb" Cc: "rsgb" Date: Sun, 28 Oct 2012 13:24:01 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Score: 3.8 (+++) 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: ----- Original Message ----- From: mal hamilton To: rsgb_lf_group@yahoogroups.co.uk Sent: Sunday, October 28, 2012 1:21 PM Subject: Re: [rsgb_lf_group] Answers to some JT9 questions Joe es Co I do like the QSO feature because at present there is a bias towards BEACON modes and in my opinion detrimental to the eveloution of the MF/LF bands A database is not a good idea either and not necessary when the QSO facility exists, where one can get a report in real time on radio. A wsjt-x database would only encourage some to Beacon and not concentrate on having a QSO in real time as is intended. [...] Content analysis details: (3.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message 3.8 AXB_XMAILER_MIMEOLE_OL_024C2 AXB_XMAILER_MIMEOLE_OL_024C2 X-Scan-Signature: 92ba6d1cfea07ba208a9963ff95bc212 Subject: LF: Fw: [rsgb_lf_group] Answers to some JT9 questions Content-Type: multipart/alternative; boundary="----=_NextPart_000_004C_01CDB50F.7E77A6C0" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.1 required=5.0 tests=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 x-aol-global-disposition: G x-aol-sid: 3039ac1d4acf508d322f102c X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. ------=_NextPart_000_004C_01CDB50F.7E77A6C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ----- Original Message -----=20 From: mal hamilton=20 To: rsgb_lf_group@yahoogroups.co.uk=20 Sent: Sunday, October 28, 2012 1:21 PM Subject: Re: [rsgb_lf_group] Answers to some JT9 questions =20 Joe es Co I do like the QSO feature because at present there is a bias towards = BEACON modes and in my opinion detrimental to the eveloution of the = MF/LF bands A database is not a good idea either and not necessary when the QSO = facility exists, where one can get a report in real time on radio. A wsjt-x database would only encourage some to Beacon and not = concentrate on having a QSO in real time as is intended. de mal/g3kev ----- Original Message -----=20 From: Joe=20 To: rsgb_lf_group@yahoogroups.co.uk=20 Sent: Sunday, October 28, 2012 1:06 PM Subject: [rsgb_lf_group] Answers to some JT9 questions =20 GM/GA all, 1. Alberto/I2PHD and others have asked whether details of the JT9 = protocol are described somewhere. At present the only full description = is the one implicitly contained in the source code, which is openly = available at http://developer.berlios.de/projects/wsjt/ . In due course = I will provide a summary document describing the source encoding, = error-control coding, interleaving and bit-ordering scheme, and = modulation details. (At this point it's possible that a few of these = things could still change, depending on user feedback.) 2. Roger/G3XBM and others asked whether a WSPRnet-like database might = be made available. Yes, this could be useful, and in principle WSPRnet = itself could accept reception reports from WSJT-X. I will give some = thought to adding such a feature, and I'll consider having WSJT-X = support standard WSPR-format messages such as "WA1ABC FN42 37". I should = mention, however, that the principal intent of JT9 and WSJT-X is to = enable 2-way QSOs at MF and LF, with very narrow bandwidths and very = weak signals. In the longer term, I do not wish that our MF/LF = frequencies will be used mostly for beacon-like transmissions. 3. WSJT-X will continue to evolve in coming weeks. The JT9 decoder is = not yet fully optimized, and other enhancements are in the works, as = well. Surely there will be bugs in the early program releases: bug = reports and requests for new features will be most welcome! -- 73, Joe, K1JT __._,_.___ Reply to sender | Reply to group | Reply via web post | Start a new = topic=20 Messages in this topic (2)=20 Recent Activity: a.. New Members 2 a.. New Photos 1=20 Visit Your Group=20 Switch to: Text-Only, Daily Digest . Unsubscribe . Terms of Use. =20 __,_._,___ ------=_NextPart_000_004C_01CDB50F.7E77A6C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
----- Original Message -----=20
From: mal = hamilton=20
Sent: Sunday, October 28, 2012 1:21 PM
Subject: Re: [rsgb_lf_group] Answers to some JT9=20 questions

  =

 
Joe es  Co
 
I do like the QSO feature because at present = there is a=20 bias towards BEACON modes and in my opinion detrimental to the = eveloution of the=20 MF/LF bands
A database is not a good idea either and not = necessary=20 when the QSO facility exists, where one can get a report in real time on = radio.
A wsjt-x database  would only encourage = some to=20 Beacon and not concentrate on having a QSO in real time as is=20 intended.
 
de mal/g3kev
 
----- Original Message -----
From: Joe =
To: rsgb_lf_group@yahoogroups= .co.uk=20
Sent: Sunday, October 28, 2012 = 1:06=20 PM
Subject: [rsgb_lf_group] = Answers to some=20 JT9 questions

 =20

GM/GA all,

1. Alberto/I2PHD and others have asked whether = details of=20 the JT9 protocol are described somewhere. At present the only full = description=20 is the one implicitly contained in the source code, which is openly = available=20 at http://developer.berl= ios.de/projects/wsjt/=20 . In due course I will provide a summary document describing the = source=20 encoding, error-control coding, interleaving and bit-ordering scheme, = and=20 modulation details. (At this point it's possible that a few of these = things=20 could still change, depending on user feedback.)

2. Roger/G3XBM = and=20 others asked whether a WSPRnet-like database might be made available. = Yes,=20 this could be useful, and in principle WSPRnet itself could accept = reception=20 reports from WSJT-X. I will give some thought to adding such a = feature, and=20 I'll consider having WSJT-X support standard WSPR-format messages such = as=20 "WA1ABC FN42 37". I should mention, however, that the principal intent = of JT9=20 and WSJT-X is to enable 2-way QSOs at MF and LF, with very narrow = bandwidths=20 and very weak signals. In the longer term, I do not wish that our = MF/LF=20 frequencies will be used mostly for beacon-like = transmissions.

3.=20 WSJT-X will continue to evolve in coming weeks. The JT9 decoder is not = yet=20 fully optimized, and other enhancements are in the works, as well. = Surely=20 there will be bugs in the early program releases: bug reports and = requests for=20 new features will be most welcome!

-- 73, Joe, = K1JT

__._,_.___
Reply=20 to sender | Reply=20 to group | Reply=20 via web post | Start=20 a new topic
Messages=20 in this topic (2) =
Recent=20 Activity:=20 New=20 Members 2=20 New=20 Photos 1 =
Visit=20 Your Group
=20
Switch to: Text-Only,=20 Daily=20 Digest =95 Unsubscribe=20 =95 Terms of = Use
.

__,_._,___
------=_NextPart_000_004C_01CDB50F.7E77A6C0--