[Dxspider-support] (mojo, currently) SH/DX command
Dirk Koopman
djk at tobit.co.uk
Tue Jun 2 22:44:25 CEST 2020
Which, of course, doesn't explain why the results are different. That's
because I left something in sh/dx that I should have taken out because I
did this:
['freq', 'r', 0, 0, \&decodefreq],
['on', 'r', 0, 0, \&decodefreq],
['call', 'c', 1],
['info', 't', 3],
['spotter', 'c', 4],
['by', 'c', 4],
['call_dxcc', 'nc', 5],
['by_dxcc', 'nc', 6],
['origin', 'c', 7, 9],
['call_itu', 'ni', 8],
['itu', 'ni', 8],
['call_zone', 'nz', 9],
['zone', 'nz', 9],
['by_itu', 'ni', 10],
['byitu', 'ni', 10],
['by_zone', 'nz', 11],
['byzone', 'nz', 11],
['call_state', 'ns', 12],
['state', 'ns', 12],
['by_state', 'ns', 13],
['bystate', 'ns', 13],
['ip', 'c', 14],
Which is the definitive Filter keyword list for spots.
I think they match (albeit not quite in the same order at the beginning).
I've taken it out. Update and it will just work. No need to restart.
Dirk
On 02/06/2020 21:26, Dirk Koopman via Dxspider-support wrote:
> All the xxx_yyyy commands should work with or without the '_'.
>
> sh/dx 15 by_zone 14,15
> G1TLH-2 de GB7TLH 2-Jun-2020 2021Z dxspider >
> 7074.0 RV9XV 2-Jun-2020 2021Z FT8 -20dB from LP63 2155Hz
> <G0FEA>
> 14253.3 LY5A 2-Jun-2020 2020Z
> <K1JLC>
> 18099.0 ES1KK 2-Jun-2020 2020Z FT8 tu 73
> <DK2CC>
> 144221.0 I3MEK 2-Jun-2020 2020Z CQ IAC
> <IU0CNI>
> 14250.0 N6M 2-Jun-2020 2020Z special event
> <KF7UOV>
> 14285.0 EA8JK 2-Jun-2020 2019Z USB
> <CT7AUQ>
> 14200.0 8P6N 2-Jun-2020 2019Z
> <8P6NW>
> 14276.0 IU3BTY 2-Jun-2020 2019Z
> <K2TRD>
> 14076.3 HP2DFA 2-Jun-2020 2019Z FT8 tnx
> <NA5J>
> 7145.0 EA8BWW 2-Jun-2020 2018Z IO62SH<>IL18 SSB
> <EI5KG>
> 7172.0 EP2AMS 2-Jun-2020 2018Z ???? ????????????????????
> <R4DI>
> 14025.0 DL2OE 2-Jun-2020 2018Z tks fb qso Mike
> <PY2UDB>
> 14222.0 A41CK 2-Jun-2020 2017Z 57 in Bahamas audio testing
> <C6AFV>
> 14015.0 LZ1KFM 2-Jun-2020 2016Z
> <KF0IR>
> 3543.0 IK1MOP 2-Jun-2020 2016Z 16 COTA CW
> <IK1MOP>
> sh/dx 15 byzone 14,15
> G1TLH-2 de GB7TLH 2-Jun-2020 2021Z dxspider >
> 7074.0 RV9XV 2-Jun-2020 2021Z FT8 -20dB from LP63 2155Hz
> <G0FEA>
> 18099.0 ES1KK 2-Jun-2020 2020Z FT8 tu 73
> <DK2CC>
> 144221.0 I3MEK 2-Jun-2020 2020Z CQ IAC
> <IU0CNI>
> 14285.0 EA8JK 2-Jun-2020 2019Z USB
> <CT7AUQ>
> 7145.0 EA8BWW 2-Jun-2020 2018Z IO62SH<>IL18 SSB
> <EI5KG>
> 3543.0 IK1MOP 2-Jun-2020 2016Z 16 COTA CW
> <IK1MOP>
> 144174.0 SM6BFE 2-Jun-2020 2016Z KP02OJ<TR>JO68DQ tnx gl
> <OH6KTL>
> 7074.0 JA6GCE 2-Jun-2020 2015Z Ea3dkp
> <EA3DKP>
> 144200.0 IK1WVR 2-Jun-2020 2015Z hrd
> <IK8BIZ>
> 7129.0 LU1NAF 2-Jun-2020 2014Z CQ ....
> <YT1KC>
> 144260.0 M0LMK 2-Jun-2020 2013Z Thanks fot QSO 73"?????
> <PA5AB>
> 435000.0 IW3HRT 2-Jun-2020 2013Z JO32HN<SAT>JN55 via sat rs
> 4<PD4HDB>
> 7090.0 EA5FHK 2-Jun-2020 2012Z 2ES HOMENAJE NUESTRAS FIESTA
> <EA5JN>
> 144290.0 SM2OXB 2-Jun-2020 2012Z KP02PL<TR>JP93WN CQ
> <OH6PA>
> 144206.0 GM3SEK 2-Jun-2020 2012Z IO81WO<>IO73SR 73 contest
> <2E0OUT>
>
> This is the current list of "standard" keyword / value pairs from
> sh/dx . I may have missed one...
>
> if (grep {lc $f eq $_} qw(on freq call info spotter by call_dxcc
> by_dxcc bydxcc origin call_itu itu call_zone zone byitu by_itu by_zone
> byzone call_state state bystate by_state ip) ) {
>
> Are you sure you are on the absolute latest? I had to have three goes
> getting them "all" in.
>
> 73 Dirk
>
> On 02/06/2020 20:34, Danilo Brelih via Dxspider-support wrote:
>>
>> Thanks Dirk
>>
>> Hardly found 'sh/dx 15 byzone 14,15' working instead 'sh/dx 15
>> by_zone 14,15' from sh/dx help commands directions?
>>
>> Dan S50U
>>
>>
>>
>>> After quite a lot of messing around, I (think) have finished
>>> converting sh/dx queries from old style, limited, syntax to new
>>> style, Filter style syntax with a small bonus. So you can now use
>>> 'not' 'and' 'or' and brackets '(' and ')' in your sh/dx queries.
>>> There may still be some corners that I haven't covered - if there
>>> are - please report them.
>>>
>>> The small bonus is that it is now possible to use perl regexes in
>>> places where that makes sense. Practically that means "sh/dx info"
>>> queries. Regexes are perl regular expressions enclosed in '{' and '}'.
>>>
>>> For instance, for the FT8 phobic, one could use 'sh/dx not info
>>> {ft[48])'. Incidentally, that sh/dx expression can be used in an
>>> 'accept/spot' as in 'acc/spot not info {ft[48]}', but would be
>>> better done as 'rej/spot info {ft[48]}' (i.e. the same sh/dx query
>>> but without the 'not' :-).
>>>
>>> You will need to restart the node after update.
>>>
>>> Dirk G1TLH
>>>
>> --
>> Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
>> http://padgura.poglej.info
>>
>> _______________________________________________
>> 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/20200602/878aaee2/attachment-0001.htm>
More information about the Dxspider-support
mailing list