CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] The Insanity of Cut Numbers in Serial Number Contests

To: Pete Smith N4ZR <n4zr@contesting.com>, CQ-Contest <cq-contest@contesting.com>
Subject: Re: [CQ-Contest] The Insanity of Cut Numbers in Serial Number Contests
From: Gerry Hull <gerry@yccc.org>
Reply-to: w1ve@yccc.org
Date: Sun, 14 Dec 2014 15:43:36 -0500
List-post: <cq-contest@contesting.com">mailto:cq-contest@contesting.com>
The practice should be banned from CW contesting.  It's not cool, and
certainly does NOT increase QSO speed.  If anything, it slows things down.

73, Gerry W1VE

On Sun, Dec 14, 2014 at 9:50 AM, Pete Smith N4ZR <n4zr@contesting.com>
wrote:
>
> Please, please don'tuse cut numbers when transmitting a serial number.
> I've even heard some Es and As today - that's just absurd, and
> counterproductive..
>
> There is good information science behind this plea.  When you really need
> to get a number right, particularly with weak signals, even the most common
> cut numbers, like N and T, are more trouble than they are worth in time
> saving.  Why?  Because each full number has five elements, grouped together
> - that is consecutive dots or dashes.  Your brain can use this fact to copy
> confidently, even if QRM or QSB causes you not to hear a dit or dah,
> because of spacing *between* numbers.  If you send a cut number, you
> deprive the receiving op of this aid - he asks for a fill, and you've lost
> more time than the cut number would save you in 5 QSOs.
>
> --
>
> 73, Pete N4ZR
> Check out the Reverse Beacon Network at
> http://reversebeacon.net,
> blog at reversebeacon.blogspot.com.
> For spots, please go to your favorite
> ARC V6 or VE7CC DX cluster node.
>
> _______________________________________________
> CQ-Contest mailing list
> CQ-Contest@contesting.com
> http://lists.contesting.com/mailman/listinfo/cq-contest
>
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest

<Prev in Thread] Current Thread [Next in Thread>