Of all the DT drifeters I saw not one was running JTAlert.
Then again highlighting the DT values > 0.5 seconds might be a better solution
though once you get your clock set the I find the highlighting irritating as
all highlight should be calling your attention to something.
And based on watching FD today I think 80% (4 of 5) > 0.5 second might be the
good target.
Mike.
On Sunday, June 23, 2019, 03:10:58 PM CDT, August Treubig
<atreu...@sbcglobal.net> wrote:
JTAlert already does that. Highlights in red.
AugAG5AT
Sent from my iPad
On Jun 23, 2019, at 2:04 PM, Gary Hinson <g...@isect.com> wrote:
Instead of “Your clock is off” (which, to some, may mean “Your clock is turned
off”) I suggest “Your clock is wrong” or better still the action-oriented
“Check your clock”.
And the proposed 3 out of 5 decodes being more than half a second wrong risks
triggering the message far too often when the band is busy, especially during
events such as field day and DXpeditions when a greater proportion of ops are
probably using temporary setups without atomic clock references. I think a
statistical test would be more appropriate, although I’m not sure which one
(ask a statistician!).
Another approach would be simply to highlight DT values that are more than,
say, 1 second wrong in the decode panes (e.g. with red or orange backgrounds
for minus and plus DT values), and leave the ops to notice the slew of reds or
oranges and figure out what’s going on. This has the advantage that, if we are
reasonably sure of our own clocks, we might notice and maybe send a message to
other stations whose DT values are highlighted.
73
Gary ZL2iFB
From: Black Michael via wsjt-devel <wsjt-devel@lists.sourceforge.net>
Sent: 24 June 2019 00:27
To: WSJT Software Development <wsjt-devel@lists.sourceforge.net>
Cc: Black Michael <mdblac...@yahoo.com>
Subject: [wsjt-devel] Field Day time problem
I've seen about 2 dozen clubs doing Field Day where their clocks are off.
We need to provide an indication in WSJT-X when clocks are off like this.
With concurrence I can do a patch for this....my idea is this.
At least 5 decodes where 60% or more > 0.5 seconds is an indication of bad
timing.
A message would be put in the Rx Frequency window "Your clock is off...see
help". With appropriate references in the Help to search "your clock is off"
and time solutions.
This doesn't cover the case where their clock is way off as they won't see any
decodes. The only solution for that would be doing a time query from a known
source and I don't think we want to go that route.
de Mike W9MDB
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
