[RTTY] RTTY and Skimmer was: Re: Decoder performance on crowded bands
Michael Adams
mda at n1en.org
Thu Oct 1 12:25:11 EDT 2015
Today, skimmers report once every 10 minutes while a station is detected running.
I wonder, if that logic were tweaked to adjust that window to report "every 10 minutes or after another station has been spotted on that same frequency, whichever comes first", could the CT1BOH skimbusted/skimverify logic be tweaked somehow to warn about possible S&P callers.
Similarly...does there need to be an adjustment in the skimbusted logic to allow consideration of garble tables for RTTY spots?
Finally, elsewhere in this thread, I believe I remember seeing that another node operator was getting feeds from both the RBN and from DL4RCK's system. I have been doing that on my node, but I am discontinuing the DL4RCK feed after my CQWW RTTY experience. On AR v6, duplicate spots from the different networks are being parsed as non-dupes, which impacts the CT1BOH logic.
I can see someone arguing that skimmers can decode RTTY better than CW and therefore should get the "verify" tag sooner, but I chalked up the spotted S&P calls and the busted calls in part to the failure to dedupe spots.
--
Michael Adams | N1EN | mda at n1en.org
-----Original Message-----
This much I'm pretty sure of - neither CW nor RTTY Skimmer does any post-processing. Once the callsign and whether the station is CQing has been determined in a given decoder stream, that information is immediately passed to the Telnet server. Ever since the first days of CW Skimmer I have wished for a function that would, in effect, "notice"
that a station that was spotted as CQing was, in fact, S&P. The obvious way to do this would be to "take note" that a station just posted as CQing turned up within some time interval on a different frequency, therefore indicating that he wasn't CQing at all, or at least no longer on the same frequency. Logging software could then go back and delete the original spot from the Bandmap or other listing of eligible stations waiting to be called.
73, Pete N4ZR
More information about the RTTY
mailing list