On 30/03/2018 15:44, Gene Marsh wrote:
At first, I thought someone was pranking me.  Then, I saw it BEFORE I had 
transmitted.  In my example, I had not been on for 3 days.

I work FT8 approximately 10 hours a week, and approximately 10 hours of 
standing by on the program and radio.  In that time, 5-6 instances occur.  50% 
were good call signs, 50% were bogus.  ALL were properly formed and legitimate 
grid coords (but some were in the middle of nowhere).

If you know the issue, please email me!  Maybe I’m going crazy!

Hi Gene,

you have "Menu->Decode->Enable AP" checked. Please read this section of the WSJT-X User Guide:

http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.8.0.html#_ap_decoding

A priori decoding assumes parts of the candidate incoming messages using information already known and tries to construct messages containing that information. WSJT-X assumes you are waiting for CQ replies when you are not in a QSO (DX Call cleared) so it assumes your callsign might be part of an incoming message. If it can pull out a plausible message with a valid checksum after making that assumption it will show a decode. It also tags that decode to show it was obtained using AP information by appending a marker, in this case 'a2', it may also append a '?' if the decode is marginal even using AP.

If you make your WSJT-X main window a little wider you will see these appended markers (note the scroll bar at the bottom of the window). Of course you could also disable AP decoding but you would lose around 1.5% of useful decodes, that may not sound much but those 1.5% are the most interesting decodes, i.e. stations calling you.

WSJT-X v1.9 will stop considering AP type 2 decodes a few decodes after you stop calling, this should reduce the already low rate of false AP type 2 decodes to a very small one.

73
Bill
G4WJS.


------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to