TRLog
[Top] [All Lists]

Re: [Trlog] SS Bandmap dupe bug

To: TRLog Reflector <trlog@contesting.com>
Subject: Re: [Trlog] SS Bandmap dupe bug
From: "Tim Totten, N4GN" <n4gn@n4gn.com>
Date: Fri, 7 Nov 2003 16:45:37 -0500 (EST)
List-post: <mailto:trlog@contesting.com>
On Fri, 7 Nov 2003, Udo DL2ZAV wrote:

> > During SS I noticed several times that I would receive a packet spot
> > for a callsign on another band and then would be called by that
> > station during a run.  The callsign would remain in the Bandmap on the
> > other band and when I did an S&P run on that band NEXTBANDMAP would
> > take me to that frequency.
>
> Why not? He could still be there when he is M/M or SO2R. TR
> cannot know that.

Yes, but I think the intent of the original posting was that for contests
like SS (work each station ONCE, not once per band), TR should put an
asterisk next to the call in a bandmap once it's worked.

Example:

- I'm using packet (M or U category in SS).
- I'm running on 15.
- K7RAT is spotted on 20.
- I haven't worked K7RAT yet (I'm a lid), so it shows up with no asterisk.
- K7RAT finds me on the second radio and works me (he's not a lid).
- It would be nice if the spot on 20 was updated with an asterisk (and all
that goes with that, like being in the queue for NEXT BANDMAP).

I'd call this very low priority in the scheme of things, but it might
result in fewer lids like me calling K7RAT on Sunday afternoon when
they're already in the log.

73,

Tim Totten, n4gn@n4gn.com
http://www.n4gn.com
_______________________________________________
Trlog mailing list
Trlog@contesting.com
http://lists.contesting.com/mailman/listinfo/trlog

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