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 9678E3800008E; Sun, 28 Oct 2012 09:16:44 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1TSSiV-0001fG-Qi for rs_out_1@blacksheep.org; Sun, 28 Oct 2012 13:15:51 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1TSSiV-0001f7-Bt for rsgb_lf_group@blacksheep.org; Sun, 28 Oct 2012 13:15:51 +0000 Received: from ppa03.princeton.edu ([128.112.128.214]) by relay1.thorcom.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1TSSiP-0000LH-Bl for rsgb_lf_group@blacksheep.org; Sun, 28 Oct 2012 13:15:50 +0000 Received: from csgsmtp201l.Princeton.EDU (csgsmtp201l.Princeton.EDU [128.112.134.60]) by ppa03.princeton.edu (8.14.4/8.14.4) with ESMTP id q9SDFh1k002850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 28 Oct 2012 09:15:43 -0400 Received: from [192.168.1.3] (pool-173-61-149-45.cmdnnj.fios.verizon.net [173.61.149.45]) (authenticated bits=0) by csgsmtp201l.Princeton.EDU (8.13.8/8.12.9) with ESMTP id q9SDFhjm013184 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 28 Oct 2012 09:15:43 -0400 Message-ID: <508D2FFF.40700@princeton.edu> Date: Sun, 28 Oct 2012 09:15:43 -0400 From: Joe Taylor User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:6.0) Gecko/20110812 Thunderbird/6.0 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.431,0.0.0000 definitions=2012-10-28_04:2012-10-26,2012-10-28,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=quarantine_notspam policy=quarantine score=0 spamscore=0 ipscore=0 suspectscore=1 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1203120001 definitions=main-1210280111 X-Spam-Score: -2.9 (--) 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: 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.) [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, medium trust [128.112.128.214 listed in list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Scan-Signature: 0a4643e586472c13187d293ec5d096c2 Subject: LF: Answers to some JT9 questions Content-Type: text/plain; charset=ISO-8859-1; 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 x-aol-global-disposition: G x-aol-sid: 3039ac1d4acf508d303c5842 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none 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