I, too, was running JTAlertX last night for the ‘test, but for a different reason than to check dupes. JTAlertX and Log4OM are my regularly day-to-day system. N1MM+ is only launched during contests. Since JTAlertX is basing dupe declaration on my big log and not the contest, I’m very happy to hear that RC5 will report dupes independently, based on a contest-by-contest effort.
It just keeps getting better. :) From: John Kludt [mailto:johnnykl...@gmail.com] Sent: Tuesday, November 20, 2018 8:54 AM To: WSJT-Dev <wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] RTTY roundup dups David, Actually I found JTAlters very useful for exactly that reason - dup checking. But see Joe's note - already handled in RC5 or the GA release. John On Tue, Nov 20, 2018 at 11:19 AM David Kjellquist <d...@kjellquist.com <mailto:d...@kjellquist.com> > wrote: Has anyone come up with ideas for avoiding dups when using FT8 in a large contest? JTAlert checks B4 but its display matrix is limited and not really designed for contest use. N1MM log integration works well but I don't see that it checks for dups prior actual log entry (not much help). But, I'm not really N1MM literate so I may be missing something. JTAlert does preload a call into AClog but I can't check N3FJP contest logs since N3FJP integration is AClog only. -- Dave, WB5NHL 5BDXCC, 308 countries confirmed 206 wrkd FT8, 159 confirmed _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
