Hi Bill, Thanks for the explanation. SP5 was active 1h or more b4 i started to call the SX special call. I checked that in all.txt, somehow it was exctracted from earlier decodes...
Best regards, 73 Patrik 9A5CW Datuma sri, 12. pro 2018. 20:38 Bill Somerville <[email protected] piše: > On 12/12/2018 18:54, Patrick 9A5CW wrote: > > Hi, > > can someone explain what happend here? See part of all.txt. > > I am 9A5CW, i am not SP5ORS? > > How i sent that msg? > > Yesterday saw something similar with another SP callsign in the > > Brackets when he was calling CR150AA....?! > > I was not transmiting at that time. > > > > Best regards, > > Patrik 9A5CW > > p.s. if u need ALL.TXT i can sent it > > > Hi Patrik, > > this is a hash code collision. The hash code for 9A5CW and SP5ORS are > the same. I am not sure quite why WSJT-X is printing <SP5ORS> instead of > <9A5CW> since your callsign should be newer in the hash table. The > messages sent are exactly correct, the problem is in the printing at > your end. It looks like our algorithm for dealing with potential hash > collisions needs some work although there are always some scenarios when > we can't get this right, for example if messages involving the real > SP5ORS including their call as a hash are interleaving the same with > your call i.e neither is most likely to be correct. > > 73 > Bill > G4WJS. > > > > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
