Hello Bill and all team
While I am working on the Hamlib / FT991 issue with Michael I got caught too by
the wsprd issue .
1/ 5644 :error message in wsjtx at decode time starting or running wsprd
2/ Dos command wsprd without parameter : just the usage ok
3/ Dos command but trying to open a c2 file from command line it crashes
4 / tried 5647 and it works
I suspect it gives an idea of the root cause ! I am back to hamlib issue now …
Regards
Jean Louis
C:\WSJT\wsjtx\bin>wsprd
Usage: wsprd [options...] infile
infile must have suffix .wav or .c2
Options:
-a <path> path to writeable data files, default="."
-c write .c2 file at the end of the first pass
-e x (x is transceiver dial frequency error in Hz)
-f x (x is transceiver dial frequency in MHz)
-H do not use (or update) the hash table
-m decode wspr-15 .wav file
-q quick mode - doesn't dig deep for weak signals
-s single pass mode, no subtraction (same as original wsprd)
-v verbose mode (shows dupes)
-w wideband mode - decode signals within +/- 150 Hz of center
-z x (x is fano metric table bias, default is 0.42)
C:\WSJT\wsjtx\bin>
C:\WSJT\wsjtx\bin>wsprd 150526_1904.c2 error wsprd.exe has stopped (windows
message)
-----Message d'origine-----
De : Bill Somerville [mailto:g4...@classdesign.com]
Envoyé : mercredi 1 juillet 2015 12:20
À : wsjt-devel@lists.sourceforge.net
Objet : Re: [wsjt-devel] wspr two-pass decoder status and .c2 file problem
On 01/07/2015 06:16, Robert Kalkwarf wrote:
> Steve,
Hi Bob,
>
> Win7 32 bit
>
> I get an Error running or starting c:/WSJT/wsjtx/bin/wsprd
That looks like you have installed using an installer generated by the package
build option. Have a look in the installed folder and see if wsprd.exe is
there. It will be "C:\WSJT\wsjtx\bin\wsprd.exe". If it is there, try running it
from the command line and tell us what you get.
>
> Tried build-wsjtx install
>
> Tried build-wsjtx package
>
> Answered y both times to update. HELP says I am running r5644
>
> Clue Please?
>
>
> 73 Bob w7wo
73
Bill
G4WJS.
>
>
>
>> On Jun 30, 2015, at 3:18 PM, Steven Franke < <mailto:s.j.fra...@icloud.com>
>> s.j.fra...@icloud.com> wrote:
>>
>> For those testing wspr mode in wsjt-x ver 1.6, I’ve just committed r5644
>> which makes decoder #5 from Joe’s table, below, the default decoder in
>> wsjt-x ver 1.6. It is no longer necessary to separately compile wsprd_exp to
>> get the benefits of two-pass decoding.
>> Steve k9an
>>
>>> On Jun 29, 2015, at 6:25 PM, Joe Taylor < <mailto:j...@princeton.edu>
>>> j...@princeton.edu> wrote:
>>>
>>> Hi Steve,
>>>
>>>>> The test runs all used the same set of 386 *.wav files, processed
>>>>> with the following decoders:
>>>>>
>>>>> 1. wsprd, from WSPR-X (baseline decoder) 2. wspr4 3. wsprd, as
>>>>> built for WSJT-X v1.6.0 r5636 4. wsprd_exp, signal subtraction
>>>>> using symbol-by-symbol coherence 5. wsprd_exp, subtraction with
>>>>> full coherence and test for local maxima 6. wsprd_exp, subtraction
>>>>> with full coherence and snr> min_snr
>>>>>
>>>>> For each run the following table gives the number of decodes, the
>>>>> wall-clock running time, the average time per wav file, and the
>>>>> "improvement factor" for number of decodes and speed.
>>>>>
>>>>> Decodes Time1 AvgTime Improvement Decoder
>>>>> (s) (s) Decodes Speed
>>>>> ----------------------------------------------------------------
>>>>> 1. 1451 2111 5.5 1.00 1.00 baseline
>>>>> 2. 1693 1599 4.1 1.17 1.32 wspr4
>>>>> 3. 2208 335 0.9 1.52 6.30 WSJT-X v1.6.0 r5636
>>>>> 4. 2464 413 1.1 1.70 5.11 partial coherence
>>>>> 5. 2567 431 1.1 1.77 4.90 full coherence
>>>>> 6. 2839 2136 5.5 1.96 0.99 more candidates
>>>> Thanks for running these tests. These agree with my results,
>>>> although I see somewhat more improvement as you go down the list,
>>>> probably because my test files are all from 20m under crowded band
>>>> conditions.
>>> Agreed: I think my test files were not quite so homogeneous as yours.
>>>
>>>> At some point, we should look at the coherent subtraction lowpass
>>>> filter. The length (nfilt) and impulse response were chosen without
>>>> much thought...
>>> Yes, this may need further tweaking. In addition, I suspect we can
>>> find a criterion better than simply "smspec[j] > min_snr" for
>>> choosing candidate frequencies, and likely some other speedups, as well.
>>>
>>> -- Joe
------------------------------------------------------------------------------
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/> https://www.gigenetcloud.com/
_______________________________________________
wsjt-devel mailing list
<mailto:wsjt-devel@lists.sourceforge.net> wsjt-devel@lists.sourceforge.net
<https://lists.sourceforge.net/lists/listinfo/wsjt-devel>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
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
