In developing wsprdaemon I sought to emulate the WSPR decode operation as closely as possible. So after observing that WSJT-x invoked wsprd with "-C 500', I made that the default for WD's use of wsprd. I would welcome suggestions about the optimal set of this and wsprd parameters, and at WD isites t would be easy to quantify the performance effects of such changes.
On Sun, May 1, 2022 at 12:25 PM Daniele Forsi via wsjt-devel < [email protected]> wrote: > Jim wrote: > > > my thought on the 500 was something someone else told me... > > > > I'll look at the source code > > 500 is not the default value, but it's the value used in the > invocation of wsprd made by wsjt-x; I can see it in the status line > (see image attached) > > in my local git checkout the code apparently is at line 1612: > widgets/mainwindow.cpp:1611: if((m_ndepth&7)==2) depth_args << > "-C" << "500" << "-o" << "4"; //3 pass, subtract, Block detection, OSD > widgets/mainwindow.cpp:1612: if((m_ndepth&7)==3) depth_args << > "-C" << "500" << "-o" << "4" << "-d"; //3 pass, subtract, Block > detect, OSD, more candidates > > -- > 73 de IU5HKX Daniele > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > -- Rob Robinett AI6VN [email protected] mobile: +1 650 218 8896
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
