[Dxspider-support] Blocking FT8 spots

[Danilo Brelih]

Dirk thanks 

Thinking ahead from the user's point of view. Would it make sense to simplify "{\bFT\d|PSK\b}" with a user-friendly command like "NO_DIGIMODES" or similar? 

Commonly DIGI modes are = info FT4 or info FT8 or info PSK or info RTTY or info PACTOR or info AMTOR or info WSPR or info BPSK .... and others. 

REJ/SPOTS 9 info ("NO_DIGIMODES") and (freq 14071/14090 or freq 21074/21091 ...) 

The problem are contests having considerable band activity on CW where stations are also operating on DIGI frequencies. But this is another story where the contest program could be restricted so that it does not flooding bandmap frequencies e.g. 14071 where a significant number of stations are appearing on a single frequency. 

Either way with the command above we can reduce the number of DIGIMODES spots but we will not eliminate them completely which is not so bad at all. 

CUL, Dan S50U 

> Or without the spurious bracket:

> REJ/SPOTS 9 info {\bFT\d|PSK\b} and (freq 14071/14090 or freq 21074/21091 ...)

> This will only work on reasonably up to date mojo branch nodes. You can add more
> strings to test for, all separated by a '|' character.

> For master branches you have to use something similar to Danilo's suggestion but
> I would add brackets:

> REJ/SPOTS 9 (info FT4 or info FT8 or info PSK) and (freq 14071/14090 or freq
> 21074/21091).

> 73 Dirk G1TLH

> On 10/05/2022 22:13, Dirk Koopman via Dxspider-support wrote:

>> Try:

>> REJ/SPOTS 9 (info {\bFT\d|PSK\b} and (freq 14071/14090 or freq 21074/21091 ...)

>> On 10/05/2022 14:48, Danilo Brelih via Dxspider-support wrote:

>>> Joaquin via Dxspider-support je 10.5.2022 ob 14:43 napisal:

>>> I usually suggest using:

>>> REJ/SPOTS 9 info FT4 or info FT8 or info PSK

>>> The problem are DIGI spots without a rejected string in the comment field. In
>>> this case I would add:

>>> REJ/SPOTS 9 info FT4 or info FT8 or info PSK and (freq 14071/14090 or freq
>>> 21074/21091) ... etc for FT frequencies. The problem in this case is the freq
>>> overlap with other modes in frequency range. Does anyone see a better solution?

>>> CUL Dan, S50U

>>>> Mike,
>>>> The obvious would be:
>>>> rej/spot info FT8
>>>> 73 de Kin

>>>> El 10 may. 2022 14:34, Michael Walker via Dxspider-support
>>>> <dxspider-support at tobit.co.uk> escribió:

>>>>> Hi All

>>>>> Is there a user filter to easily block FT8 spots?

>>>>> I was trying reject things, but it was going well. :)

>>>>> Mike va3mw

>>> --
>>> Osti jarej!

>>> _______________________________________________
>>> Dxspider-support mailing list 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
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support

> _______________________________________________
> 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/20220511/f7caab1c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: undefined
Type: image/gif
Size: 354 bytes
Desc: not available
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20220511/f7caab1c/attachment-0001.gif>