[Dxspider-support] contesthf/cw

[Kin]

There has only been one request for frequency/band ranges. Normally it is not necessary to filter by frequency. 
As you said, you can select by RBN type and if you want by tags in the case of digital modes. This is how I use it.
 
Kin
 
 
EA3CV-2 dxcluster.cronux.net 7300
http://clustermap.cronux.net/map.html
 
 
De: Rudy Bakalov <r_bakalov at yahoo.com> 
Enviado el: jueves, 21 de noviembre de 2024 14:01
Para: Kin <ea3cv at cronux.net>
CC: The DXSpider Support list <dxspider-support at tobit.co.uk>; s50u at s50e.si; The DXSpider Support list <dxspider-support at dxcluster.org>
Asunto: Re: [Dxspider-support] contesthf/cw
 
Sorry, I am still unsure what the strategy is. More specifically, I don’t understand the logic of linking frequency to mode, especially during a contest. You can have CW, FT8/4, and CW spots in the same frequency range. The authoritative source of mode is RBN and the spot itself, not the cluster.
 
If I want CW spots, I tell the cluster I want CW spots and don’t want RTTY and FT8/4; then the cluster only passes spots that come from RBN as labeled as CW.
 
What am I missing? Is DXS ignoring the mode label in the spot itself?
 
Rudy N2WQ
 
Sent using a tiny keyboard.  Please excuse brevity, typos, or inappropriate autocorrect.
 



On Nov 21, 2024, at 7:13 AM, Kin <ea3cv at cronux.net> wrote:

Hi Rudy,
 
I think it is not necessary to use the one frequency or range in RBN, unless you are looking for something very specific. 
 
In Dan's case, as it is a contest, the ideal is to use the band labels to eliminate the ones that are not used in the contest.
If only SSB were that easy ....
 
73 de Kin EA3CV
 
 
EA3CV-2 dxcluster.cronux.net 7300
http://clustermap.cronux.net/map.html
 
 
De: Rudy Bakalov <r_bakalov at yahoo.com> 
Enviado el: jueves, 21 de noviembre de 2024 12:24
Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
CC: s50u at s50e.si; The DXSpider Support list <dxspider-support at dxcluster.org>; Kin <ea3cv at cronux.net>; The DXSpider Support list <dxspider-support at tobit.co.uk>
Asunto: Re: [Dxspider-support] contesthf/cw
 
I currently run a CC Cluster node and considering migrating to DXS so this discussion is very educational to me.
 
The question that’s on my mind is why bother with frequency segments at all? RBN spots already arrive with the appropriate tag- CW, RTTY, FT4, or FT8. So why use frequency instead of the spot tag?
 
Rudy N2WQ
 
Sent using a tiny keyboard.  Please excuse brevity, typos, or inappropriate autocorrect.
 



On Nov 21, 2024, at 1:57 AM, Kin via Dxspider-support <dxspider-support at tobit.co.uk> wrote:

Mornig Dan,
 
If we select a band in RBN, it will be complete, which is in your interest because you know that in the contests, the segments are lengthened, and in the case of RBN CW you are not influenced by anything that is not CW in the whole band. 
 
Kin EA3CV
 
 
EA3CV-2 dxcluster.cronux.net 7300
http://clustermap.cronux.net/map.html
 
De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Danilo Brelih via Dxspider-support
Enviado el: miércoles, 20 de noviembre de 2024 21:56
Para: 'The DXSpider Support list' <dxspider-support at dxcluster.org>
CC: Danilo Brelih <s50u at s50e.si>
Asunto: Re: [Dxspider-support] contesthf/cw
 
Kin je 20.11.2024 ob 20:43 napisal:
Then I would apply an acc/rbn filter on 10m,15m,20m,40m,80m
Kin RR. It might be even better to define each band separately with a frequency range, example:
S50U : rbn
 filter1 accept by_zone 14,15,16,20 and ( freq 1810/2000 or freq 3500/3600 or freq 7000/7100 or freq 14000/14100 or freq 21000/21100 or freq 28000/28100 )
Am I open to any better approaches? 🙂
CUL Dan
-- 
 <https://s50clx.infrax.si> S50CLX DX Cluster
_______________________________________________
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/20241121/16913da0/attachment-0003.htm>