Difference between revisions of "Some Practice Examples"

From DXSpider Documentation Wiki
Jump to: navigation, search
(New page: �[1m9. Some Practice Examples�[0m The proceeding sections have discussed the basics of DXSpider filters. The following are some examples utilizing basic filters and some not so b...)
 
 
Line 1: Line 1:
�[1m9.  Some Practice Examples�[0m
+
=Some Practice Examples=
  
The proceeding sections have discussed the basics of DXSpider filters.
+
The proceeding sections have discussed the basics of DXSpider filters.  The following are some examples utilizing basic filters and some not so basic combination filters.
  The following are some examples utilizing basic filters and some not
+
so basic combination filters.
+
  
 +
Let's say you don't want to see any of those 6m, 2m, or 220 spots.
  
  Let's say you don't want to see any of those 6m, 2m, or 220 spots.
+
  reject/spot 0 on uhf
 
+
 
+
      reject/spot 0 on uhf
+
 
+
 
+
As a good stand alone contest filter ...
+
  
 +
As a good stand alone contest filter ...
  
 
  accept/spot on contesthf/<mode> where mode is either CW, SSB, or RTTY
 
  accept/spot on contesthf/<mode> where mode is either CW, SSB, or RTTY
  
 +
'''Note:''' since a slot number is not included slot 1 is assumed.
  
Note: since a slot number is not included slot 1 is assumed.
+
It's a CW contest weekend so you don't want to see any WARC band or SSB spots.
 
+
 
+
It's a CW contest weekend so you don't want to see any WARC band or
+
SSB spots.
+
 
+
 
+
      accept/spots 0 on contesthf/cw
+
 
+
 
+
It's the same weekend, but you also don't want to see any US or
+
Canadian spots, or any rtty and data spots that are included in the CW
+
portion of the bands.  Any of the following will accomplish the same
+
result:
+
 
+
 
+
      reject/spot 0  not on contesthf/cw
+
      reject/spot 1 on contesthf/data
+
      reject/spot 2 call_dxcc w,ve
+
 
+
      or
+
 
+
      accept/spot 0 on contesthf/cw and not (call_dxcc 226,197 or on contesthf/data)
+
 
+
      or
+
 
+
      accept/spot 0 on contesthf/cw and not (call_dxcc w,ve or on contesthf/data)
+
 
+
 
+
The following two discussions are from the Administrator Manual and
+
are good "textbook" examples:
+
 
+
 
+
      rej/spot on hf/cw
+
      acc/spot on 0/30000
+
      acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
+
  
 +
accept/spots 0 on contesthf/cw
  
Note that accept and reject can be abbreviated. Also, the first filter
+
It's the same weekend, but you also don't want to see any US or Canadian spots, or any rtty and data spots that are included in the CW portion of the bands.  Any of the following will accomplish the same result:
has not been specified with a number. This will automatically be
+
assumed to be number 1.  In this case, we have said to reject all HF
+
spots in the CW section of the bands but accept all others at HF. Also
+
accept anything in VHF and above that is spotted in or by operators in
+
  the zones 14, 15 and 16. Each filter slot actually has a 'reject' rule
+
slot and an 'accept' rule slot. The reject rule slot is executed
+
BEFORE the accept rule slot.
+
  
 +
reject/spot 0  not on contesthf/cw
 +
reject/spot 1 on contesthf/data
 +
reject/spot 2 call_dxcc w,ve
  
It was mentioned earlier that after a reject test that doesn't match,
+
or
the default for following tests is 'accept', the reverse is true for
+
'accept'. In the example what happens is that the reject is executed
+
first, any non hf/cw spot is passed to the accept line, which lets
+
through everything else on HF.  The next filter line lets through just
+
VHF/UHF spots from EU.
+
  
 +
accept/spot 0 on contesthf/cw and not (call_dxcc 226,197 or on contesthf/data)
  
If you set a reject filter like this ...
+
or
  
 +
accept/spot 0 on contesthf/cw and not (call_dxcc w,ve or on contesthf/data)
  
      reject/spots on hf/cw
+
The following two discussions are from the Administrator Manual and are good "textbook" examples:
  
 +
rej/spot on hf/cw
 +
acc/spot on 0/30000
 +
acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)
  
Then you will get everything except HF CW spots. You could make this
+
Note that accept and reject can be abbreviated. Also, the first filter has not been specified with a number. This will automatically be assumed to be number 1. In this case, we have said to reject all HF spots in the CW section of the bands but accept all others at HF. Also accept anything in VHF and above that is spotted in or by operators in the zones 14, 15 and 16. Each filter slot actually has a 'reject' rule slot and an 'accept' rule slot. The reject rule slot is executed BEFORE the accept rule slot.
single filter even more flexible. For example, if you are interested
+
in IOTA and will work it on CW even though normally you are not
+
  interested in CW, then you could say ...
+
  
 +
It was mentioned earlier that after a reject test that doesn't match, the default for following tests is 'accept', the reverse is true for 'accept'. In the example what happens is that the reject is executed first, any non hf/cw spot is passed to the accept line, which lets through everything else on HF.  The next filter line lets through just VHF/UHF spots from EU.
  
      reject/spots on hf/cw and not info iota
+
If you set a reject filter like this ...
  
 +
reject/spots on hf/cw
  
But in that case you might only be interested in iota and say,
+
Then you will get everything except HF CW spots. You could make this single filter even more flexible. For example, if you are interested in IOTA and will work it on CW even though normally you are not interested in CW, then you could say ...
  
 +
reject/spots on hf/cw and not info iota
  
      accept/spots not on hf/cw or info iota
+
But in that case you might only be interested in iota and say,
  
 +
accept/spots not on hf/cw or info iota
  
which achieves exactly the same thing.  Note that since slot numbers
+
which achieves exactly the same thing.  Note that since slot numbers were not used, slot 1 is assumed.
were not used, slot 1 is assumed.
+

Latest revision as of 14:43, 18 December 2008

Some Practice Examples

The proceeding sections have discussed the basics of DXSpider filters. The following are some examples utilizing basic filters and some not so basic combination filters.

Let's say you don't want to see any of those 6m, 2m, or 220 spots.

reject/spot 0 on uhf

As a good stand alone contest filter ...

accept/spot on contesthf/<mode> where mode is either CW, SSB, or RTTY

Note: since a slot number is not included slot 1 is assumed.

It's a CW contest weekend so you don't want to see any WARC band or SSB spots.

accept/spots 0 on contesthf/cw

It's the same weekend, but you also don't want to see any US or Canadian spots, or any rtty and data spots that are included in the CW portion of the bands. Any of the following will accomplish the same result:

reject/spot 0  not on contesthf/cw
reject/spot 1 on contesthf/data
reject/spot 2 call_dxcc w,ve

or

accept/spot 0 on contesthf/cw and not (call_dxcc 226,197 or on contesthf/data)

or

accept/spot 0 on contesthf/cw and not (call_dxcc w,ve or on contesthf/data)

The following two discussions are from the Administrator Manual and are good "textbook" examples:

rej/spot on hf/cw
acc/spot on 0/30000
acc/spot 2 on 50000/1400000 and (by_zone 14,15,16 or call_zone 14,15,16)

Note that accept and reject can be abbreviated. Also, the first filter has not been specified with a number. This will automatically be assumed to be number 1. In this case, we have said to reject all HF spots in the CW section of the bands but accept all others at HF. Also accept anything in VHF and above that is spotted in or by operators in the zones 14, 15 and 16. Each filter slot actually has a 'reject' rule slot and an 'accept' rule slot. The reject rule slot is executed BEFORE the accept rule slot.

It was mentioned earlier that after a reject test that doesn't match, the default for following tests is 'accept', the reverse is true for 'accept'. In the example what happens is that the reject is executed first, any non hf/cw spot is passed to the accept line, which lets through everything else on HF. The next filter line lets through just VHF/UHF spots from EU.

If you set a reject filter like this ...

reject/spots on hf/cw

Then you will get everything except HF CW spots. You could make this single filter even more flexible. For example, if you are interested in IOTA and will work it on CW even though normally you are not interested in CW, then you could say ...

reject/spots on hf/cw and not info iota

But in that case you might only be interested in iota and say,

accept/spots not on hf/cw or info iota

which achieves exactly the same thing. Note that since slot numbers were not used, slot 1 is assumed.