WSJT X version: r5604 Operating System: Windows XP
Symptoms: Does not decode in the "G" bin-width even when decoding marginal signals with 300 Hz spreading Other Symptoms: If you try and force "G" bin-width decodes by setting MinW to "G" the program gives a faulty output of dB = -125, DT = -0.69 and Freq = 599 even though it has been decoding satisfactorily with the bin-width set to any lower level than "G". Background: This bug was detected when doing simulation tests that showed that the JT4g performed no better than JT4f even at spreading wider than the JT4f bin-width (e.g. 200 and 400 Hz.) . Test Results: Over 400 tests were undertaken with the WSJT-X simulator set for marginal decoding at -21.5 dB S/N and spreading of 300 Hz which should have favoured the "G" bin-width of 315 Hz. Of these tests the program gained 69% correct syncs, 0.2 % decodes in "C" bin-width, 0.9 % in "D", 4.9% in "E", 19.5% in "F" and nil in "G". The increasing number of decodes with bin-width up to "F" is consistent with the bin-width getting closer to the spreading of 300 Hz up until it gets to the "G" bin-width which gives nothing. WSJT10: WSJT10 has a similar problem and but in this case locks up if you set MinW to "G". It seems that this bug may simply relate to the variable win-width routine not do the final step to the "G" bin-width. 73 Rex VK7MO ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
