[Dxspider-support] Number of spots in CQWW CW?

[Rene Olsen]

Hi.

I found out that the sh/dxs command can actually be told to get stats back in time. I didn't 
know that :-)

sh/dxs 40 20181130 (this command will get stats from November 30th and 40 days back.
I had no idea it could do that. Sometimes it actually helps to read the help.

I have looked at data back to 2018, and the number of spots in the SSB part seems to have 
exploded, while the number of spots in the CW part seems to always have been lower than in 
the SSB part.

 27-Oct-2018:   34264	 26-Oct-2019:   34239	 24-Oct-2020:   36303	 30-Oct-2021:   50188	 29-Oct-2022:   51285
 28-Oct-2018:   33525	 27-Oct-2019:   34896	 25-Oct-2020:   37104	 31-Oct-2021:   51686	 30-Oct-2022:   50757
 24-Nov-2018:   25971	 23-Nov-2019:   24457	 28-Nov-2020:   28661	 27-Nov-2021:   31481	 26-Nov-2022:   34667
 25-Nov-2018:   26922	 24-Nov-2019:   22849	 29-Nov-2020:   28348	 28-Nov-2021:   31466	 27-Nov-2022:   27665

The last two years, the numbers for the SSB part seems to have exploded.

If the CW spots from the RBN network, somehow means that less spots are available on the 
"normal" dx cluster feed, one could argue that it is not so good, as many nodes does not 
have RBN feeds, and if they do, it can be quite overwelming in a contest weekend I guess.

So, I am not sure if this is just the "normal" state of things, that there has just always been 
less spots in the CW part than in the SSB part, or if the RBN feeds are somehow doing 
something as well.

Vy 73 de Rene / OZ1LQH


On 28 Nov 2022 at 16:21, Dirk Koopman via Dxspider-sup wrote:

> Erm...
> 
> That sounds like a "bad thing[tm]", doesn't it?  Surely a direct feed 
> from the RBN has been a feature of contest programs for quite a while. 
> All DXSpider does is curate somewhat to reduce (and distribute)  the 
> bandwidth requirements, whilst trying to retain (and condense) the 
> richness of information available. So I am struggling to understand why 
> overall spot numbers have changed because of my stuff.
> 
> I have another suggestion. The last two years have had many (most?) 
> people at home for (far) more time than usual - for some reason or 
> other. Even though this is a weekend contest, I wonder whether all this 
> enforced time at home meant that more non-work related related jobs that 
> would, under normal work condx, be done at the weekend, got done during 
> the week instead. Thus leaving more time (and concentration levels) 
> available for contesting. This year, things have got back to more normal 
> patterns, but now everything has got much more expensive very quickly. 
> Maybe people are actually having to work more to pay their bills and 
> have much less time for hobbies.
> 
> Or have I got the wrong end of the stick (again)?
> 
> 73 Dirk G1TLH
> 
> On 28/11/2022 12:25, Mike G3YPP via Dxspider-support wrote:
> >
> > Well, I have a theory.
> >
> > I was an active participant in CQWW CW operating G4P making 1100 QSOs, 
> > 2/3 of which were S&P (Search and Pounce)
> >
> > I used N1MM Logger+ connected to my cluster MX0NCA-2.    My cluster is 
> > connected to the RBN so RBN spots are shown in the N1MM bandmap along 
> > with "normal" spots.
> >
> > I have "Spot all S&P QSOs" selected in N1MM.
> >
> > BUT even with this selected N1MM does not spot recently spotted 
> > callsigns (on same frequency).   This is a good intended feature.
> >
> > So because of the RBN feed, N1MM only actually sent 45 of my QSOs to 
> > the cluster.    All the rest had already been spotted by the RBN.
> >
> > Given more clusters now connecting to the RBN - thanks to Dirk´s great 
> > work on the mojo branch - far fewer CW signals are actually spotted on 
> > the "normal" feed.
> >
> > That´s my take on it.
> >
> > Mike G3YPP
> >
> > Sysop for MX0NCA-2
> >
> >
>