[Dxspider-support] RBN Busted Skimmer Spots

[Joaquin .]

You are absolutely right Lee, skimmers do not always provide reliable
information, but between the all and nothing, between receiving 100 raw
spots (inedible) and none, I am left with receiving 10 treated (filtered)
even if they are imperfect. Moreover, the value of 'Q' > 1 gives us a
certain reliability, and if we rely on our ears (CW) the result can be very
surprising.

>From the tests that I've been doing for months with RBN spots, I can say
that for me it has been a remarkable change (in positive) to go from
receiving all the spots to a few, and not only for the quantity (which now
makes them manageable for humans) but for the usefulness that those who
have passed the filter have given me.
I'm convinced that in the near future we will be able to optimize the code
even more, new algorithms will emerge and the HW will be better :-)

Kin EA3CV


El vie., 10 jul. 2020 a las 10:00, Lee Sawkins via Dxspider-support (<
dxspider-support at tobit.co.uk>) escribió:

> Not to rain on anyone's parade but ... the RBN calls their spot streams
> "raw".  Their spots contain bad calls and frequencies and little is done to
> remove them.  The RBN depends on the clusters to do this.  I have seen no
> mention of how this is being done in the new software.
>
> There are about 150+ CW Skimmers.   Each CW Skimmer is about 99% or so
> accurate for calls.   These skimmers do not all bust the calls the same
> way.  So what you end up with is a much higher error rate of bad to good
> calls.  When working a contest the longer one stays on a band and works
> stations, the higher the percentage of busted calls there is in the band
> map.  Stay on a band long enough and the band map has more busted calls
> than good ones.  I currently see EV73NS, OE7NS, V73N, VE3NS, V73NI, V73T,
> V73NA, V73NN and V73NS spotted on the same frequency.  Only one of those
> calls is right.
>
> CW and RTTY are bad for being busted.  Not so for FT4/FT8, but it still
> happens.  Sometimes grid squares get mistaken for call signs.  I see spots
> for JN87FI in the last few minutes.  Frequently SP5xxx calls get shortened
> to P5xxx.  That usually creates a big pile up.
>
> Lee VE7CC
>
> ----- Original Message -----
> From: Michael Carper, Ph.D. via Dxspider-support <
> dxspider-support at tobit.co.uk>
> To: The DXSpider Support list <dxspider-support at tobit.co.uk>
> Cc: Michael Carper, Ph.D. <mike at wa9pie.net>, Joaquin . <joaquin at cronux.net
> >
> Sent: Fri, 10 Jul 2020 00:02:19 -0600 (MDT)
> Subject: Re: [Dxspider-support] The RBN interface is here...
>
> Unless Dirk objects, I'll be announcing this broadly to our Ham Radio
> Deluxe newsletter group (which hits about 35,000 of the most active hams in
> the world). I can make the announcement fairly generic... but most of our
> customers use WA9PIE-2.
>
> But here's the story... those who don't receive these spots are missing out
> on 90% of the world's spots. Automatically generated spots outnumber
> manually generated spots by more than 10:1 (and it's probably MUCH higher
> than that). Because successful DXers beat the pile-up, getting the
> information first gives you an advantage.
>
> Mike, VK4EIE, WA9PIE
>
> On Fri, Jul 10, 2020 at 3:40 PM Joaquin . via Dxspider-support <
> dxspider-support at tobit.co.uk> wrote:
>
> > A great job has been done by Dirk.
> >
> > Now it's time to make it known to the users, and what better opportunity
> > to try it out at the next IARU HF Contest. Now it's up to us to spread
> the
> > word.
> >
> > Thank you very much Dirk.
> >
> > Kin EA3CV
> >
> > El jue., 9 jul. 2020 a las 23:39, Dirk Koopman via Dxspider-support (<
> > dxspider-support at tobit.co.uk>) escribió:
> >
> >> TL&DR
> >>
> >> The Reverse Beacon Network DXSpider client is here!
> >>
> >> If you want to see what it does: connect to gb7djk.dxcluster.net 7300,
> >> login and then type 'help rbn'.
> >>
> >> If you are a 'master' branch read UPGRADE.mojo, do what it says, then
> >> read RBN.mojo for instructions and information about the RBN interface.
> You
> >> will be able to read both documents in either branch. You should stop
> the
> >> node before doing the 'git pull --all; git checkout --track mojo
> >> origin/mojo'.
> >>
> >> If you are on the 'mojo' branch, then read RBN.mojo and, if necessary,
> do
> >> what it says and read UPGRADE.mojo. Particularly if you have a build
> number
> >> under 276.
> >>
> >> Have fun.
> >>
> >> 73 Dirk G1TLH
> >> _______________________________________________
> >> Dxspider-support mailing list
> >> Dxspider-support at tobit.co.uk
> >> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
> >>
> > _______________________________________________
> > Dxspider-support mailing list
> > Dxspider-support at tobit.co.uk
> > https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
> >
>
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20200710/53cf478e/attachment.htm>