[Dxspider-support] Question about Spot::add_dup. build test-598
Kin
ea3cv at cronux.net
Sat Mar 22 08:42:51 GMT 2025
Morning Chris,
(Chan) <- I WI3W-2 PC61^14080.0^IQ3VN^19-Mar-2025^2037Z^FT4 Premio LAGORAI 2025^ IN3JYO^IW1FRU-74^195.32.127.23^H27^~ 4 hops
(Chan) <- I WI3W-2 PC61^14080.0^IQ3VN^19-Mar-2025^2037Z^PREMIO LAGORAI 2025 FT4 10 PUNTOS^IN3JYO^EA4RCH-5^ 195.32.127.23^H25^~ 6 hops
The minimum route between IW1FRU-74 and WI3W-2 is 3 hops. There are at least 5 routes with 3 hops.
In the provided example, there are 4 hops.
See https://github.com/EA3CV/dxspider_info/blob/main/Logs/01.png
The minimum route between EA4RCH-5 and WI3W-2 is 3 hops. There are at least 8 routes with 3 hops.
In the provided example, there are 6 hops.
See https://github.com/EA3CV/dxspider_info/blob/main/Logs/02.png
My conclusion regarding the variation in hops:
1. Other identical PC61s may have arrived at WI3W-2 with fewer hops but were not shown in the capture.
2. Something is failing, and I don’t believe all the transit nodes involved are responsible. Ergo...
Regarding the variation in the "comment" and "origin node" fields at the same time, I see two possible explanations:
1. Two spots were created simultaneously on two different nodes, apparently by a machine (synchronization).
2. One of the PC61s may have been modified and re-injected into the network.
If we combine all this information, what do you think is happening here?
Kin EA3CV
PS
IW1FRU-74 isn't just associated with Keith G6NHU-2. It appears to have more nodes: CX2SA-8 and G0TRT-9.
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Christopher Schlegel via Dxspider-support
Enviado el: viernes, 21 de marzo de 2025 23:49
Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
CC: Christopher Schlegel <sutehk.cs at gmail.com>
Asunto: Re: [Dxspider-support] Question about Spot::add_dup. build test-598
Just to give an example since I had it copied to the notepad...
19Mar2025 at 20:37:35 (chan) <- I WI3W-2 PC61^14080.0^IQ3VN^19-Mar-2025^2037Z^FT4 LAGORAI Award 2025^IN3JYO^IW1FRU-74^195.32.127.23^H27^~
19Mar2025 at 20:37:35 (spotdup) Spot::add_dup: CHECK (+INPUT+) freq=14080.0 call=IQ3VN d=1742416620 text='FT4 LAGORAI Award 2025' by=IN3JYO node=IW1FRU-74 ipaddr='195.32.127.23'
19Mar2025 at 20:37:35 (spotdup) Spot::add_dup: CHECK (NORM TEXT) XIQ3VN|IN3JYO|14080|FT4LAGORAIAWARD
19Mar2025 at 20:37:35 (spotdup) Spot::add_dup: CHECK (QRG-CALL) XIQ3VN|14080
19Mar2025 at 20:37:35 (spotdup) Spot::add_dup: CHECK (CALL) XIQ3VN
19Mar2025 at 20:37:35 (spotdup) Spot::add_dup: ADD (+INPUT+) freq=14080.0 call=IQ3VN d=1742416620 text='FT4 LAGORAI Award 2025' by=IN3JYO node=IW1FRU-74 ipaddr='195.32.127.23'
19Mar2025 at 20:37:35 (spotdup) Spot::add_dup: ADD (NORM TEXT) XIQ3VN|IN3JYO|14080|FT4LAGORAIAWARD STORE=>20:40:35Z
19Mar2025 at 20:37:35 (spotdup) Spot::add_dup: ADD (QRG-CALL) XIQ3VN|14080 STORE=>20:42:40Z
19Mar2025 at 20:37:35 (spotdup) Spot::add_dup: ADD (CALL) XIQ3VN STORE=>20:37:45Z
19Mar2025 at 20:37:35 (progress) SPOT: IQ3VN on 14080.0 @ 2037Z by IN3JYO(195.32.127.23)@IW1FRU-74 'FT4 LAGORAI Award 2025' route: WI3W-2
19Mar2025 at 20:37:35 (chan) -> X WI3W DX de IN3JYO: 14080.0 IQ3VN FT4 LAGORAI Award 2025 2037Z
19Mar2025 at 20:37:53 (chan) <- I WI3W-2 PC61^14080.0^IQ3VN^19-Mar-2025^2037Z^LAGORAI AWARD 2025 FT4 10 POINTS^IN3JYO^EA4RCH-5^195.32.127.23^H25^~
19Mar2025 at 20:37:53 (spotdup) Spot::add_dup: CHECK (+INPUT+) freq=14080.0 call=IQ3VN d=1742416620 text='LAGORAI AWARD 2025 FT4 10 POINTS' by=IN3JYO node=EA4RCH-5 ipaddr='195.32.127.23'
19Mar2025 at 20:37:53 (spotdup) Spot::add_dup: CHECK (NORM TEXT) XIQ3VN|IN3JYO|14080|LAGORAIAWARD202
19Mar2025 at 20:37:53 (spotdup) Spot::add_dup: CHECK (QRG-CALL) XIQ3VN|14080 DUPE=>20:42:40Z
You can see where it passed initially due to the change in comment, but caught and duped on the callsign and frequency.
Chris, WI3W
On Fri, Mar 21, 2025 at 3:21 PM Kin via Dxspider-support <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk> > wrote:
Now it's obvious.
Everything is set up on 5 nodes. We'll see how things evolve.
Thanks, Dirk
Kin
-----Mensaje original-----
De: Dirk Koopman <djk at tobit.co.uk <mailto:djk at tobit.co.uk> >
Enviado el: viernes, 21 de marzo de 2025 20:01
Para: The DXSpider Support list <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk> >
CC: Kin <ea3cv at cronux.net <mailto:ea3cv at cronux.net> >; The DXSpider Support list <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk> >
Asunto: Re: [Dxspider-support] Question about Spot::add_dup. build test-598
What *should* happen is that the next exact copy of the spot (from another node) will fail at the normal full spot dupe record - which is how it has always been done.
Therefore it won’t trigger all the other tests. The tests operate in the same fashion as “ladder logic”. An exact copy will fail on the first step.
It only gets more complicated when looking at the individual fields where one gets into non-identical copies.
Dirk
> On 21 Mar 2025, at 18:42, Kin via Dxspider-support <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk> > wrote:
>
> Dirk,
>
> The following spot:
>
> 1742576798
> PC61^28074.0^AF5CC^21-Mar-2025^1706Z^FT8^ES0IA^SK3W-6^91.129.104.85^H1
> 8^~
>
> triggers all of this after the CHECKs:
>
> 1742576798^(spotdup) Spot::add_dup: ADD (+INPUT+) freq=28074.0
> call=AF5CC d=1742576760 text='FT8' by=ES0IA node=SK3W-6
> ipaddr='91.129.104.85'
> 1742576798^(spotdup) Spot::add_dup: ADD (NORM TEXT) XAF5CC|ES0IA|28074|FT8
> +600 secs STORE=>17:16:37Z
> 1742576798^(spotdup) Spot::add_dup: ADD (QRG-CALL) XAF5CC|28074
> +305 secs STORE=>17:11:42Z
> 1742576798^(spotdup) Spot::add_dup: ADD (CALL) XAF5CC
> +10 secs STORE=>17:06:47Z
> 1742576798^(spotdup) Spot::add_dup: ADD (BY) XES0IA
> +10 secs STORE=>17:06:47Z
> 1742576798^(spotdup) Spot::add_dup: ADD (IPADDR) X91.129.104.85
> +10 secs STORE=>17:06:47Z
>
> The question is: how is it possible that the next two spots were
> labeled as DUPE if the threshold wasn't exceeded? The three PC61s
> arrived in the same second, right?
>
> 1742576798^(spotdup) Spot::add_dup: CHECK (+INPUT+) freq=28074.0
> call=AF5CC d=1742576760 text='FT8' by=ES0IA node=SK3W-6
> ipaddr='91.129.104.85'
> 1742576798^(spotdup) Spot::add_dup: CHECK (NORM TEXT)
> XAF5CC|ES0IA|28074|FT8 DUPE=>17:16:37Z
> 1742576798^(spotdup) Spot::add_dup: CHECK (+INPUT+) freq=28074.0
> call=AF5CC d=1742576760 text='FT8' by=ES0IA node=SK3W-6
> ipaddr='91.129.104.85'
> 1742576798^(spotdup) Spot::add_dup: CHECK (NORM TEXT)
> XAF5CC|ES0IA|28074|FT8 DUPE=>17:16:37Z
>
> Kin EA3CV
>
>
> <winmail.dat>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk <mailto: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 <mailto: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/20250322/9c206892/attachment-0001.htm>
More information about the Dxspider-support
mailing list