Hi Joe Further testing (with 10 calls in call3.txt now) with DS and averaging both enabled, and a 'weaker' signal [that has so far not produced a single line decode (#40, #-24)] seems to show a trend in which decoder is used.
Calls+loc seem to decode with averaging with d, while messages containing calls+reports or calls+RRR decode with averaging with f. Running other settings per your recommendations, and no false decodes seen (other than the "dragging" average). Charlie > As things now stand, you need to click "Clear Avg" to start a new > average. Possibly we will want to use the alternate (reversed) sync > pattern, as we did in JT4, so that the receiving software can recognize > the message has changed, even before it can be decoded? "Clear Avg" works as expected - a changed message is decoded in significantly fewer periods. Reversing sync might be a good idea. Charlie ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785471&iu=/4140 _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
