In this case, K0YR did not submit a log. So the log checking used the QSOs
in the logs of the stations he worked to determine the sent exchange. While
a lot of ops logged 'T0M' (with a zero), most logged the letter 'O'. My
recordings of the contest verified that K0YR sent 'T0M' with a zero to me,
but I interpreted the zero as the letter 'O' since it was a name. Just like
I log '599' rather than '5NN' in a CW contest.
73,
Ed
-------------------------
Ed Muns - W0YK
www.w0yk.com
> -----Original Message-----
> From: rtty-bounces@contesting.com
> [mailto:rtty-bounces@contesting.com] On Behalf Of Robert Chudek - K0RC
> Sent: Friday, 29 October, 2010 00:01
> To: rtty@contesting.com
> Subject: Re: [RTTY] NA Sprint RTTY Log Check Report Analysis
>
> "Senator, I served with TØM", I know TØM. TØM is a friend of mine!"
>
> This problem actually is even more convoluted... What gets
> sent out over the air from the macro string does not
> necessarily have to match what was stored in the contest
> header (which generates the sent report for the Cabrillo file).
>
> So he might have had TØM in the macro string, but TOM in the
> contest header. If the log checking software goes by what is
> in the Cabrillo file, it won't match was everyone logged
> during the contest.
>
> Also, in a different contest, there was a station that had
> exchanged the characters opposite. His callsign was supposed
> to have a Zero, but he was transmitting an Oh on RTTY. I
> alerted him to this at some point in the contest (early on).
> The operator had fixed it by the next time I tuned across and
> printed him. So what do you think is going to happen to the
> fellows that logged "what was sent" prior to the operator
> making a change?
>
> So when an obvious error prints to your screen, and you want
> to "fix it", you will still be taking a WAG as to what will
> pass or fail during the log checking process.
>
> 73 de Bob - KØRC in MN
>
>
> On 10/28/2010 11:36 PM, Ed Muns wrote:
> > Yes, this is the crucial question. Understand that log checking is
> > going to give the nod to the sent exchange when the
> received exchange
> > differs. But ... that doesn't mean the sent exchange is what is in
> > the sender's log! So, sometimes the innocent (who truly
> logged what
> > was sent) gets dinged. Life is unfair, but trust me, far more log
> > check errors are in your favor than vice versa.
> >
> > 73,
> > Ed
> > -------------------------
> > Ed Muns - W0YK
> > www.w0yk.com
> >
> >
> >
> >> -----Original Message-----
> >> From: rtty-bounces@contesting.com
> >> [mailto:rtty-bounces@contesting.com] On Behalf Of Iain
> MacDonnell -
> >> N6ML
> >> Sent: Thursday, 28 October, 2010 21:18
> >> To: Hank Garretson
> >> Cc: David Levine; CQ Contesting Reflector; RTTY Reflector
> >> Subject: Re: [RTTY] NA Sprint RTTY Log Check Report Analysis
> >>
> >> On Fri, Oct 29, 2010 at 4:06 AM, Hank
> Garretson<w6sx@arrl.net> wrote:
> >>>
> >>> On Thu, Oct 28, 2010 at 9:02 PM, Iain MacDonnell - N6ML
> >>> <ar@dseven.org>
> >>> wrote:
> >>>
> >>>> I thought I must have manually typed it (as opposed to
> clicking on
> >>>> it), and goofed, but apparently he really was sending
> sending "T0M"
> >>>> (with a zero).
> >>>
> >>> A good reason to use a slash-zero font in your print window.
> >> But that brings up the age-old question ... do you log
> what he sent,
> >> or what you think is what he really meant to send?
> >>
> >> ~Iain / N6ML
> >> _______________________________________________
> >> 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
> >
> _______________________________________________
> 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
|