Hi Mike,
Some parameters that are user-configurable in WSJT-X are hard-wired when
you run jt9[.exe] from the command line.
Try making changes as follows, starting around line 81 in jt9.f90, and
then re-compiling:
shared_data%params%naggressive=0
shared_data%params%n2pass=2
shared_data%params%nranera=6
With these parameters set to the same values as those I've selected in
WSJT-X, I get identical decoding results on a test file with 13 JT65 and
10 JT9 signals, using the following command:
jt9 -L 100 -S 2500 -6 -9 -d 3 d:/data/JT65-HF/150919_2005.wav
-- Joe, K1JT
On 2/15/2017 12:27 PM, Black Michael wrote:
> How does one run decoding against a set of WAV files that does the same
> thing as WSJT-X?
>
> I've tried this:
> jt9 -d 3 -9 -6 -S 2400 test.wav
>
> But it misses a lot of JT65 decodes.
>
> de Mike W9MDB
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>
>
>
> _______________________________________________
> wsjt-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
