"I also wonder if the ones complaining are using the older version of JTAlert
which tries to "guess" the TIME_ON from the 1st observation of the callsign
which works on a normal QSO but not when you're waiting for them at all"
I have not complained to anyone but I have had to track down multiple instances
of incorrect QSO time reporting that probably were caused by this problem. In
all cases I looked back thought the QSO decode records and found that the
reported QSO time correlated to a time when I had called the station but had
not completed a contact until a much later call. All seen with older versions
of JTAlert and WSJT-X. These errors can be detected from eQSL reports but
with LoTW the QSO is simply lost.
Any code that attempts to derive a QSO start time should also include a
reasonableness test on QSO duration.
73,
Andy k3wyc
------------------------------------------------------------------------------
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
