<div dir="ltr">Just to give an example since I had it copied to the notepad...<div><br></div><div>19Mar2025@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^~<br>19Mar2025@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'<br>19Mar2025@20:37:35 (spotdup) Spot::add_dup: CHECK (NORM TEXT) XIQ3VN|IN3JYO|14080|FT4LAGORAIAWARD<br>19Mar2025@20:37:35 (spotdup) Spot::add_dup: CHECK (QRG-CALL) XIQ3VN|14080<br>19Mar2025@20:37:35 (spotdup) Spot::add_dup: CHECK (CALL) XIQ3VN<br>19Mar2025@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'<br>19Mar2025@20:37:35 (spotdup) Spot::add_dup: ADD (NORM TEXT) XIQ3VN|IN3JYO|14080|FT4LAGORAIAWARD STORE=>20:40:35Z<br>19Mar2025@20:37:35 (spotdup) Spot::add_dup: ADD (QRG-CALL) XIQ3VN|14080 STORE=>20:42:40Z<br>19Mar2025@20:37:35 (spotdup) Spot::add_dup: ADD (CALL) XIQ3VN STORE=>20:37:45Z<br>19Mar2025@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<br>19Mar2025@20:37:35 (chan) -> X WI3W DX de IN3JYO: 14080.0 IQ3VN FT4 LAGORAI Award 2025 2037Z<br><br><br>19Mar2025@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^~<br>19Mar2025@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'<br>19Mar2025@20:37:53 (spotdup) Spot::add_dup: CHECK (NORM TEXT) XIQ3VN|IN3JYO|14080|LAGORAIAWARD202<br>19Mar2025@20:37:53 (spotdup) Spot::add_dup: CHECK (QRG-CALL) XIQ3VN|14080 DUPE=>20:42:40Z<br></div><div><br></div><div>You can see where it passed initially due to the change in comment, but caught and duped on the callsign and frequency.</div><div><br></div><div>Chris, WI3W</div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Mar 21, 2025 at 3:21 PM Kin via Dxspider-support <<a href="mailto:dxspider-support@tobit.co.uk">dxspider-support@tobit.co.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Now it's obvious.<br>
Everything is set up on 5 nodes. We'll see how things evolve.<br>
<br>
Thanks, Dirk<br>
<br>
Kin<br>
<br>
-----Mensaje original-----<br>
De: Dirk Koopman <<a href="mailto:djk@tobit.co.uk" target="_blank">djk@tobit.co.uk</a>> <br>
Enviado el: viernes, 21 de marzo de 2025 20:01<br>
Para: The DXSpider Support list <<a href="mailto:dxspider-support@tobit.co.uk" target="_blank">dxspider-support@tobit.co.uk</a>><br>
CC: Kin <<a href="mailto:ea3cv@cronux.net" target="_blank">ea3cv@cronux.net</a>>; The DXSpider Support list <<a href="mailto:dxspider-support@tobit.co.uk" target="_blank">dxspider-support@tobit.co.uk</a>><br>
Asunto: Re: [Dxspider-support] Question about Spot::add_dup. build test-598<br>
<br>
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.<br>
<br>
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. <br>
<br>
It only gets more complicated when looking at the individual fields where one gets into non-identical copies.<br>
<br>
Dirk <br>
<br>
> On 21 Mar 2025, at 18:42, Kin via Dxspider-support <<a href="mailto:dxspider-support@tobit.co.uk" target="_blank">dxspider-support@tobit.co.uk</a>> wrote:<br>
> <br>
> Dirk,<br>
> <br>
> The following spot:<br>
> <br>
> 1742576798<br>
> PC61^28074.0^AF5CC^21-Mar-2025^1706Z^FT8^ES0IA^SK3W-6^91.129.104.85^H1<br>
> 8^~<br>
> <br>
> triggers all of this after the CHECKs:<br>
> <br>
> 1742576798^(spotdup) Spot::add_dup: ADD (+INPUT+) freq=28074.0<br>
> call=AF5CC d=1742576760 text='FT8' by=ES0IA node=SK3W-6 <br>
> ipaddr='91.129.104.85'<br>
> 1742576798^(spotdup) Spot::add_dup: ADD (NORM TEXT) XAF5CC|ES0IA|28074|FT8<br>
> +600 secs STORE=>17:16:37Z<br>
> 1742576798^(spotdup) Spot::add_dup: ADD (QRG-CALL) XAF5CC|28074<br>
> +305 secs STORE=>17:11:42Z<br>
> 1742576798^(spotdup) Spot::add_dup: ADD (CALL) XAF5CC<br>
> +10 secs STORE=>17:06:47Z<br>
> 1742576798^(spotdup) Spot::add_dup: ADD (BY) XES0IA<br>
> +10 secs STORE=>17:06:47Z<br>
> 1742576798^(spotdup) Spot::add_dup: ADD (IPADDR) X91.129.104.85<br>
> +10 secs STORE=>17:06:47Z<br>
> <br>
> The question is: how is it possible that the next two spots were <br>
> labeled as DUPE if the threshold wasn't exceeded? The three PC61s <br>
> arrived in the same second, right?<br>
> <br>
> 1742576798^(spotdup) Spot::add_dup: CHECK (+INPUT+) freq=28074.0<br>
> call=AF5CC d=1742576760 text='FT8' by=ES0IA node=SK3W-6 <br>
> ipaddr='91.129.104.85'<br>
> 1742576798^(spotdup) Spot::add_dup: CHECK (NORM TEXT) <br>
> XAF5CC|ES0IA|28074|FT8 DUPE=>17:16:37Z<br>
> 1742576798^(spotdup) Spot::add_dup: CHECK (+INPUT+) freq=28074.0<br>
> call=AF5CC d=1742576760 text='FT8' by=ES0IA node=SK3W-6 <br>
> ipaddr='91.129.104.85'<br>
> 1742576798^(spotdup) Spot::add_dup: CHECK (NORM TEXT) <br>
> XAF5CC|ES0IA|28074|FT8 DUPE=>17:16:37Z<br>
> <br>
> Kin EA3CV<br>
> <br>
> <br>
> <winmail.dat><br>
> _______________________________________________<br>
> Dxspider-support mailing list<br>
> <a href="mailto:Dxspider-support@tobit.co.uk" target="_blank">Dxspider-support@tobit.co.uk</a><br>
> <a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" rel="noreferrer" target="_blank">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
<br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
<a href="mailto:Dxspider-support@tobit.co.uk" target="_blank">Dxspider-support@tobit.co.uk</a><br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support" rel="noreferrer" target="_blank">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
</blockquote></div>