Hi Greg, > On Jun 25, 2015, at 11:10 PM, KI7MT <ki7m...@gmail.com> wrote: > > Hi Steve, > > Just so I am clear on this. The Makefile (Linux) has three targets, > wsprd, wsprsim and wspr_exp. All we need to build is wspr_exp as the > wsprd is being dealt with by Cmake yes? Yes, the regular wsprd and the simulation program wsprsim are built by Cmake, but not wsprd_exp. > > I'll be adding this to JTSDK Nix to build and cp the wspr_exp decoder to > install/bin location on each turn. > > I had brief look at the Windows Makefile.MinGW but did not see the > wsprd_exp target listed, so I am assuming this is only being tested on > *Nix ?? I have only tested wsprd_exp on linux and OS X. I don’t have a Windows machine.
Thanks for adding wsprd_exp to the WSJT-X build script. Some time soon I think that we’ll want to just rename wsprd_exp to wsprd and have it replace the current decoder. Before we do that, Id like to see that at least a couple of people besides me have been able to use wsprd_exp without problems. Steve k9an > > 73's > Greg, KI7MT > > On 06/24/2015 07:30 PM, Steven Franke wrote: >> For those testing wspr mode in wsjt-x, I have placed a .pdf file containing >> information on the current status of the experimental two-pass decoder >> wsprd_exp at this link: >> >> https://dl.dropboxusercontent.com/u/33211132/signal_subtraction.pdf >> >> I have been running the two-pass decoder with wsjt-x and with my 8-channel >> gnuradio-based setup for the past several days without any problems. >> If you would like to play with the new decoder, the Makefile in the >> wsjt-x/lib/wsprd directory will compile it. For testing with wsjt-x, I >> renamed the executable wsprd and copied it into the <wsjt-x install>/bin >> directory. >> >> While testing this new decoder I used a batch of .wav files and also a >> separate batch of .c2 files that were written by the latest wsjt-x. I >> eventually realized that all of the .c2 files that were written by wsjt-x >> were contaminated by signal dropouts. See “Case 3” in the pdf document for >> an example and more details. After discovering the problem with the .c2 >> files, I saved a batch of .wav and .c2 files using wsjt-x and found that the >> .wav files were fine, but that the .c2 files were contaminated. This makes >> me wonder if the problem lies in the writec2 routine in wsjt-x. I welcome >> input/opinion on this from those who are more familiar with the code. Could >> this problem somehow be specific to my setup? >> >> Steve k9an > > ------------------------------------------------------------------------------ > Monitor 25 network devices or servers for free with OpManager! > OpManager is web-based network management software that monitors > network devices and physical & virtual servers, alerts via email & sms > for fault. Monitor 25 devices for free with no restriction. Download now > http://ad.doubleclick.net/ddm/clk/292181274;119417398;o > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ Monitor 25 network devices or servers for free with OpManager! OpManager is web-based network management software that monitors network devices and physical & virtual servers, alerts via email & sms for fault. Monitor 25 devices for free with no restriction. Download now http://ad.doubleclick.net/ddm/clk/292181274;119417398;o _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
