Ahhh...duh. I get it. You know sometimes even the simple solution is not
obvious. I still have to give this one some thought. I guess CQ/###
would still have to show up if you were alone there. The way it works
right now to add this feature I think all I need to add is the marker
which would track LASTCQFREQUENCY and a warning when a conflict occurs.
Gary Ferdinand W2CS wrote:
>
> But that's not what Guy or I was talking about, Ron.
>
> The marker would be the indicator of where you are CQing, not the indicator
> of "packet spot conflict." Thus, the true spot would exist with a ">" or
> something next to it to indicate both the spot and the CQ. If no spot close
> to CQ freq, then display what is displayed today.
>
> 73/Gary W2CS
>
> > -----Original Message-----
> > From: trlog-admin@contesting.com [mailto:trlog-admin@contesting.com]On
> > Behalf Of Ron D. Rossi
> > Sent: Tuesday, June 04, 2002 11:48 AM
> > To: Gary Ferdinand W2CS
> > Cc: TRLOG
> > Subject: Re: [TRLog] Arghh. Halp. Need something entirely new from TR.
> >
> >
> > >>>"Gary Ferdinand W2CS" said:
> > >
> > > I think Guy's idea has merit. Don't overlay what would
> > otherwise be going
> > > into the bandmap by a CQ entry, but rather add a special
> > character to denote
> > > CQ frequency.
> >
> > It does have merit. Providing a warning would not be too
> > difficult. Having a
> > marker show up next to the CQ/### would be problematic. What
> > makes it go away?
> > Time? Yet another keystroke to remember? Something else? I would be very
> > inclined to leave this one at the warning level.
> >
> > Before we get on a philosophical debate on cluster use and
> > cheater detection
> > can was focus on features?? Bring that up on CQ-Contest :)
> >
> > --
> > 73 es God Bless de KK1L...ron rossi(kk1l@arrl.net) <><
> > QTH: Jericho, Vermont
> > My page: http://www.qsl.net/kk1l
> >
> > >
> > > > -----Original Message-----
> > > > From: trlog-admin@contesting.com [mailto:trlog-admin@contesting.com]On
> > > > Behalf Of Tree N6TR
> > > > Sent: Sunday, June 02, 2002 4:47 PM
> > > > To: k2av@contesting.com; trlog@contesting.com
> > > > Cc: n4af@contesting.com
> > > > Subject: Re: [TRLog] Arghh. Halp. Need something entirely new from TR.
> > > >
> > > >
> > > > > After reviewing UBN's from the CQWW, I can see that bad spots are
> > > > > costing me points after the contest is over, e.g. NIL's that the log
> > > > > checker can't relate to the real station.
> > > > >
> > > > > For example...
> > > > >
> > > > > NY4A is calling CQ on 40 on 7017. Someone in JA land spots KW4M at
> > > > > 7017.
> > > >
> > > > I don't know. If a call is close to yours, then it won't count as
> > > > a NIL for you. I actually feel that having some noise on the spots
> > > > is a good thing - makes people either have errors in their log, or
> > > > make them take the time to hear the call right. If JA1XYZ, JE2ABC,
> > > > JA5QQQ and JA3DEF are claiming single operator, it is easy to busy
> > > > them for using packet if a few instances like this occur.
> > > >
> > > > > If there was a spot showing me as KQ4A 7.017.3, I would see
> > it and add
> > > > > a lot of extra DE NY4A until it got corrected.
> > > >
> > > > Wow.
> > > >
> > > > All of this makes me feel even more that packet is poison.
> > > >
> > > > Tree
> > > > _______________________________________________
> > > > TRLog mailing list
> > > > TRLog@contesting.com
> > > > http://lists.contesting.com/mailman/listinfo/trlog
> > > >
> > >
> > > _______________________________________________
> > > TRLog mailing list
> > > TRLog@contesting.com
> > > http://lists.contesting.com/mailman/listinfo/trlog
> > >
> >
> >
> >
> > _______________________________________________
> > TRLog mailing list
> > TRLog@contesting.com
> > http://lists.contesting.com/mailman/listinfo/trlog
> >
>
> _______________________________________________
> TRLog mailing list
> TRLog@contesting.com
> http://lists.contesting.com/mailman/listinfo/trlog
--
73 es God Bless de KK1L...ron (kk1l@arrl.net) <><
QTH: Jericho, Vermont
My page: http://www.qsl.net/kk1l
|