Thanks to all for your informative comments on frequencies and operating
procedures for FT8 under extreme pileup conditions.
We need more such input. Preferably some of it should come from
operators who actually plan to use FT8 in a major DXpedition. The most
useful input will surely come from operators with significant FT8
experience as well as experience running (or breaking through) big
pileups. Given sufficient time, we can add program features that will
make things better for those on both ends of the pileup, and we'll be
happy to work toward that end.
We could design a fully automatic system that would maximize a
DXpedition's FT8 QSO rate. It would probably have one set of operating
rules for the DXpedition station, a different set for everyone else.
Reception at the DX location would cover a relatively wide band (say
Ned's 30 kHz needed for RTTY), and would decode all adequate signals
found therein, almost simultaneously. It might choose callers at
random, perhaps jumping around in frequency. Or, to avoid an "arms
race" in high power, it might choose the weakest decoded signal, or a
signal chosen at random among all decodes with S/N <-10 dB, or some
such. Yes, in principle the Dxped could even work more than one station
at a time, using Alex's highly linear transmitter. Operators would have
nothing to do beyond starting the program, watching the QSOs accumulate,
and (for the home operators) hoping to be selected.
Of course, it would be no fun (for anyone but the programmer?) to watch
this fully automated mayhem. I guess we want, instead, a system that
works well, gives everyone a chance, rewards operating skills and
accumulated experience... and also produces a high QSO rate.
Ned, what were your average and maximum hourly rates with RTTY VP8STI
and VP8SGI? What are these numbers for high scorers in RTTY contests?
-- Joe, K1JT
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
