To: | [email protected] |
---|---|
Subject: | Re: LF: Fw: Covert Char per Min to Words per Min ? |
From: | Andy Talbot <[email protected]> |
Date: | Fri, 20 Aug 2010 21:19:40 +0100 |
Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=c8Hl9NfO0R/cCqdaORZTXcQbr5sI7wNSmie8+vroF0g=; b=M4l4CSRHBvjbGnrT3I9OkZ9GLjO2pf6Qs1zopRWV5i60QPJtp/5ddyeEDXPnnOIOyJ n1HmVo0/Rq7Ipd2JEoE26FLLerKAIrYQGJJ29FmkVKc04lRhg73LFiQUjoJHoVZ1xzBJ mEKMkRJ8IMCFMOqto4c5gUfEZyhqB5jWv8gUI= |
Domainkey-signature: | a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=U1+cnkMPLSAILKGCKzJyet0QTxmdSWiM+tuJwT8hozZT9Bt/eNj1cZr4Ph/wQHn1dn MvjxleilybqlAPRklJ6Hqy3sd2xdDpZHMePID1zzgbU+D5obRntRV2wIy/XqAW4Wo6/C +LpOzr10xlt6Jj3XGPeK1hxMyJ7KeWdtmu930= |
Domainkey-status: | good (testing) |
In-reply-to: | <A7CFEAFBFDF34B06BB1219A07B811874@AGB> |
References: | <A7CFEAFBFDF34B06BB1219A07B811874@AGB> |
Reply-to: | [email protected] |
Sender: | [email protected] |
Normally you can assume 5 characters per word, that factor is is reasonably constant - the average word is 5 letters
The number of bits per character is more complicated to quantify. In CMSK for example, where the character length varies based on the probability of the letter's occurence in typical messages, the effective number of bits per character is less than for ASCII encoding, say around 5 or 6 bits per character average for the whole alphabet. With a heavily source encoded scheme - like WSJT with a small alphabet to start with, - it is possible to get right down to less than 5 signalling bits per character. But particularly in Varicoded data, there are more bits added in framing and synchronisation, so call it total of 7 bits per character complete
If you then take note of the error correction overhead, which doubles up the number of bits sent for each message, and add in another 17% of synchronisation bits , you end up with a net rate of something like 17 bits per character for the error corrected message. So, CMSK8 (8 bits per second) equates to about 8/17 characters per second, or 30 characters per minute, or 6 words per rminute - which is rather faster than the 3.75 rate quoted in the table - so I've missed something somewhere?
CMSK8 is 8 times faster than CMSK1, but its not the whole story. If the link is too weak to support the faster speed, but the slow one gets through - which is then faster ? CMSK8 that may work tomorrow, if you're lucky, eventually; or will work CMSK1 now?
On 20 August 2010 19:09, Graham <[email protected]> wrote:
|
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | LF: Re: Re: qso g3kev, rn3agc |
---|---|
Next by Date: | LF: G3KEV, Vladimir Shuplyakov |
Previous by Thread: | Re: LF: Fw: Covert Char per Min to Words per Min ?, Gary - G4WGT |
Next by Thread: | LF: LF:137.7, Vladimir Shuplyakov |
Indexes: | [Date] [Thread] [Top] [All Lists] |