My 2c on finding states not worked as multipliers.I used jtalert's ability to flag states not worked. I pointed jtalert to an empty adif file, and let it log the contest traffic. I reset all the wanted states (had them done and not needed that tracking for normal operation) and activated "wanted states" alert. Then, once in awhile I ran scan log and updated the wanted states matrix...Razvan Wa2rp
Sent from Yahoo Mail on Android On Mon, Dec 3, 2018 at 5:31 PM, Bill Somerville<[email protected]> wrote: On 03/12/2018 20:48, David Fisher wrote: > Bottom line – WSJT-X has most of the tools needed for light-duty > contesting. It’s quite useable at that level. If/when it is > integrated with N1MM so we can see multipliers, dupes, etc., in real > time, then we’ll be cooking. I hope someone (Bill perhaps?) will say > a few words about were they hope to go with N1MM integration. Hi David, N1MM Logger+ integration is not necessarily the same thing as dupe and multiplier detection. WSJT-X will almost certainly be enhanced to highlight multipliers seen in any decodes, maybe also to hide decodes or at least highlight (lowlight) dupes based on the QSOs logged so far in a specific contest and the rules of that contest. That's not going to happen for the v2.0.0 GA release as it's too late now. There are also obvious requirements to integrate dupe and multiplier detection with an external contest logging application like N1MM (there are several other popular candidates). This is probably seen as necessary when other modes are used, RTTY Roundup being an excellent example where stations may be worked in FT8 or any other allowed digital mode including RTTY, PSK etc.. This is a much more complex task involving both ends cooperating rather than just firing (and forgetting) data from one program to another like a QSO logged message. TBH it would probably be easier to write a RTTY and PSK decoder for WSJT-X than get such levels of inter-application coordination sorted out, but that is not going to happen. One issue with such integration is the ongoing maintenance and the inevitable slew of requests to support a.n.other non-portable logging application on some favoured operating system. WSJT-X is not a station logbook, it is a weak signal communications tool, to that end logbook and other general station housekeeping functionality will always be on little more than a "minimum to be useable" basis. 73 Bill G4WJS. _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
