------=_NextPart_001_0000_01C18270.A8FBB220
Content-Type: text/plain; charset="iso-8859-1"
Ed,
You DON'T get penalized for logging dupes.
If you use any of the major logging programs, they will
mark them as zero points.
Its always easier to log a dupe than to go through the
explanation.
73,
Larry K4AB
----- Original Message -----
From: K4SB
Sent: Tuesday, December 11, 2001 16:44
To: secc@contesting.com
Subject: Re: [SECC] ARRL 10 M test and Croatian CW DX Contest
John Laney wrote:
> Therefore, my first suggestion for those of us who will be working the
> ARRL 10M contest on CW this weekend is to give a serial number in
> addition to state/province to anyone who specifically asks for one
> during the period of overlap of the Croatian contest. I think all
> contest software programs give a running QSO number readout even when
> serial numbers are not being used. So, I plan (as guest op at W4AN) to
> give out that number from the computer to anyone who asks during that
> period.
> My other suggestion is that we be even more willing than usual to work
> and log duplicate contacts after the end of the Croatian contest at 14Z
> on Sunday. The arguments have often been stated for working and logging
> all dupes anyway and I won't repeat these here, but there may be
> operators, particularly from Europe, who will give out some QSOs in the
> ARRL 10M contest and give new serial numbers, who, if they send in a
> log, will not include those contacts they made on 10 M while in the
> Croatian contest. So, log these guys again and your log should match up
> and you should get credit for the second QSO if the first is not
> reported.
> 73,
> John, K4BAI/8P9HT/8P9Z.
I agree with John in giving out the serial numbers if asked, but I
will not log such a contact.
If I get called later by the same person, operating the 10 meter
contest, that's OK. But I'm not willing to put up with getting
penalized for dupes. Regretfully, scheduling has made this a mess. My
log is going to show a dupe, and nothing good can come from that,
except to perhaps edit out the first contest.
Or, log all the contacts, but refuse the dupes later. There is no
requirement that logs be submitted by anyone, and a cross check of
logs submitted will confirm a station who works both contests.
Or is there something I'm missing here?
73
Ed
--
SECC on the Web: http://secc.contesting.com/
Submissions: secc@contesting.com
Administrative requests: secc-REQUEST@contesting.com
Problems: owner-secc@contesting.com
------=_NextPart_001_0000_01C18270.A8FBB220
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<HTML><BODY STYLE=3D"font:10pt verdana; border:none;"><DIV>Ed,</DIV> <DIV=
> </DIV> <DIV>You DON'T get penalized for logging dupes.</DIV> =
<DIV> </DIV> <DIV>If you use any of the major logging programs, they=
will</DIV> <DIV>mark them as zero points.</DIV> <DIV> </DIV> <DIV>I=
ts always easier to log a dupe than to go through the </DIV> <DIV>ex=
planation.</DIV> <DIV> </DIV> <DIV>73,</DIV> <DIV>Larry K4AB</DIV> <=
DIV> </DIV> <DIV> </DIV> <DIV> </DIV> <BLOCKQUOTE style=3D=
"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0=
00000 2px solid; MARGIN-RIGHT: 0px"> <DIV style=3D"FONT: 10pt Arial">----=
- Original Message -----</DIV> <DIV style=3D"BACKGROUND: #e4e4e4; FONT: 1=
0pt Arial; COLOR: black"><B>From:</B> K4SB</DIV> <DIV style=3D"FONT: 10pt=
Arial"><B>Sent:</B> Tuesday, December 11, 2001 16:44</DIV> <DIV style=3D=
"FONT: 10pt Arial"><B>To:</B> secc@contesting.com</DIV> <DIV style=3D"FON=
T: 10pt Arial"><B>Subject:</B> Re: [SECC] ARRL 10 M test and Croatian CW =
DX Contest</DIV> <DIV> </DIV>John Laney wrote:<BR><BR>> Therefore=
, my first suggestion for those of us who will be working the<BR>> ARR=
L 10M contest on CW this weekend is to give a serial number in<BR>> ad=
dition to state/province to anyone who specifically asks for one<BR>> =
during the period of overlap of the Croatian contest. I think all<B=
R>> contest software programs give a running QSO number readout even w=
hen<BR>> serial numbers are not being used. So, I plan (as guest=
op at W4AN) to<BR>> give out that number from the computer to anyone =
who asks during that<BR>> period.<BR><BR>> My other suggestion is t=
hat we be even more willing than usual to work<BR>> and log duplicate =
contacts after the end of the Croatian contest at 14Z<BR>> on Sunday.&=
nbsp; The arguments have often been stated for working and logging<BR>>=
; all dupes anyway and I won't repeat these here, but there may be<BR>>=
; operators, particularly from Europe, who will give out some QSOs in the=
<BR>> ARRL 10M contest and give new serial numbers, who, if they send =
in a<BR>> log, will not include those contacts they made on 10 M while=
in the<BR>> Croatian contest. So, log these guys again and your=
log should match up<BR>> and you should get credit for the second QSO=
if the first is not<BR>> reported.<BR>> 73,<BR>> John, K4BAI/8P=
9HT/8P9Z.<BR><BR>I agree with John in giving out the serial numbers if as=
ked, but I<BR>will not log such a contact.<BR>If I get called later by th=
e same person, operating the 10 meter<BR>contest, that's OK. But I'm not =
willing to put up with getting<BR>penalized for dupes. Regretfully, sched=
uling has made this a mess. My<BR>log is going to show a dupe, and nothin=
g good can come from that,<BR>except to perhaps edit out the first contes=
t.<BR><BR>Or, log all the contacts, but refuse the dupes later. There is =
no<BR>requirement that logs be submitted by anyone, and a cross check of<=
BR>logs submitted will confirm a station who works both contests.<BR><BR>=
Or is there something I'm missing here?<BR><BR>73<BR>Ed<BR><BR>--<BR>SECC=
on the Web: http:/=
/secc.contesting.com/<BR>Submissions: =
secc@contesting.com<BR>Adminis=
trative requests: secc-REQUEST@contesting.com<BR>Problems: &nb=
sp; &nbs=
p; owner-secc@contesting.com<BR><BR></BLOCKQUOTE></BODY></HTM=
L>
------=_NextPart_001_0000_01C18270.A8FBB220--
--
SECC on the Web: http://secc.contesting.com/
Submissions: secc@contesting.com
Administrative requests: secc-REQUEST@contesting.com
Problems: owner-secc@contesting.com
|