On 8/14/21 06:55, Bill Somerville via wsjt-devel wrote:
Hi Mike,
it is not cleared automatically. TBH it's not a big deal as hash
collisions that cause incorrect decodes are rare since the vast
majority of WSPR transmissions are Type 1 messages. We normally
suggest deleting it if someone reports an unexplained incorrect
decode. Many wspr systems run 24/7 so there are no system restarts, or
at least very few.
I don't think the user should have to delete it manually. Murphy's Law
says that as soon as you do, you'll receive a type 2 or 3 message with a
hash value you just deleted.
I think the better way is to keep the hash table sorted in least
recently used (LRU) order (as you suggested) and to check that the first
four characters of the grid square match (if I understand the formats
correctly).
How many stations transmit WSPR on multiple bands at once? Multiband
monitoring by individual stations is pretty common, right? A single hash
database common to multiple copies of wsprd could thus be useful.
Phil
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
