>one feature of the latest decoder is there to yield decodes before all >transmissions are completed.
Bill, Was this a user request, or just a result of the new decoding algorithm? (My curiosity has been piqued.) Ed N4II. From: Bill Somerville <g4...@classdesign.com> Sent: Tuesday, May 12, 2020 3:29 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] WSJT-X 2.2.0-rc1 On 12/05/2020 20:22, Christoph Berg wrote: Re: Bill Somerville this change is deliberate. Prior versions favour strong stations calling at the lowest audio offset, we think it is better to randomize the frequency order to give all stations more equal weighting. This is particularly in respect of the "Call 1st" feature. There is also another factor, the latest FT8 decoder makes up to three attempts at decoding, each doing up to three passes. Each attempt subtracts signals from prior attempts to reveal masked signals. There is no sorting or randomizing across the attempts, the overriding priority being to print he decodes as soon as possible after they are discovered. Well that still favors the stronger stations. Was "calling at lower offset" something people were really rushing for, or did that have any bias towards them in contests or crowded bands? What I wanted sometimes was a "favor callers *not* on my tx frequency". (But that's probably an unrelated thing to this change.) Another plus of the old ordering was that you could see the three passes and say "hey look it decoded this one because it subtracted a stronger signal first". The new ordering seems to be pretty messy instead. Christoph Hi Christoph, yes stronger signals may well be decoded on an earlier pass, but we cannot deal with that without delaying the printing of any decodes until all decodes attempts are completed, that would be very counterproductive given one feature of the latest decoder is there to yield decodes before all transmissions are completed. We could of course sort decodes continuously as they flow in, but that would make the UI very confusing with decodes continuously shuffling just as you are trying to read them. There is no optimal solution. 73 Bill G4WJS.
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
