CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] Cut numbers -- a different take

To: <cq-contest@contesting.com>
Subject: Re: [CQ-Contest] Cut numbers -- a different take
From: <w5gn@mxg.com>
Date: Mon, 15 Dec 2014 10:41:48 -0600
List-post: <cq-contest@contesting.com">mailto:cq-contest@contesting.com>
At least for the WPX CW contest, N1MM and N1MM+ both decode the cut
number for the serial, so you can type exactly what you hear and
see the transcribed numbers.  I was surprised to find the CQ WW does 
not decode cut numbers for the zone, but I guess that was a conscious
choice since the zone will normally be populated from the call.
I'm not sure what other contests are similarly decoded.

Of course, for ARRL 10, or any contest where the exchange can 
include either serial numbers or text (state/oblast/etc), 
cut numbers can't be safely decoded.

And I'll always send 5NN NN from EI/W5GN for the ARRL CW and others
contests that send power; not only because it sounds nice, and seems
to be very well understood - I can't recall every needing to fill
with actual numbers - but also because "99" is the "nick-number" of 
my bride, KA5PQD, plus, her Grandmother signed her letters from Texas
in the 1880's with "99 - Peace and Love", which could go along with
73 and 88 on the air!

99,
and 
MERRILLY CHRISTMAS,
Barry and Judy Merrill

-----Original Message-----
From: CQ-Contest [mailto:cq-contest-bounces@contesting.com] On Behalf Of Art 
Boyars
Sent: Monday, December 15, 2014 8:40 AM
To: cq-contest@contesting.com
Subject: [CQ-Contest] Cut numbers -- a different take

Well, yes, they are annoying -- especially if I am running (hah!).  But...

1.  If I am S&P, I usually hear one report before my QSO, so I am ready for cut 
numbers.  (That's for actual spot-free S&P; might not apply to skill-free 
point-and-click.)

2.  I think we will eventually learn to copy cut numbers, just like we learned 
to love 5NN -- and even ENN -- even at QRQQQ.  And I think all the big guns 
here in Zone 5 are sending 5NN 5, not even T5 or o5, and certainly not 05.  Who 
am I to complain if some European wants to send A4 or A5, or if some Brazilian 
wants to use AA?  It all saves time, and, as the noted electrical experimenter 
Ben Franklin (3BF, in the pre-license days) said, "Time is QSOs."

3.  "Ah," you say, "A4, etc., are zone numbers.  We already know those.
We're complaining about Ser No's."  Yes, and you have made my point about CQ WW 
-- no copying skill req'd; but that's a different topic.  But it does lead me 
to...

4.  ...Point 2, again.  The user has to be smart -- what can the copying 
station handle -- in this particular QSO?  It's just like wise use of code 
speed (or phonetics).  Right now, I think most of the regular contesters can 
decode N=9 and T=0 in a QSO NR.  I think E=5 and A=1 will be next.  I don't 
know if we'll ever get beyond that.

In the end, Darwin (preferring the soft sciences, he was never QRV) will rule, 
and what works best will survive.  Who want's to go back to .....
----. ----. ----- .....? Or hand keys? Or paper logs?  The innovators will 
decide what improves their desired results -- whether that be max rates, max 
points, or max fun.

(Regarding leading zeros: Those of us who start the 'Test late and are sending 
NR<10 when everybody else is >200 find that it helps to send the leading zero 
until you have at least two digits, sometimes three.  The copying op often 
cannot believe that NR 5 is right, and asks for a repeat.
OTOH, many lower-tier op's do, indeed, seem to use it too long, but that might 
be based on their own experience.)

And if you are sitting there grumping while everybody else is increasing their 
rate by 1% or 2%, I sincerely hope you are having fun.

73, Art K3KU
"Tune for maximum fun"
_______________________________________________
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>