Russ --

Obviously the bogus JT65 decodes you have seen are related to your use of "Enable Averaging". You haven't answered my questions about optional decoder settings and the contents of your CALL3.TXT file. Best of all would be a sequence of *.wav files which, when opened in WSJT-X, would produce the bogus decode you wish would go away. When pursuing the sort of tests you have been making, it's important to always run with "Save All" enabled. Without such supporting information, there's not much we can do to help.

        -- Joe

On 12/19/2018 9:29 AM, Russ wrote:
Joe, Bill, Charles, and all.  The problem I reported (many instances of old
contact information being shown as decodes and similar issues, in JT65) was
eliminated by unchecking the 'Enable Averaging' box under decoding.  When I
re-enable averaging the problem returns after a bit of usage.

I have seen one or two instances of this happening when averaging was
disabled, but it only seems to happen when averaging has recently been used
and then turned off.  I always click the 'Clear Avg' button after disabling
averaging.  Also I am not sure if I reported this before, but when the bogus
decodes (while averaging) show up, there is nothing at all shown in the
averaging window (F7).

Thanks for your help.

73, Russ K2TXB

-----Original Message-----
From: Joe Taylor <j...@princeton.edu>
Sent: Saturday, December 15, 2018 1:31 PM
To: WSJT software development <wsjt-devel@lists.sourceforge.net>
Subject: Re: [wsjt-devel] Version 2.0 issues with JT65

Russ --

You're calling some displays "bogus decodes", and evidently they are
bogus.  But you appear to have all the knobs turned up to maximum
aggressiveness.  Most if the displayed messages are flagged with "?",
which you may interpret as "caveat emptor", or some such.

Probably you saved "KF4FCO EM70" in your callsign database.  How many
other calls are there?

The message "CQ KF4FCO EM70     OO" is clearly nonsense, so you could
reject it out of hand.

When we've had time to pay careful attention to some of these anomalies,
and especially when more people are using WSJT-X for their EME
operations, we'll clean up some of these peculiarities.  In the
meantime, you'll need to use some common sense if you want to use very
aggressive decoding settings.

        -- Joe, K1JT

On 12/15/2018 13:04, Russ wrote:
Bill, Joe, Charlie, whoever is interested; here is a new wrinkle to the
problem.

I was operating MSK144 on 2 meters.  Got done and decided to switch to
JT65
to see if the false decodes would start to happen.  It didn't right
away, so
went away for a while leaving it running.  When I got back I had two
decodes
showing in the average box: " CQ KF4FCO EM70".  This was the last good
decode that I got on MSK144 !  I DID click to Clear Averages before this
happened.  Here is all.txt.  You can see the four good decodes and my CQ
around 1530, and then two bogus decodes of the same call, at 1743, some
time
after I had switched to JT65.  While I was typing this a local started
up
calling CQ on the frequency I am on.  And now there are six instances of
the
same decode showing on the JT65 screen.

1523 -30  2.0 1327 ## CQ KF4FCO EM70     OO               O d20
1527 -30  6.1 1550 #  CQ KF4FCO EM70                      ? d20
1539 -30  4.7 1598 #  CQ KF4FCO EM70                      ? d20
1544 -30  6.2 1436 #  CQ KF4FCO EM70                      ? d20
181215_154645  Transmitting 144.15 MHz  MSK144:  CQ K2TXB FN20

1743 -30  6.2 1368 #  CQ KF4FCO EM70                      ? d20
1748 -30  6.0 1595 #  CQ KF4FCO EM70                      ? d20

And Joe suggested checking the average window.  For the period in
question
it had only one entry:

. 1727  -1.2 -1.09  1399 *

That is 16 minutes before the first bogus decode and does not appear to
be
related.

73, Russ K2TXB



_______________________________________________
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



_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to