CQ-Contest
[Top] [All Lists]

Re: [CQ-Contest] not logging dupes is wrong

To: <cq-contest@contesting.com>
Subject: Re: [CQ-Contest] not logging dupes is wrong
From: "Ron Notarius W3WN" <wn3vaw@verizon.net>
Reply-to: wn3vaw@verizon.net
Date: Wed, 10 Dec 2008 17:08:19 -0500
List-post: <cq-contest@contesting.com">mailto:cq-contest@contesting.com>
Or W3WH, W3WC, and W3WN (as happened last weekend), let alone W3WN and N2WN
and other call combinations that are VERY similar.

Work now, dupe sheet later!

73

-----Original Message-----
From: cq-contest-bounces@contesting.com
[mailto:cq-contest-bounces@contesting.com]On Behalf Of Julius Fazekas
Sent: Wednesday, December 10, 2008 2:05 PM
To: cq-contest@contesting.com; kr2q@optimum.net
Subject: Re: [CQ-Contest] not logging dupes is wrong


I'll second that!

Particularly when both N2WM and N2WK are playing in the same event. Several
times during ARRL 160 two of us were in the same place at the same time this
past weekend.

At least once, we had back to back QSOs with one station in a very nasty
pileup. Hopefully he didn't start scratchy his head thinking one was an
"insurance" QSO and the other was a dupe.

I log every "dupe", unless the contest has a penalty for dupes, then I might
hesitate.

I find "QSO B4" and the ensuing confusion breaks my running rhythm, and I
sure don't need any help in that area ;o)

73,
Julius

Julius Fazekas
N2WN

Tennessee Contest Group
TnQP http://www.tnqp.org/

Elecraft K2/100 #3311
Elecraft K2/100 #4455
Elecraft K3/100 #366


--- On Wed, 12/10/08, kr2q@optimum.net <kr2q@optimum.net> wrote:

> From: kr2q@optimum.net <kr2q@optimum.net>
> Subject: [CQ-Contest] not logging dupes is wrong
> To: cq-contest@contesting.com
> Date: Wednesday, December 10, 2008, 10:33 AM
> Disclaimer:  these are my thoughts and should not be
> construed to represent any opinion
> or "ruling" by any contest committee with which I
> am associated.
>
> Jukka said that he does not log dupes and feels good about
> it because he set up an
> "agreement" with the other guy that he will
> remove the "first" dupe from his log.
>
> I think that this is wrong in most cases.
>
> If you log K2AA at 0800z and then K2AA calls you again at
> (say) 1000z, you say that you
> will log him again at 1000z but only after telling him that
> you are removing K2AA from your
> log at 0800z.  Well, what if the "first" QSO with
> K2AA was actually with N2AA or K3AA or
> K2AAK, etc?  YOU made the error in YOUR log, but by
> removing the "first dupe," you are
> penalizing the other guy (who will now get a NIL).
>
> If the other guy checks his log at 0800 and finds OH7LI,
> then you can agree.  But what if
> he says, "I don't have anytthing close to your
> call in my log at that time" or if he says,
> "I first turned on the radio just 15 minutes
> ago?"  Or what if he doesn't say anything?
>
> Removing QSO's from logs is potentially dangerous and I
> would not do it.  I do think that
> it is "nice" and "courteous" to tell
> the guy that he is a dupe and give him the time so that
> he can check his log to see if he copied your call wrong.
> But if he does and says, "no dupe,"
> then you have to work him "again" and you should
> not remove the 1st QSO, even if it
> shows "dupe" in your log.
>
> de Doug KR2Q
> _______________________________________________
> 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

_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest

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