Hello Bill, Thank you for the clear explanation, as always. One question remains, how long will an entry in the hash table exist for? In particular is it cleared after a band change? I sometimes do bandhopping to monitor different bands.
Thanks again and 73, Ton pa0tbr On Sat, 15 Dec 2018 at 18:50, Bill Somerville <[email protected]> wrote: > On 15/12/2018 17:11, Ton PA0TBR wrote: > > I am trying to work out why some callsigns are shown as <...> in WSJT-X > > Sometimes <...> is reflected in JTAlert as ... other times it is not > > shown in JTAlert. > > > > For example: > > 103615 -12 1.8 1590 ~ <...> LZ1PPZ > > 103645 -2 1.8 1590 ~ <...> LZ1PPZ R-18 > > 103715 -5 1.9 1589 ~ <...> LZ1PPZ R-20 > > 103745 -8 1.8 1588 ~ OG55W <LZ1PPZ> 73 > > > > Looks like LZ1PPZ worked OG55W, but why was the call of OG55W not > > shown in the initial messages? > > And why is LZ1PPZ enclosed by <> in the last message? > > > > Other examples: > > 112030 -12 0.3 915 ~ G3PLP <...> -16 > > 112100 -14 0.3 915 ~ <G3PLP> ZS9YOTA RR73 > > Why was ZS9YOTA substituted by <...> ? > > > > 111800 -17 0.1 650 ~ CQ SD4C JP80 Sweden > > 111830 -14 0.1 650 ~ <...> > > What happened here? > > > > I use WSJT-X v2.0.0.0 in FT8 mode > > > > 73, > > Ton pa0tbr > > Hi Ton, > > in the WSJT-X 77-bit FT8 (and MSK144) protocol non-standard callsigns > like OG55W and ZS9YOTA require one of the callsigns in a two-callsign > message to be compressed to a hash code to make space for the rest of > the message information. The hash code is a one-way algorithm so the > callsign cannot be looked up until a message with the callsign in full > has been received, until then the hash code is indicated as <...>. Once > the hash table is populated, the callsigns received as hash codes are > printed between '<' and '>' characters. The QSO flow and choice of which > of the two callsigns is hashed is arranged so that a station hearing > either end of the QSO will eventually get the hash table populated for > both callsigns. Also the flow and choice of which callsign to hash means > that during a QSO each station will send and receive each callsign > un-hashed at least once, in fact this is a corollary of the previous > sentence. > > 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
