<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection">
<div dir="auto">Hi Mike,<br />
<br />
I’ve just been through and checked, out of all of my node partners, only four of them accepted all the self spots which were sent via me during AFS yesterday. Most accepted some of them but only with a ten minute gap, not the five minutes that one of my users was trying.<br />
<br />
Just checking your node, it’s the same - It’s showing around half of the spots that he uploaded.<br />
<br />
Kin posted a modified DXDupe.pm file a couple of days ago along with the variables to tweak, these are the variables I’ve added to my /spider/startup and these, along with the updated file, are allowing the self spotting at roughly one minute intervals. Of course, I can’t control what other nodes accept.<br />
<br />
Hope this helps.<br />
<br />
73 Keith<br />
<br />
# Allow self spotting on all frequencies<br />
set/var $Spot::minselfspotqrg 0<br />
<br />
# duplicate time to 1 minute (60 seconds)<br />
# default was 3600<br />
set/var $Spot::dupage 60<br />
<br />
# resolution spot time to 1 minute (60 seconds)<br />
# default was 600<br />
set/var $Spot::timegranularity 60<br />
<br />
# resolution spot qrg in kilohertz<br />
# default was 25<br />
set/var $Spot::qrggranularity 1<br />
<br />
<br />
<br />
<br /></div>
</div>
<div name="messageReplySection">On 19 Jan 2025 at 17:40 +0000, Mike G3YPP via Dxspider-support <dxspider-support@tobit.co.uk>, wrote:<br />
<blockquote type="cite" style="border-left-color: grey; border-left-width: thin; border-left-style: solid; margin: 5px 5px;padding-left: 10px;">Keith,<br />
We had the same issue at our node MX0NCA-2.<br />
Self spots did not propagate to the network at all.<br />
<br />
Any ideas would be welcome.<br />
<br />
Mike G3YPP/G4P<br />
Sysop for MX0NCA-2<br />
Sent from my iPad<br />
<br />
<blockquote type="cite">On 19 Jan 2025, at 17:04, dxspider-support-request@tobit.co.uk wrote:<br />
<br />
Send Dxspider-support mailing list submissions to<br />
dxspider-support@tobit.co.uk<br />
<br />
To subscribe or unsubscribe via the World Wide Web, visit<br />
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br />
or, via email, send a message with subject or body 'help' to<br />
dxspider-support-request@tobit.co.uk<br />
<br />
You can reach the person managing the list at<br />
dxspider-support-owner@tobit.co.uk<br />
<br />
When replying, please edit your Subject line so it is more specific<br />
than "Re: Contents of Dxspider-support digest..."<br />
<br />
<br />
Today's Topics:<br />
<br />
1. Re: Self-spotting and de-duplication (Keith)<br />
<br />
<br />
----------------------------------------------------------------------<br />
<br />
Message: 1<br />
Date: Sun, 19 Jan 2025 17:03:37 +0000<br />
From: Keith, G6NHU <g6nhu@me.com><br />
To: The DXSpider Support list <dxspider-support@tobit.co.uk><br />
Subject: Re: [Dxspider-support] Self-spotting and de-duplication<br />
Message-ID: <b53d5c05-9b05-4b55-bbdb-69ee2e6196d6@Spark><br />
Content-Type: text/plain; charset="utf-8"<br />
<br />
I?ve had a couple of users ask me about this because yesterday was the RSGB AFS contest which now allows self spotting for the first time.<br />
<br />
All their spots were accepted at my node but sadly other nodes didn?t take them all, I assume due to de-duplication settings.<br />
<br />
So until everyone is unified, self spots at five minute intervals won?t propagate anyway.<br />
<br />
73 Keith<br />
<br />
<blockquote type="cite">On 17 Jan 2025 at 13:31 +0000, IZ2LSC via Dxspider-support <dxspider-support@tobit.co.uk>, wrote:<br />
Thanks Kin,<br />
I will try it on my backup (isolated) cluster node.<br />
<br />
73<br />
Andrea<br />
iz2lsc<br />
<br />
--><br />
<br />
<br />
<blockquote type="cite">On Fri, Jan 17, 2025 at 12:55?PM Kin <ea3cv@cronux.net> wrote:<br />
Morning Andrea,<br />
<br />
While waiting for Dirk to confirm the possible bug and its solution, I'm passing you a modified version of DXDupe.pm that fixes the deletion of hashes depending on the $Spot::dupage variable.<br />
It also solves the problem of deleting expired spots.<br />
<br />
It should be copied to: /spider/Local and restart the node.<br />
<br />
Kin EA3CV<br />
<br />
De: Dxspider-support <dxspider-support-bounces@tobit.co.uk> En nombre de IZ2LSC via Dxspider-support<br />
Enviado el: viernes, 17 de enero de 2025 10:18<br />
Para: The DXSpider Support list <dxspider-support@tobit.co.uk><br />
CC: IZ2LSC <iz2lsc.andrea@gmail.com><br />
Asunto: Re: [Dxspider-support] Self-spotting and de-duplication<br />
<br />
If every time a spot is ignored is also added?again to the dupe list, this is a loop. Maybe is this the bug?<br />
<br />
1737101764^(pc11) PCPROT: Duplicate Spot ?IZ2LSC-97: PC61 7006.0|JF4IQS/1|1737101700|JF4IQS|IZ2LSC-97 ignored<br />
<br />
view_dupes JF4IQS/1<br />
|JF4IQS/1|JF4IQS|433060||1737100440|POTAJP1149FMHIK = 17-Jan-2025 0754Z expires 17-Jan-2025 0824Z<br />
|JF4IQS/1|JF4IQS|7005||1737100800|POTAJP1149CWHIK = 17-Jan-2025 0801Z expires 17-Jan-2025 0831Z<br />
|JF4IQS/1|JF4IQS|7005|[-POTA-] JP-114 = 17-Jan-2025 0801Z expires 17-Jan-2025 0831Z<br />
|JF4IQS/1|JI2OJV|7005||1737101580|POTAJP1149CWHIK = 17-Jan-2025 0814Z expires 17-Jan-2025 0844Z<br />
|JF4IQS/1|JI2OJV|7005|[-POTA-] JP-114 = 17-Jan-2025 0814Z expires 17-Jan-2025 0844Z<br />
|JF4IQS/1|JF4IQS|7005||1737101700|POTAJP1149CWHIK = 17-Jan-2025 0816Z expires 17-Jan-2025 0846Z<br />
<br />
--><br />
<br />
<br />
On Thu, Jan 16, 2025 at 11:01?PM IZ2LSC <iz2lsc.andrea@gmail.com> wrote:<br />
<blockquote type="cite">Kin,<br />
when the hash is expired, is it removed from the file?<br />
I can see hash already?expired and still present in the file.<br />
Not sure if this is expected.<br />
<br />
Andrea<br />
<br />
--><br />
<br />
<br />
On Thu, Jan 16, 2025 at 8:12?PM Bj?rn Ekelund via Dxspider-support <dxspider-support@tobit.co.uk> wrote:<br />
<blockquote type="cite">Thanks. For human spots it makes perfect sense to include the comment.<br />
<br />
Bj?rn SM7IUN<br />
<br />
On Thu, Jan 16, 2025 at 7:06?PM Kin <ea3cv@cronux.net> wrote:<br />
<blockquote type="cite">Bj?rn,<br />
<br />
All this is for non-RBN spots.<br />
I don't remember now the treatment of RBN spots.<br />
<br />
Kin<br />
<br />
De: Bj?rn Ekelund <bjorn@ekelund.nu><br />
Enviado el: jueves, 16 de enero de 2025 18:26<br />
Para: Kin <ea3cv@cronux.net><br />
CC: The DXSpider Support list <dxspider-support@tobit.co.uk><br />
Asunto: Re: [Dxspider-support] Self-spotting and de-duplication<br />
<br />
Kin,<br />
<br />
this was very clear and very helpful.<br />
Thank you for spending the time to do it.<br />
I am sure others appreciate it too.<br />
<br />
In my?opinion, all comments should be ignored when determining?dupes for skimmer spots.<br />
<br />
Bj?rn SM7IUN<br />
<br />
On Thu, Jan 16, 2025 at 10:28?AM Kin <ea3cv@cronux.net> wrote:<br />
<blockquote type="cite">Morning Bj?rn,<br />
<br />
<blockquote type="cite">So timegranularity defines a window within which spots are considered to have<br />
the same time, Does this then effectively define the minimum respotting time?<br /></blockquote>
<br />
Yes, timegranularity effectively defines the minimum respotting time. It determines the size of the time window within which spots are considered to have the same timestamp. For example, if timegranularity is set to 600 seconds (10 minutes), any spots reported within the same 10-minute interval will be grouped together, effectively preventing additional spots from being considered separate unless they occur in a different interval.<br />
<br />
<blockquote type="cite">Or is this the function of dupage? If it is, then I do not see the purpose of quantizing<br />
time into timegranularity steps.<br /></blockquote>
<br />
timegranularity is about standardizing time representation, while dupage enforces the minimum time between duplicate spots.<br />
<br />
<blockquote type="cite">And how can 600 be 4 minutes? Is time counted in steps of 0.4s?<br />
Does this mean that dupage 3600 is 24 minutes?<br /></blockquote>
<br />
<blockquote type="cite">And what is the function of qrggranularity? My empirical experiments say that I need<br />
to move 10kHz away for DXSpider to not consider a new spot a dupe. Not 25kHz.<br /></blockquote>
<br />
I hope that the following examples will clarify how it works.<br />
<br />
<blockquote type="cite">All I'm trying to do is to set up my node so that<br /></blockquote>
<br />
<blockquote type="cite">1. a new spot of the same station on the same QRG after more than 3 minutes is never considered a dupe<br /></blockquote>
<br />
$Spot::timegranularity = 60<br />
$Spot::dupage = 180<br />
<br />
You should know that a duplicate is the sum of the fields spotted+spotter+qrg+time+comments, which will generate a hash like this: |IZ0ARL|IK2JTS|7075||1737012600|DTMBAI1823RM. For this reason, just using spotted+qrg+time is not sufficient to determine duplication.<br />
<br />
<blockquote type="cite">2. a new spot of a station 1kHz away from the previous spot is never considered a dupe.<br /></blockquote>
<br />
$Spot::qrggranularity = 1<br />
<br />
<blockquote type="cite">3. self spots are never ever blocked<br /></blockquote>
<br />
$Spot::minselfspotqrg = 0<br />
<br />
<br />
Example<br />
<br />
* Variables<br />
<br />
$Spot::timegranularity = 600??? --> 10 min<br />
$Spot::qrggranularity = 25????? --> 25 kHz<br />
$Spot::dupage = 3600??????????? --> 1 h<br />
<br />
* Spot<br />
<br />
DX de IK2JTS:???? 7065.0? IZ0ARL?????? DTMBA I1823RM??????????????????? 0731Z (1737012660)<br />
<br />
<br />
Adjusts to the nearest multiple (either downward or upward)<br />
<br />
1737012660/600 = 2895021.1 --> 2895021 (round to the nearest integer)<br />
2895021*600 = 1737012600<br />
<br />
7065.0/25 = 282.6 --> 283 (round to the nearest integer)<br />
283?25 = 7075<br />
<br />
* dupefile<br />
<br />
|IZ0ARL|IK2JTS|7075||1737012600|DTMBAI1823RM = 16-Jan-2025 0731Z expires 16-Jan-2025 0831Z<br />
<br />
This means that time is fixed in 10-minute intervals, and frequency is fixed in 25 kHz steps.<br />
<br />
<br />
* Comparison with different values for the same spot:<br />
<br />
DX de IK2JTS:???? 7065.0? IZ0ARL?????? DTMBA #I-1823RM????????????????? 0735Z (1737012900)<br />
<br />
Scenario 1:<br />
<br />
$Spot::timegranularity = 600<br />
$Spot::qrggranularity = 25<br />
$Spot::dupage = 3600<br />
<br />
|IZ0ARL|IT9JZK|7075||1737013200|DTMBAI1823RM = 16-Jan-2025 0735Z expires 16-Jan-2025 0835Z<br />
?????????????????????? (0740Z)<br />
<br />
Scenario 2:<br />
<br />
$Spot::timegranularity = 60<br />
$Spot::qrggranularity = 1<br />
$Spot::dupage = 300<br />
<br />
|IZ0ARL|IT9JZK|7065||1737012900|DTMBAI1823RM = 16-Jan-2025 0735Z expires 16-Jan-2025 0740Z<br />
????????????????????? (0735Z)<br />
<br />
<br />
I'm not sure if I?ve managed to explain myself clearly this time. This is my interpretation after analyzing the code, from someone who is not an expert. I think the person who can help us best is Dirk, the creator of this. And sorry because my English is terrible<br />
<br />
Kin EA3CV<br />
<br /></blockquote>
</blockquote>
_______________________________________________<br />
Dxspider-support mailing list<br />
Dxspider-support@tobit.co.uk<br />
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br /></blockquote>
</blockquote>
</blockquote>
_______________________________________________<br />
Dxspider-support mailing list<br />
Dxspider-support@tobit.co.uk<br />
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br /></blockquote>
-------------- next part --------------<br />
An HTML attachment was scrubbed...<br />
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20250119/cd40b167/attachment.htm><br />
<br />
------------------------------<br />
<br />
Subject: Digest Footer<br />
<br />
_______________________________________________<br />
Dxspider-support mailing list<br />
Dxspider-support@tobit.co.uk<br />
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br />
<br />
<br />
------------------------------<br />
<br />
End of Dxspider-support Digest, Vol 264, Issue 63<br />
*************************************************<br /></blockquote>
<br />
<br />
_______________________________________________<br />
Dxspider-support mailing list<br />
Dxspider-support@tobit.co.uk<br />
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br /></blockquote>
</div>
</body>
</html>