RTTY
[Top] [All Lists]

Re: [RTTY] Good Observations in RTTY RU

To: "Alex" <kr1st@amsat.org>, "'Steve **KT0DX**'" <kt0dx@comcast.net>, <rtty@contesting.com>
Subject: Re: [RTTY] Good Observations in RTTY RU
From: "Robert Chudek - K0RC" <k0rc@pclink.com>
Reply-to: Robert Chudek - K0RC <k0rc@pclink.com>
Date: Tue, 6 Jan 2009 11:07:35 -0600
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
Alex suggested:
> Really, just work the duplicate. And if you really feel
> you have to massage your log, drop the first time you
> logged a station on that band and all is fine.


No, sorry, all will not be fine! You should NEVER remove a log entry. Here's 
why this suggestion will cause a problem...

Let's say KR1ST is cqing and has a good pileup going. He prints KØRC and 
logs my callsign on Saturday. Unknown to him, I'm not on the air until 
Sunday when I call him. He see's that I'm a DUPE. The correct action is to 
simply rework me and don't challenge the DUPE.

Now let's say the contest is over and someone follows the suggestion to 
remove the first KØRC contact from the log...

This will create a problem! In reality, KR1ST actually worked Chuck, KØRF 
but due to all the QRM, it decoded into my callsign instead. If KR1ST 
removes that first contact, KØRF is going to take a penalty of "Not in 
(KR1ST) log" when the logs are processed.

If the first KØRC is NOT removed, then KØRF will get credit for the contact. 
KR1ST will not get credit for that contact (the first KØRC is a busted 
call).

As you can see, there is risk involved when going back and messing with a 
contest log. It's one thing to fix an obvious mistake like logging KØRCRC 
instead of KØRC, but it's a different story if you start changing or 
removing legitimate callsigns. You might be creating penalties for the other 
operators in the contest!

73 de Bob - KØRC in MN


----- Original Message ----- 
From: "Alex" <kr1st@amsat.org>
To: "'Steve **KT0DX**'" <kt0dx@comcast.net>; <rtty@contesting.com>
Sent: Monday, January 05, 2009 7:33 PM
Subject: Re: [RTTY] Good Observations in RTTY RU


> Steve **KT0DX** wrote:
>
>> On others the trash was right next to the last letter in the call and I
>> would get something like KH6JM KH6JMGdEdl.  Now which call was correct
>> the KH6JM or the KH6JMG.  If both are in the master call data base they
>> are going to both show up as good.
>
> The extra space is a good suggestion. I add the extra space to my call, 
> too,
> although quite a number of folks logged me as KR1S instead of KR1ST. Both
> calls are in the master call database and both are valid callsigns. 
> Reliance
> on the call master database can be dangerous at times.
>
>> This would be a good time saver over the course of the
>> contest.
>
> Another good time saver is to log duplicates instead of trying to tell the
> other station it's a dupe contact.
>
> You don't get penalized for dupes in your log for most contests as far as 
> I
> know. And obviously if I'd be a dupe to you, then you are not in my log, 
> so
> the first contact in your log is invalid anyway. It really gets bad when
> folks not only say it's a dupe, but even tell you the date and time of the
> first contact. What are they trying to prove? Or do they really think I'm
> going to manually enter a contact in the midst of a contest? Heck no, I
> rather skip you and work someone else. (can you tell it's one of my pet
> peeves in contesting? :) ). The funny thing is that you see seasoned
> contesters doing this "you're a dupe" thing. Really, just work the
> duplicate. And if you really feel you have to massage your log, drop the
> first time you logged a station on that band and all is fine.
>
> Good suggestions, Steve.
>
> 73,
> --Alex KR1ST
> http://www.kr1st.com
> http://www.airlinkexpress.org
>
>
>
> _______________________________________________
> RTTY mailing list
> RTTY@contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
> 

_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

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