Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-dk03.r1000.mx.aol.com (Internet Inbound) with ESMTP id DE42738000083; Wed, 1 Feb 2012 05:41:55 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1RsXcV-0007uJ-Sa for rs_out_1@blacksheep.org; Wed, 01 Feb 2012 10:40:55 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1RsXcV-0007uA-FN for rsgb_lf_group@blacksheep.org; Wed, 01 Feb 2012 10:40:55 +0000 Received: from mail-iy0-f171.google.com ([209.85.210.171]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1RsXcT-0000R6-0M for rsgb_lf_group@blacksheep.org; Wed, 01 Feb 2012 10:40:55 +0000 Received: by iaeh11 with SMTP id h11so2402254iae.16 for ; Wed, 01 Feb 2012 02:40:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=oepsX5R7rJbc9/ePoo3S24+UtZ9WTARlWn+GC+j75dM=; b=hXnNEu9GhUSu785qrcBd+XOURwT+4qab8vjUFyTDDyiyTNK7FhXBnO6wGqBxvbSKyQ HqNjYGwWF/7RBMCtcb0ITwhMs2y5c5JMjClt53tcTEPiE3c8OHAS8hxaAAmuStR9A+F6 RJt4I8RQje1GJJbU9gDlR5KCTFwMDq+WAXQ8E= MIME-Version: 1.0 Received: by 10.42.165.135 with SMTP id k7mr20848440icy.32.1328092846335; Wed, 01 Feb 2012 02:40:46 -0800 (PST) Received: by 10.231.12.140 with HTTP; Wed, 1 Feb 2012 02:40:46 -0800 (PST) In-Reply-To: <4F2911FC.3020709@talktalk.net> References: <4F2911FC.3020709@talktalk.net> Date: Wed, 1 Feb 2012 10:40:46 +0000 Message-ID: From: Andy Talbot To: rsgb_lf_group@blacksheep.org X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: Re: LF: OPERA and QRS Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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-SCOLL-SCORE: 0:2:448696416:93952408 X-AOL-SCOLL-URL_COUNT: 0 X-AOL-SCOLL-AUTHENTICATION: mail_rly_antispam_dkim-m016.2 ; domain : gmail.com DKIM : pass x-aol-sid: 3039ac1db4074f2916f3167a X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Ah, now you're into the realms of soft decision decoding. How does the brain interpret a faulty QRSS symbol? Or a faulty callsign? Do you see the callsign of a well know LF operator if the gap between those two dots were filled in - or could it be a newcomer with a coincidental callsign? If you're expecting one of a few well known stations, that becomes a code-book detection - and opens up all sorts of worm cans. The error detection capabilities of the human brain are both remarkably powerful, and very prone to making gross systematic faults based on what you are expecting. I think, the comparison of time to send a given amount of data is valid. ie One QRSS transmission vs one Opera / WSPR Tx. If you want to overlay QRSS periods, then you must consider, pro-rata, slower Opera speeds to get the same time for the source data. Has anyone really come to a decision on what S/N Ratio is OK for QRSS, using either the FFT bin size or the reciprocal of the dot period as a bandwidth reference? My feeling is that a value of +3 to +6dB of the bin bandwidth, which is about 0 to 3dB above a typical dot period seems about right. And probably not coincidently, is roughly about the same S/N for audible morse it its dot-period bandwidth. Andy 'jnt On 1 February 2012 10:20, qrss wrote: > We all seem to have agreed to compare OPERA with a QRS speed which takes = the > same time to send a call sign, correct or not? > A QRS beacon can send the call continuously all day and successive period= s > are often used to establish the information. > > How about comparing like for like in the timing of Data Bits, OPERA uses > digital techniques and no doubt repeats the data in =A0the 4 minute perio= d of > OP4. In this case we would need to be comparing it with QRS1 or QRS1.025 = if > you like. > > I feed a coding session coming on. > > 73 Eddie G3ZJO > >