George, I'm afraid I really don't like this suggestion. I, and many
others, find the machine computed SNR to be quite a useful piece of
information.
If the other station gives me a -20db SNR, then when I'm finally done, I
know why it took longer.
With it being machine computed, it's much more useful than the
ubiquitous 59 or 599 (or worse 5NN) report that so many contesters think
is useful. If that's all you're going to send, then perhaps we should
just all assume that's what we're going to get no matter how many
repeats it takes! Contest logging software shouldn't prefill that info
into the log! The whole point of having something that is a specific
contact variant is to have something you need to think about. You can't
work an HF contest and get any real idea how your antenna is working.
Gordon
WA9WTK
George J Molnar via wsjt-devel wrote:
Going back to my original suggestion - I do not seek to banish signal
reports for those that want them, certainly. Only set the -default-
VHF condition to grids-only QSOs. This would have the immediate
advantage of substantially untying the mess that crops up too often
between users in CM working those not in CM, or with different software.
In the case of R1 QSO practice, without judging the merits of the R1
Handbook, it would seem that in this case, the non-default condition
could be set to reports, just as all special operating conditions
contacts are treated as exceptions to the default.
European ops - I am very curious about the real world use here. If I
work you on 6m Es during the CQ Worldwide Contest, which requires just
a grid, is our contact valid? The rules state “Signal reports are not
required and should not be included in the log entry.” Do any of your
contests contacts count? I’m confused and would like to understand better.
Very 73,
*George J Molnar
College Park, Maryland*
*KF2T | FM19ma*
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
