Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CQ\-Contest\]\s+To\s+cut\s+or\s+not\s+to\s+cut\?\s*$/: 23 ]

Total 23 documents matching your query.

1. [CQ-Contest] To cut or not to cut? (score: 1)
Author: Pete Smith N4ZR <n4zr@contesting.com>
Date: Thu, 31 May 2012 08:23:15 -0400
There's nothing like a CW serial number contest to get you re-thinking about the use of cut numbers. For situations where first-time intelligibility is important, I think use of cut numbers probably
/archives//html/CQ-Contest/2012-05/msg00225.html (7,790 bytes)

2. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: Alan Dewey <aldewey@aol.com>
Date: Thu, 31 May 2012 09:05:23 -0400 (EDT)
Pete; I agree with you. The cut numbers as part of the serial numbers drove me crazy this weekend. To receive an "A" in the middle of a 4 digit number may save three dashes but I think that time is m
/archives//html/CQ-Contest/2012-05/msg00226.html (9,775 bytes)

3. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: "Bob Naumann" <W5OV@W5OV.COM>
Date: Thu, 31 May 2012 08:09:10 -0500
Pete, I think that in serial numbers, the only digit that should be cut is a leading zero. For example, when I send 020 (twenty) I would send T 2 0 - not T 2 T. I think doing anything else runs the r
/archives//html/CQ-Contest/2012-05/msg00227.html (9,906 bytes)

4. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: Doug Smith <dougw9wi@gmail.com>
Date: Thu, 31 May 2012 08:33:24 -0500
Agreed fully. Obviously I copy fairly well, both letters & numbers :) They say the key to getting past the 12wpm hump is learning to copy letters as a single sound -- to hear ..- and immediately thin
/archives//html/CQ-Contest/2012-05/msg00228.html (9,157 bytes)

5. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: "Robert Brandon" <rb@austin.rr.com>
Date: Thu, 31 May 2012 08:54:46 -0500
I've copied quite a few serial numbers in my time, but I'm still startled when I get a cut number. I can usually decode it, but it takes me an extra beat or two to do so. And guess what -- that erase
/archives//html/CQ-Contest/2012-05/msg00233.html (10,089 bytes)

6. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: "VE5ZX" <ve5zx@hotmail.com>
Date: Thu, 31 May 2012 08:20:31 -0600
During the WPX CW while condx here were good on 15m they were not great. Many low power EU signals were marginal. I noticed that I asked for more repeats from EU stations that were using cut number t
/archives//html/CQ-Contest/2012-05/msg00236.html (8,080 bytes)

7. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: Hank Greeb <n8xx@arrl.org>
Date: Thu, 31 May 2012 10:49:25 -0400
Pete: You have great points. I agree wholeheartedly. I'm probably branded as a "stick in the mud," but: I generally ask "NR?" repetitively if a fellow sends cut numbers for his number. But, last week
/archives//html/CQ-Contest/2012-05/msg00237.html (10,574 bytes)

8. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: Mirko S57AD <miroslav.sibilja@amis.net>
Date: Thu, 31 May 2012 17:00:26 +0200
It has been prevalent in former YU local contests held on 80m (usualy 2 hour events where every second counted), in pre-computer ages. Say, one of buddies heard me and tailended with short AO, and I
/archives//html/CQ-Contest/2012-05/msg00238.html (8,950 bytes)

9. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: Ktfrog007@aol.com
Date: Thu, 31 May 2012 13:00:30 -0400 (EDT)
The most egregious misuse of cut numbers I've ever heard was by 4T100MP in 2011. Some ops there sent 4T1TTMP as their call sign. No kidding. I always find cut numbers to be a problem. Europeans use t
/archives//html/CQ-Contest/2012-05/msg00244.html (9,166 bytes)

10. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: Richard Thorne <rmthorne@att.net>
Date: Thu, 31 May 2012 13:01:48 -0400
I'm not a fan of cut numbers. I like using T for leading zeros in the serial number. After the first hour or so in the beginning of a contest everyone is in the grove. After serial number 99 I no lon
/archives//html/CQ-Contest/2012-05/msg00247.html (10,796 bytes)

11. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: Georgek5kg@aol.com
Date: Thu, 31 May 2012 13:40:12 -0400 (EDT)
Opinion, yes definitely. Cut numbers other than T, A or N are too confusing in my opinion. Some European stations use cuts, and I sure wish they would not! I generally always have to ask for repeats
/archives//html/CQ-Contest/2012-05/msg00248.html (10,007 bytes)

12. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: W0MU Mike Fatchett <w0mu@w0mu.com>
Date: Thu, 31 May 2012 12:06:03 -0600
Cut numbers in the serial number threw me constantly. Maybe the very good ops deal with it but I am geared up for number not letters! Most of the cut numbers are from EU and JA. Most people lost what
/archives//html/CQ-Contest/2012-05/msg00250.html (10,796 bytes)

13. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: John <af5cc@fidmail.com>
Date: Thu, 31 May 2012 13:15:08 -0500
I do find that sending the leading zeros as T seems to help most ops, as they seem to be expecting a three digit number AF5CC or is that 1F5CC? _______________________________________________ CQ-Cont
/archives//html/CQ-Contest/2012-05/msg00251.html (11,664 bytes)

14. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: F5vjc <foxfive.vjc@gmail.com>
Date: Thu, 31 May 2012 20:19:42 +0200
So, everyone agrees cut numbers apart from T and N are more bother than they are worth. Why doesn't the penny drop with all contest Ops ? Agn, Agn... 73, Deni F5VJC __________________________________
/archives//html/CQ-Contest/2012-05/msg00252.html (11,712 bytes)

15. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: Mats Strandberg <sm6lrr@gmail.com>
Date: Thu, 31 May 2012 23:02:00 +0400
ENN guys are primitive and next time I think I shall avoid them when I S&P Time to remind too inventive guys that Morse Code has some kind of basic rules and limitations... 599001 can be 5NN TT1....
/archives//html/CQ-Contest/2012-05/msg00256.html (11,586 bytes)

16. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: Tom Osborne <w7why@frontier.com>
Date: Thu, 31 May 2012 12:04:35 -0700
Hi Kermit It has always puzzled me why some stations use a big, long call like that, and then use cut numbers for the exchange :-) 73 Tom W7WHY _______________________________________________ CQ-Cont
/archives//html/CQ-Contest/2012-05/msg00257.html (9,541 bytes)

17. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: "Michael D. Adams" <mda@ab1od.org>
Date: Thu, 31 May 2012 15:08:33 -0400
In WPX, the only cut numbers I used were leading T's. However, there were times that I felt like not using cut numbers was excessive / discourteous to the other station -- the "when in Rome..." pheno
/archives//html/CQ-Contest/2012-05/msg00258.html (12,090 bytes)

18. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: Zack Widup <w9sz.zack@gmail.com>
Date: Thu, 31 May 2012 14:50:59 -0500
An anecdote - In my first really semi-serious effort as a little pistol in ARRL DX CW (n 1993) I had been inactive in ham radio for quite a number of years and honestly hadn't encountered cut numbers
/archives//html/CQ-Contest/2012-05/msg00261.html (12,707 bytes)

19. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: Ktfrog007@aol.com
Date: Thu, 31 May 2012 19:24:51 -0400 (EDT)
Well, you gotta save somewhere. As far as using cut numbers, the rule I was taught was to use them only in unambiguous situations, where only numbers could possibly be used. This makes them OK for se
/archives//html/CQ-Contest/2012-05/msg00265.html (8,461 bytes)

20. Re: [CQ-Contest] To cut or not to cut? (score: 1)
Author: W0MU Mike Fatchett <w0mu@w0mu.com>
Date: Thu, 31 May 2012 18:32:15 -0600
If you want to send enn for the signal report great. Actually I could care less what is sent there. Someday it will probably be e e e. If you send cut numbers to me, you can probably count on a fill.
/archives//html/CQ-Contest/2012-05/msg00266.html (10,786 bytes)


This search system is powered by Namazu