CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] List of WRTC stations / Results /Overspotting and futur

To: CQ Contest <cq-contest@contesting.com>
Subject: Re: [CQ-Contest] List of WRTC stations / Results /Overspotting and future WRTCs
From: "Kenneth E. Harker" <kenharker@kenharker.com>
Date: Fri, 16 Jul 2010 07:16:52 -0700
List-post: <cq-contest@contesting.com">mailto:cq-contest@contesting.com>
     There's a fourth possibility.  At the top of each clock hour (or maybe 
every other clock hour), every WRTC team must change call signs (which of 
course are pre-determined by random draw and given to the ops by the referee 
at each change time).  If you threw in a mandatory QSY at the same time, it 
would limit the amount of time that any identified station could benefit from 
the cheating.  It would also limit the effect of good versus not-quite-as-good
call signs.   The down side is that getting an adequate supply of call signs 
to use might be hard/impossible.

On Thu, Jul 15, 2010 at 06:51:42PM -0700, Martin Monsalvo, LU5DX wrote:
 
> The main problem behind over-spotting, cheerleading via any means, is in fact
> that teams do not remain anonymous throughout the contest.
>  
> To me there are three possible solutions to this:
>  
> 1)      Make WRTC a CW only contest with the same set of pre-programmed 
> messages 
> for everyone (though I’m mostly a CW lid) I wouldn’t like a CW only WRTC.
> 2)      Make WRTC a sprint type competition (I really like this one). It 
> would 
> make operation so much more fun, even with two stations being able to 
> transmit, 
> like in 2010 WRTC.
> 3)      Provide Teams a set of pre-recorded voice messages, for exchanges, 
> CQs, 
> TUs, QRZs, Repeats, and for individual letters, plus the same set of standard 
> messages for CW.
-- 
Kenneth E. Harker WM5R
kenharker@kenharker.com
http://www.kenharker.com/

_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
<Prev in Thread] Current Thread [Next in Thread>