hi Bill - I do understand that WSJT-X is a multi-decoder. On a busy band in RTTY I might have say 4 callsigns to choose from in my receive display after I call CQ, and the contest logger will highlight based on already worked, new mult, etc. - and I click or use a hotkey to grab the one I want to work. So contest loggers already implement a feed of decodes.
(And now we get 40 calls to choose from instead of 4 and we better choose fast or lose our TX slot - time to develop new skills. There's the fun part!) There's an existing UI metaphor for digital contests that works. I'm suggesting that staying within that metaphor may provide the best contesting environment and take less effort than developing a whole contest logger within WSJT-X. thanks and 73 jeff wk6i On Tue, Nov 20, 2018 at 11:19 AM Bill Somerville <g4...@classdesign.com> wrote: > On 20/11/2018 19:01, Jeff Stai wrote: > > If I decide to run WSJT-X in the Roundup, I'm not expecting my > > preferred logger to have any support for it, so I believe I will be > > treating WSJT-X as if it were a stand alone RTTY modem and I'll be > > typing stuff into the contest logger - letting the logger keep track > > of dupes and mults and score as it always does. > > > > This is not how we have come to expect to operate RTTY in contests > > (clicking things or key strokes to get things into the entry window) > > but really it's no worse than operating phone. ;) > > > > It's always seemed to me that the easiest path would be for WSJT-X to > > interact like any modem program (eg MMTTY) with the contest logger, > > let the logger do what it does best, and not reinvent wheels - > > especially when multiple modes and/or logging programs are in the mix. > > But I gather this is not the path being taken. > > > > 73 jeff wk6i > > Hi Jeff, > > I believe you are missing an important factor with WSJT-X, that it is a > multi-signal decoder. With that it becomes important to be able to > quickly determine which of the up to 40+ decodes each 15-second period > are not dupes and more importantly might be new multipliers. In state of > the art contest loggers these capabilities are provided either when you > type in a call to work, or in assisted categories via some sort of band > map populated from worked QSOs, typed in callsigns, and if in an > assisted category from cluster spots. WSJT-X can already pass all > decodes to another application (JTAlert is a good example) for such > processing but as it stands I don't believe any contest loggers have the > required interfaces. Until contest loggers decide to implement a feed of > decodes heard by WSJT-X and allow the logger operator to pick the next > QSO partner from those decodes, we are stuck with WSJT-X having to > provide some equivalent mechanism if we want the contesting community to > see FT8 as a viable mode for digital contests. > > 73 > Bill > G4WJS. > > > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- Jeff Stai ~ WK6I ~ wk6i.j...@gmail.com Ask me about Green Keys Night - Jan 1, 2019 0000-2359 UTC! RTTY op at W7RN Twisted Oak Winery ~ http://www.twistedoak.com/
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
