Well, OK, Joe wrote the program, so he really is the ultimate authority. But the “decoded a spur and used that number for the SNR” seems to be the real issue here.
In an ideal world, signals for a particular call should be sorted _after_ all the decodes are done, and the strongest (very probably not the spur) should be used. However, if the program flow is “Decode at a random spot on the waterfall, queue the results to upload to PSKreporter, set as number to report to QSO partner”, and then another one comes along, you have to do all these gyrations to determine if it’s ‘better’ and replace it, and unqueue from PSKreporter and all this messy stuff. 73, Willie N1JBJ > On Dec 1, 2023, at 3:53 AM, Geoff Van der Wagen via wsjt-devel > <wsjt-devel@lists.sourceforge.net> wrote: > > Hi Joe, > > Puzzled by your response. I agree with not uploading dupes, but I can't > fathom why you wouldn't compare dupes and pick the strongest one. In a > situation like this, clearly the strongest signal is representative of the > real conditions. I can't think of a use for uploading any other decode, > besides as punishment for any stations that dare to have their spurs strong > enough to be heard (ironically the worse their transmitter is, the less they > get punished). > > Anyway, it sounds like a conscious choice, so good luck with it. > > Regards, > > Geoff VK2WA > > > > On 1/12/23 13:14, Joe Taylor via wsjt-devel wrote: >> Hi Geoff, >> >> On 11/30/2023 9:03 PM, Geoff Van der Wagen VK2WA via wsjt-devel wrote: >>> I just had a funny one with a close station, S9+10dB, the transmission was >>> +32 SNR but WSJT-X uploaded only the first decode at -19dB: >>> >>> Queried for all spots me + target, unique NOT ticked: >>> >>> Would have been better to upload the 32dB spot! >> >> Perhaps that would be your choice. It was not ours. >> >> We don't post duplicate decodes. Any decode of a message identical to one >> already staged for posting in the same Rx sequence is considered a dupe and >> discarded. >> >> -- Joe >> >> >> _______________________________________________ >> wsjt-devel mailing list >> 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 _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
