Hi Phillip, It would be nice if the problem could be reduced at the source of the spot then there is less complexity needed upstream. My thought is the PSKreporter option in WSJT-X can only be enabled if CAT is defined, this might filter some of the chaff from the wheat when it comes to spots before it gets to upstream services like PSKreporter. (by the way I am a Big fan of your work Phillip)
Another avenue where CAT is not mandatory, might be for WSJT-X to include a 'quality' value with each spot when it is sent from WSJT-X to PSKreporter that identifies those spots coming from a CAT controlled station and those from non CAT stations, this could be used as a weighting factor when looking for bad spots. That I am guessing would need to be a collaboration between yourself and the DEV team as to how it was implemented. The down side would be the sheer weight of old software out there that would still be sending spots. Thanks for your input. Regards, Peter, vk5pj On Tue, Aug 16, 2022 at 11:00 AM Philip Gladstone via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > pskreporter has an algorithm to identify and filter out most of those bad > spots. However, this can only happen once confirming/disconfirming spot > reports arrive from other monitoring stations. Thus HamSpots will be passed > these bad spots before pskreporter can figure out that they are bad. > > Philip > > On Mon, Aug 15, 2022 at 8:01 PM Laurie, VK3AMA via wsjt-devel < > wsjt-devel@lists.sourceforge.net> wrote: > >> >> >> On 16/08/2022 9:52 am, Laurie, VK3AMA via wsjt-devel wrote: >> > >> > HamSpots has a couple of thousand callsigns that have their spots >> > permanently blocked because of repeated occurrences of wrong-band >> > spotting by the callsign >> >> I neglected to add, that the majority of those habitual wrong-band >> spotters spots are entering HamSpots via the PSKReporter spot feed. >> >> de Laurie VK3AMA >> >> >> >> _______________________________________________ >> 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
