I tried a little experiment today. I operate the CW Ops mini tests and normally use SKIMVALID in my filters that I use for cw skimmers....in this mornings test, I only saw one busted call K4TZ/TK4TZ. For this afternoons session, I changed SKIMVALID to NOT SKIMBUSTED and in about the same length of time (25-30 minutes), I ran into several more busts:
N7US/N7UN
K4TZ/TK4TZ
K5TU/TK5TU
N2IC/TN2IC
F5TKR/N5KTR
N4AF/TN4AF
now this morning I was on 40M, and 20M this afternoon, so maybe prop played a role in it, and I know its a small sample set, but I am not convinced the NOT SKIMBUSTED works as well , or better, than SKIMVALID
------ Original Message ------
Date 2/3/2025 6:22:24 PM
Subject Re: [DXLab] Reasonable call prefilter
I posted this on the N1MM Logger+ group just over a month ago:
?
See <http://www.k3lr.com/w9zrx/AR-Cluster%20Filter%20Commands.pdf>, near the top of page 5.
?
Looking at those definitions: Skimvalid looks for multiple spots with the same callsign. Skimbusted looks for similar (e.g. "off-by-one") callsigns that are already marked as valid. A busted spot could still pass as Skimvalid if enough skimmers bust the call the same way, but if the correct call has already been spotted there, adding Not Skimbusted to the filter may help prevent the busted spot from showing up.
?
73,
Rich VE3KI
?
On Mon, Feb 3, 2025 at 05:04 PM, Jamie WW3S wrote:
Whats the difference between, if any, between NOT SKIMBUSTED and SKIMVALID ? My skimmer filters use SKIMVALID and other than occasionally getting a T in front of some calls, they seem pretty reliable …..
?
On Feb 3, 2025, at 7:41?AM, John K3TN via groups.io <jpescatore@...> wrote:
For all AR clusters you can enter a filter command that takes advantage of spot quality filter: SET DX FILTER NOT SKIMBUSTED
?
That does a great job of eliminating bad RBN/skimmer spots, based on work by CT1BOH. Not perfect, but really big step forward.
?
73 John K3TN
?
?
