<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">More on filtering.<br>
I achieve much more successful (if not ideal 😎) filtering if I
separate the rejection of digi SPOTS with two separate rules. The
first rule is based on the search string in the comment field (ft,
psk, rtty, fsk, jt, js) and the second is based on the frequency.
In this case my SPOTS filter looks like:</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">S50U : spots<br>
filter2 reject info {\bft\d|psk\d|rtty\d|fsk\d|jt\d|js\b}<br>
filter3 reject freq 1838/1842 or freq 3573/3590 or freq 7040/7048
or freq 7074/7078 or freq 14071/14090 or freq 21074/21140 or freq
28070/28120<br>
filter4 accept freq contesthf/cw and by_zone 14,15,16</div>
<br>
<div class="moz-cite-prefix">Maybe Dirk has an answer why the rule
separated by AND doesn't work as I write in my previous post?</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">> filter1 reject info
{\bft\d|psk\d|rtty\d|fsk\d|jt\d|js\b} and ( freq 1838/1842 or freq
3573/3590 or freq 7040/7048 or freq 7074/7078 or freq 14071/14090
or freq 21074/21140 or freq 28070/28120 )</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">73 Dan S50U</div>
<div class="moz-cite-prefix"><br>
</div>
<blockquote type="cite"
cite="mid:b608c9a3-9560-6da0-1e37-b336e4889832@siol.net">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">Hi</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">If it's in anyone's interest. I would
use the following filter rule for HF CW contests on my latest
DXSpider V1.57 build 441. What I want to achieve is:<br>
<br>
with SPOTS:<br>
- I reject DIGI mode spots<br>
- I accept all spots on CONTESTHF bands on CW portion of the
bands and rejects all others<br>
- I accept all spots generated by spotting callsign within the
CQ zone 14,15,16 and rejects all others<br>
<br>
with RBN:<br>
- I accept all rbn spots on CONTESTHF bands on CW portion of the
bands<br>
- I accept all rbn spots generated by spotting skimmer callsign
within the CQ zone 15 and rejects all others<br>
- I accept only rbn spots heard from more then 2 skimmer
stations, i.e. Q is greater then 2.<br>
<br>
</div>
<div class="moz-cite-prefix">S50U : spots<br>
filter1 reject info {\bft\d|psk\d|rtty\d|fsk\d|jt\d|js\b} and (
freq 1838/1842 or freq 3573/3590 or freq 7040/7048 or freq
7074/7078 or freq 14071/14090 or freq 21074/21140 or freq
28070/28120 )<br>
filter2 accept freq contesthf/cw and by_zone 14,15,16<br>
S50U : rbn<br>
filter1 accept on contesthf/cw and by_zone 15 and info
{q:[2-9]}</div>
<div class="moz-cite-prefix">S50U de S50CLX 21-May-2022 1110Z
2.4481 dxspider ><br>
<br>
The interesting thing about all this is that some DIGI spots
still get past the filters rule. I can't find a pattern, but it
works for me that the rule doesn't dump spots where the filter
doesn't find the string we're looking for in the comment field.
If blank then spots are rejected by from/to freq selection.</div>
<div class="moz-cite-prefix">Dirk what do you think?</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Some examples where the above filter
does not dump SPOTS by reject info rule correctly. Seems only
spots with some info in comment filed are passed on, empty field
cut them successfully!</div>
<div class="moz-cite-prefix"><br>
<pre>R1CAV 14074.9 HG0WFF 0657Z 21 TNX 73
OK2TRN 14080.0 +IQ8BV 0851Z 21 GIRO D???ITALIA AWD TNX
IU5AXT 14085.0 IQ5QO/IS0 0920Z 21 IFF183 DLI IS0-102 correct reference number
DF6JF 14074.0 +SV1SSL 0920Z 21 tu 73 gl op at DL1640Y
EW6AS 21076.0 +LZ2KTS 0656Z 21 tnx QSO
PA3GPU 21074.0 +EA5MR 0816Z 21 CDM EA*
IZ2UTE 21074.0 EW1ZR 0821Z 21 73
DJ7YP 21076.2 +9K2NO 0852Z 21 tnx good dx
IZ3ERM 28075.2 +VK7NET 0628Z 21 tnx
OZ1MFP 28074.0 +4S7VG 0704Z 21 JO55SK<>MJ96WW cq
S53R 28080.0 +9N7AA 0730Z 21 FH calll 1000Hz+
</pre>
73 Dan, S50U<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<blockquote type="cite"
cite="mid:f1a30991-a505-1d03-0e74-0a302fab226b@tobit.co.uk">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div class="moz-cite-prefix">Or without the spurious bracket:<br>
<br>
REJ/SPOTS 9 info {\bFT\d|PSK\b} and (freq 14071/14090 or freq
21074/21091 ...)<br>
<br>
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.<br>
<br>
For master branches you have to use something similar to
Danilo's suggestion but I would add brackets:<br>
<br>
REJ/SPOTS 9 (info FT4 or info FT8 or info PSK) and (freq
14071/14090 or freq 21074/21091).<br>
<br>
73 Dirk G1TLH<br>
<br>
On 10/05/2022 22:13, Dirk Koopman via Dxspider-support wrote:<br>
</div>
<blockquote type="cite"
cite="mid:7bece1b1-7202-000b-0002-93e0377958fa@tobit.co.uk">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div class="moz-cite-prefix">Try:<br>
<br>
REJ/SPOTS 9 (info {\bFT\d|PSK\b} and (freq 14071/14090 or
freq 21074/21091 ...)<br>
<br>
<br>
On 10/05/2022 14:48, Danilo Brelih via Dxspider-support
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:b2f1a9f0-450d-617c-d500-65fcb504324a@siol.net">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div class="moz-cite-prefix">Joaquin via Dxspider-support je
10.5.2022 ob 14:43 napisal:</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I usually suggest using:</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">REJ/SPOTS 9 info FT4 or info
FT8 or info PSK<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">The problem are DIGI spots
without a rejected string in the comment field. In this
case I would add:</div>
<br>
<div class="moz-cite-prefix">
<div class="moz-cite-prefix">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?</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">CUL Dan, S50U</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<blockquote type="cite"
cite="mid:c1ec9d7c-e7fd-4f91-a100-7dfb9618ce50@email.android.com">
<meta http-equiv="content-type" content="text/html;
charset=UTF-8">
<div dir="auto">
<div>
<pre dir="ltr" style="max-height: 999999px; font-size: 24px; line-height: 32px; background-color: rgb(248, 249, 250); border: none; padding: 10px 0.14em 10px 0px; margin-top: 0px; margin-bottom: 0px; font-family: "google sans", roboto, "helvetica neue", arial, sans-serif; width: 361.091px; white-space: pre-wrap; color: rgb(32, 33, 36);"><span style="max-height:999999px">Mike, </span></pre>
<pre dir="ltr" style="max-height: 999999px; font-size: 24px; line-height: 32px; background-color: rgb(248, 249, 250); border: none; padding: 10px 0.14em 10px 0px; margin-top: 0px; margin-bottom: 0px; font-family: "google sans", roboto, "helvetica neue", arial, sans-serif; width: 361.091px; white-space: pre-wrap; color: rgb(32, 33, 36);"><span style="max-height:999999px">The obvious would be:
rej/spot info FT8</span></pre>
<pre dir="ltr" style="max-height: 999999px; font-size: 24px; line-height: 32px; background-color: rgb(248, 249, 250); border: none; padding: 10px 0.14em 10px 0px; margin-top: 0px; margin-bottom: 0px; font-family: "google sans", roboto, "helvetica neue", arial, sans-serif; width: 361.091px; white-space: pre-wrap; color: rgb(32, 33, 36);">73 de Kin</pre>
<br>
<div class="gmail_extra"><br>
<div class="gmail_quote">El 10 may. 2022 14:34,
Michael Walker via Dxspider-support <a
class="moz-txt-link-rfc2396E"
href="mailto:dxspider-support@tobit.co.uk"
moz-do-not-send="true"><dxspider-support@tobit.co.uk></a>
escribió:<br type="attribution">
<blockquote class="quote" style="margin:0 0 0
.8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div dir="ltr">
<div style="font-family:'arial' , 'helvetica'
, sans-serif">Hi All</div>
<div style="font-family:'arial' , 'helvetica'
, sans-serif"><br>
</div>
<div style="font-family:'arial' , 'helvetica'
, sans-serif">Is there a user filter to
easily block FT8 spots?</div>
<div style="font-family:'arial' , 'helvetica'
, sans-serif"><br>
</div>
<div style="font-family:'arial' , 'helvetica'
, sans-serif">I was trying reject things,
but it was going well. :)</div>
<div style="font-family:'arial' , 'helvetica'
, sans-serif"><br>
</div>
<div style="font-family:'arial' , 'helvetica'
, sans-serif">Mike va3mw</div>
<div style="font-family:'arial' , 'helvetica'
, sans-serif"><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<div class="moz-signature">-- <br>
<a href="http://www.hervardi.com/osti_jarej.php">Osti jarej!</a></div>
</body>
</html>