Re: [wsjt-devel] Possible bug WSJT-X 2.0 FT8 F/H mode

Mon, 24 Dec 2018 16:30:00 -0800 


> On Dec 24, 2018, at 5:11 PM, Martin Davies G0HDB <[email protected]> 
> wrote:
> 
> On 24 Dec 2018 at 9:13, John Becker wrote:
> 
>> I'm running WSJT-X v2.0 on a Windows 10 Pro (1803 update) computer.
>> 
>> On Saturday, HV0A was running F/H mode on 3567 with a large number of 
>> callers. I noticed strange behavior as follows with annotated excerpts 
>> from my all.txt file:
> 
> [Snipped]
> 
>> If desired, I can send the entire 377 line session from my all.txt file.
>> 
>> The fact that re-starting the program temporarily fixed this problem 
>> indicates to me that this was not a case of MI0KOA also running F/H mode 
>> as Fox on the same frequency. Note that it started right after MI0KOA 
>> made his QSO. Strange!
>> 
>> Was anyone else seeing this?
>> 
>> 73,
>> John, K9MM
> 
> Yes, I noticed it too around the time (232315z on 2018-12-22) I worked HV0A 
> on 80m 
> although I didn't try restarting WSJT-X to see if the 'issue' disappeared; I 
> just assumed it was 
> MI0KOA also running as a Fox in F & H mode.
> 
> Here's an extract from my ALL.TXT:
> 

> 
> The first appearance of the MI0KOA callsign is at 232515z, when JA4DND was 
> calling him - 
> there's no evidence of that JA callsign previously having called HV0A.  At 
> 232500 HV0A was 
> calling BG3UPA on 417Hz , then BG3UPA was subsequently called by MI0KOA at 
> 232530 
> on 296Hz.
> 
> I wonder if MI0KOA really was QRV in F & H mode at the same time and on the 
> same 80m 
> frequency as HV0A and the two sets of QSOs just got completely intermixed and 
> tangled up, 
> or perhaps it's another instance of identical hash values for the HV0A and 
> MI0KOA callsigns 
> which got cleared by restarting the app.
> 
> --
> 73, Martin G0HDB

John and Martin,

What you were seeing was caused by a 10-bit hash collision between HV0A and 
MI0KOA. The next release of WSJT-X will incorporate a number of changes that 
are aimed at improving the handling of these situations. Specifically, the 
changes would have prevented MI0KOA from being displayed in angle brackets 
provided that you had HV0A entered into your DX Call box.

Thanks for the report!

Steve k9an



_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel






















					Reply via email to