A friend of mine from my amateur radio club, Yavapai Amateur Radio Club,
Prescott, AZ, is one of the ops on the Baker Island DXpedition. He has
lots of experience working the CQ World Wide CW Contest with the Voodoo
Contest Group in African and Middle Eastern countries. I'm really
looking forward to talking to him when he gets back to get feedback on
how things were on their end.
John, WB9VGJ
John L. Broughton
www.wb9vgj.us
wb9...@arrl.net
2silverhon...@gmail.com
On 6/30/2018 12:50 PM, Black Michael via wsjt-devel wrote:
I would like to approach this idea with some set of principles that
everybody can agree on...so here goes...
#1 Maximize QSO rate
#2 Minimize blind callers
Just those two principles are enough to say we should do whatever we
can to reduce blind callers which will also help to maximize QSO rate
as they are inversely relates (i.e. fewer blind means > qso rate).
Now...to take the logic to the extreme...if all callers were blind
then the QSO rate would be zero...quite obviously an undesirable
situation. As the % of blind callers reduces the QSO rate
increases...and the QSO rate is maximized when nobody is blind (notice
we're not considering band conditions here as that is not something we
can anything about).
So...given the two extremes which should we strive to support?
"good enough" is for horseshoes and hand grenades as the saying goes.
So why would we NOT try to minimize blind callers when it's an easy
software change to do so? This would have no changes on the fox
side...only the hounds....
de Mike W9MDB
On Saturday, June 30, 2018, 11:13:07 AM CDT, Bill Somerville
<g4...@classdesign.com> wrote:
Hi Mike,
we are not hear to determine how operators at a DXpedition site choose
to operate, we are not aware of conditions on the ground. If they feel
that they are getting optimum rates without calling CQ then that is
their choice. Remember that calling CQ from a rare entity can result
in a passband 100% full of pile up, they may have tried it and decided
it doesn't help the QSO rate.
73
Bill
G4WJS.
On 30/06/2018 17:05, Black Michael via wsjt-devel wrote:
But what about them receiving all these calls in the blind? Isn't
that going to interfere when they try to respond to people who can't
hear them?
Mike
On Saturday, June 30, 2018, 11:04:11 AM CDT, Bill Somerville
<g4...@classdesign.com> <mailto:g4...@classdesign.com> wrote:
On 30/06/2018 16:57, Black Michael via wsjt-devel wrote:
OK...so it appears the CQ every 5 trasnmissions is NOT enforced
unless Fox clicks the "More CQs" box.
We'd be a lot better off if this was always forced and Hounds were
restricted to only answer CQ's.
This explains why we don't see the CQ's and calling blind is
normally necessary (as long as you can see KH7Z that is).
if(m_tFoxTxSinceCQ>=m_foxCQtimeandui->cbMoreCQs->isChecked()){
de Mike W9MDB
Hi Mike,
it should be reasonable to assume that if the Baker Is. operators are
not enforcing regular CQ calls then they have plenty of callers to
keep the to-be-worked queue populated with more stations than Tx
slots and a QSO rate that is high.
------------------------------------------------------------------------------
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 <mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Virus-free. www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
------------------------------------------------------------------------------
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
------------------------------------------------------------------------------
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
