[Dxspider-support] 10Ghz+ spots

Tue Nov 30 12:15:01 GMT 2021

Thank you all for your responses. It appears that it is AR-Cluster that 
is the culprit. It appears to have only 7 digits of precision, but 
handles the exponent. Which suggests that it is using a float, rather 
than a double for QRG. Which means that, if this _is_ the internal 
representation in AR-C, depending on the exact (binary version) of the 
mantissa it can have between 6 and 9 decimal digits precision. 
Alternatively, it could be using a double and arithmetically rounding it 
to the nearest 7 digits. Or just truncating (flooring) it. Either way it 
is bad.

Lee VE7CC and I are discussing what to do about PC11s coming from AR-C 
nodes. But, right now what you could do is set an input filter on any 
AR-C nodes that you connect to, eg. reject/spot k1ttt input  on 
10000000/99000000

This means no disrespect to David but duplicate spots like this have to 
be suppressed. There are other issues with spots coming from AR-C nodes 
even on lower frequencies. These are less tractable and will be harder 
to deal with and could require more drastic action.

Dirk G1TLH

On 30/11/2021 09:04, gu6efb--- via Dxspider-support wrote:
>
> Can’t seem to find that spot on DXspider cluster but it’s in the 
> CCCluster log if it helps
>
> CCCluster log GB7DXG
>
> <- 17:25:22 GU6EFB-1 CC11^7074^BG3GBZ^29-Nov-2021^1725Z^FT8  -11 dB 
> 1364 Hz^VE7CC-#^1^^RBNFT8^33^23^2^3^^BC^BY^VE^ON40^CN99^40^40.5/-109^
>
> <- 17:25:22 GU6EFB-1 CC11^7074^HS3PJF^29-Nov-2021^1725Z^FT8  + 0 dB  
> 337 Hz^VE7CC-#^1^^RBNFT8^49^26^2^3^^BC^HS^VE^OK04^CN99^40^14.5/-101^
>
> -> 17:25:23 ON0DXK-5 PC61^10489772.0^9X4X^29-Nov-2021^1725Z^KI48XE  
> nice op^SV5BYR^SV5BYR-7^192.168.178.1^H29^~
>
> <- 17:25:23 GB7RDX PC61^10489772.0^9X4X^29-Nov-2021^1725Z^KI48XE  nice 
> op^SV5BYR^SV5BYR-7^192.168.178.1^H28^~
>
> <- 17:25:23 EA2CW PC61^10489772.0^9X4X^29-Nov-2021^1725Z^KI48XE  nice 
> op^SV5BYR^SV5BYR-7^192.168.178.1^H28^~
>
> <- 17:25:23 GB7DXG-1 PC61^10489772.0^9X4X^29-Nov-2021^1725Z^KI48XE  
> nice op^SV5BYR^SV5BYR-7^192.168.178.1^H28^~
>
> <- 17:25:23 VE7CC-1 PC61^10489772.0^9X4X^29-Nov-2021^1725Z^KI48XE  
> nice op^SV5BYR^SV5BYR-7^192.168.178.1^H28^~
>
> <- 17:25:23 G3WNR DX de SV5BYR: 10489772.0  9X4X         KI48XE  nice 
> op                1725Z
>
> -> 17:25:23 VE7CC-1 PC61^10489772.0^9X4X^29-Nov-2021^1725Z^KI48XE  
> nice op^SV5BYR^SV5BYR-7^192.168.178.1^H26^~
>
> -> 17:25:23 GB7RDX PC11^10489770.0^9X4X^29-Nov-2021^1725Z^KI48XE  nice 
> op^SV5BYR^SV5BYR-7^H97^~
>
> <- 17:25:23 EA2CW PC11^10489770.0^9X4X^29-Nov-2021^1725Z^KI48XE  nice 
> op^SV5BYR^SV5BYR-7^H96^~
>
> <- 17:25:23 GB7DXG-1 PC11^10489770.0^9X4X^29-Nov-2021^1725Z^KI48XE  
> nice op^SV5BYR^SV5BYR-7^H96^~
>
> <- 17:25:23 ON0DXK-5 PC11^10489770.0^9X4X^29-Nov-2021^1725Z^KI48XE  
> nice op^SV5BYR^SV5BYR-7^H96^~
>
> <- 17:25:23 VE7CC-1 PC11^10489770.0^9X4X^29-Nov-2021^1725Z^KI48XE  
> nice op^SV5BYR^SV5BYR-7^H96^~
>
> <- 17:25:23 G3WNR DX de SV5BYR: 10489770.0  9X4X         KI48XE  nice 
> op                1725Z
>
> -> 17:25:23 ON0DXK-5 PC11^10489770.0^9X4X^29-Nov-2021^1725Z^KI48XE  
> nice op^SV5BYR^SV5BYR-7^H94^~
>
> -> 17:25:24 EA2CW PC11^10489770.0^9X4X^29-Nov-2021^1725Z^KI48XE  nice 
> op^SV5BYR^SV5BYR-7^H96^~
>
> -> 17:25:24 GB7DXG-1 PC92^EI7MRE^62720^D^^5UT1U^H95^
>
> <- 17:25:24 GB7RDX PC92^EI7MRE^62720^D^^5UT1U^H94^
>
> <- 17:25:24 EA2CW PC92^EI7MRE^62720^D^^5UT1U^H94^
>
> <- 17:25:24 ON0DXK-5 PC92^EI7MRE^62720^D^^5UT1U^H94^
>
> <- 17:25:24 VE7C
>
> Keith GU6EFB
>
> *From:*Dxspider-support <dxspider-support-bounces at tobit.co.uk> *On 
> Behalf Of *Dirk Koopman via Dxspider-support
> *Sent:* 29 November 2021 19:50
> *To:* Dxspider-Support <dxspider-support at dxcluster.org>
> *Cc:* Dirk Koopman <djk at tobit.co.uk>
> *Subject:* [Dxspider-support] 10Ghz+ spots
>
> Whilst I have a lot of sysop attention...
>
> Please could we look in our logs for this spot issued today.
>
>
> 29Nov2021 at 17:25:20 (chan) <- I GB7DJK 
> PC61^10489772.0^9X4X^29-Nov-2021^1725Z^KI48XE  nice 
> op^SV5BYR^SV5BYR-7^192.168.178.1^H27^~
>
>
> The original was a valid PC61 but it has gone to some other node 
> (probably to AR-C land) and come out as a PC11 with the WRONG QRG on 
> it. Just as bad as this is that there are some ops that are using 
> narrow band on 3cms (not to mention HF) and use fractions of KHz. That 
> isn't preserved either.
>
> Please would you do this (copy'n'paste should work):
>
> grepdbg  '<- I' 'PC[61]1' 9x4x '\^1048'
>
> 29Nov2021 at 15:39:33 (chan) <- I GB7DJK 
> PC61^10489772.0^9X4X^29-Nov-2021^1539Z^ 
> ^IK5ZAI^IK5PWJ-6^151.29.14.116^H8^~
> 29Nov2021 at 15:39:33 (chan) <- I GB7DJK 
> PC11^10489770.0^9X4X^29-Nov-2021^1539Z^ ^IK5ZAI^IK5PWJ-6^H95^~
> 29Nov2021 at 17:25:20 (chan) <- I GB7DJK 
> PC61^10489772.0^9X4X^29-Nov-2021^1725Z^KI48XE  nice 
> op^SV5BYR^SV5BYR-7^192.168.178.1^H27^~
> 29Nov2021 at 17:25:20 (chan) <- I GB7DJK 
> PC11^10489770.0^9X4X^29-Nov-2021^1725Z^KI48XE  nice 
> op^SV5BYR^SV5BYR-7^H93^~
>
> Thanks
>
> Dirk G1TLH
>
>
> _______________________________________________
> 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/20211130/14e789cb/attachment.htm>