Re: [wsjt-devel] Problems with r4611 and jt9_wisdom

Hi Joe, Thanks for the export wisdom fix.That solved a broken pointer problem. > Presumably the same thing could be done with the import, as well. Yes. I modified wisdom.c (including prototype definitions to get rid of compiler warning) which works. more jt9_wisdom_status.txt Imported

[wsjt-devel] FFTW3 Wisdom

Hi Joe & All, I have been superficially following the discussions on FFTW wisdom as I am busy with other issues. It looks like things have settled down now and I have just reviewed the changes with the intention of updating my local branch that implements merging wsjtx and jt9. I have a couple

Re: [wsjt-devel] FFTW3 Wisdom

Hi Bill, I can respond to (1): Because of pointer problems, Joe implemented wisdom.c to solve the export_wisdom problem I was having. I followed up by adding import_wisdom to wisdom.c with the result that f77_wisdom.f90 is no longer required. wisdom.c now deals directly with fftw calls. -

Re: [wsjt-devel] Rig control problem with WSJT-X 1.4.0-rc2 on Linux

On Friday (11/21/2014 at 01:23AM +), Bill Somerville wrote: > On 21/11/2014 01:17, Chris Elmquist wrote: > Hi Chris, > > I am having an issue with WSJT-X v1.4.0-rc2 on Linux with a MicroHam-III > > USB sound card interface and an Icom 746PRO CAT-connected radio. I am > > using the build offere

Re: [wsjt-devel] FFTW3 Wisdom

Hi Bill and all, > 1) What is the purpose of f77_wisdom.f90 and wisdom.c? I ask because > they seem to duplicate functionality that is already available directly > from the FFTW3 library in both C and Fortran form via the fftw3.h and > fftw3f.f03 include files. File fftw3f.f03 is apparently fairl

Re: [wsjt-devel] FFTW3 Wisdom

A minor warning on 4617 C:\JTSDK-QT\src\wsjtx\mainwindow.cpp:385:7: warning: unused variable 'success' [-Wunused-variable] int success = fftwf_import_wisdom_from_filename(cfname); -Original Message- From: Joe Taylor [mailto:j...@princeton.edu] Sent: Friday, November 21, 2014 9:35 AM T

Re: [wsjt-devel] FFTW3 Wisdom

On 21/11/2014 15:34, Joe Taylor wrote: > Hi Bill and all, Hi Joe, > >> 1) What is the purpose of f77_wisdom.f90 and wisdom.c? I ask because >> they seem to duplicate functionality that is already available directly >> from the FFTW3 library in both C and Fortran form via the fftw3.h and >> fftw3f.f

Re: [wsjt-devel] KVASD for Mac

On 17/11/2014 19:15, Joe Taylor wrote: Hi Joe, > This message is mainly for Bill and John: is there something I still (or > again?) need to do, for kvasd on OS X ? Sorry for the late reply, I was waiting until any issues from the Mac KVASD installer arose. It would be handy to know exactly what c

Re: [wsjt-devel] Decoding problems

On 11/21/2014 12:34 AM, Michael Black wrote: > I seem to be seeing some decoding problems recently. ... The JT65 signals you mention in your first two files are below the threshold for the JT65 decoder, around -24 dB. It's hardly surprising to see a weak signal in the waterfall that fails to d

Re: [wsjt-devel] KVASD for Mac

Hi Bill, > It would be handy to know exactly what compiler/linker options you used > when building KVASD for the Mac? cc -c -arch i386 usleep.c cc -c -O2 -arch i386 asd1.c gfortran -o kvasd_1.12_mac32_10.7 -m32 kvasd.f90 asd1.o usleep.o cc -c -arch x86_64 usleep.c cc -c -O2 -arch x86_64 asd1.c g

Re: [wsjt-devel] KVASD for Mac

On Fri, Nov 21, 2014 at 10:44 AM, Joe Taylor wrote: > cc -c -arch i386 usleep.c > cc -c -O2 -arch i386 asd1.c > gfortran -o kvasd_1.12_mac32_10.7 -m32 kvasd.f90 asd1.o usleep.o > > cc -c -arch x86_64 usleep.c > cc -c -O2 -arch x86_64 asd1.c > gfortran -o kvasd_1.12_mac64_10.7 -m64 kvasd.f90 asd1.

Re: [wsjt-devel] FFTW3 Wisdom

Hi Joe, Bugs introduced in wisdom.c jt9.f90 call export_wisdom(wisfile(1:n)//char(0)) 1 argument wisdom.c void export_wisdom_(char fname[], int len) 2 arguments Same for call import_wisdom (2 arguments)

Re: [wsjt-devel] FFTW3 Wisdom

Joe, No bugs introducedignore...I forgot about F90 and arrays being passed. --- John G4KLA -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Report

Re: [wsjt-devel] FFTW3 Wisdom

John -- Not sure why you call these bugs? Does something on your system complain? For each string that Fortran passes as an argument, the string length is added as a "hidden argument" after the last visible argument. If the function being called is written in C, the hidden argument is visible

Re: [wsjt-devel] KVASD for Mac

On 21/11/2014 16:44, Joe Taylor wrote: > Hi Bill, Hi Joe, > >> It would be handy to know exactly what compiler/linker options you used >> when building KVASD for the Mac? > cc -c -arch i386 usleep.c > cc -c -O2 -arch i386 asd1.c > gfortran -o kvasd_1.12_mac32_10.7 -m32 kvasd.f90 asd1.o usleep.o > >

Re: [wsjt-devel] KVASD for Mac

On 21/11/2014 17:38, Bill Somerville wrote: Sorry, a correction below - all compiles should have the minimum Mac OS X version option: > For future reference you should be able to build on an OS X 10.10 system > with the following options: > > for a 32-bit version built on a 64-bit system: > > cc

Re: [wsjt-devel] KVASD for Mac

Richard -- On 11/21/2014 11:59 AM, Richard Shaw wrote: > On Fri, Nov 21, 2014 at 10:44 AM, Joe Taylor wrote: > >> cc -c -arch i386 usleep.c >> cc -c -O2 -arch i386 asd1.c >> gfortran -o kvasd_1.12_mac32_10.7 -m32 kvasd.f90 asd1.o usleep.o >> >> cc -c -arch x86_64 usleep.c >> cc -c -O2 -arch x86_6

Re: [wsjt-devel] KVASD for Mac

On Fri, Nov 21, 2014 at 11:48 AM, Joe Taylor wrote: > Richard -- > > No need for CMake here, this is a trivial (and infrequently required) > build operation. Perhaps, but it seems different flags are needed just between mac versions... Putting it in a build system keeps you from having to remem

Re: [wsjt-devel] KVASD for Mac

On 21/11/2014 17:54, Richard Shaw wrote: On Fri, Nov 21, 2014 at 11:48 AM, Joe Taylor > wrote: Richard -- No need for CMake here, this is a trivial (and infrequently required) build operation. Perhaps, but it seems different flags are needed just between

Re: [wsjt-devel] Wsjtx v1.4

Hi Leif, sorry you are having issues with the WSJT-X v1.4.0-rc2 beta release. I have recently added fixes to hamlib for both the IC-7700 and the IC-7100. Here is an installer for a version with the changes included: https://dl.dropboxusercontent.com/u/4192709/wsjtx-1.4.0-rc3-win32-r4595.exe In

Re: [wsjt-devel] Wsjtx v1.4

Apologies to the list, I meant to send this directly to Leif, which I have now done. 73 Bill G4WJS. On 21/11/2014 18:41, Bill Somerville wrote: > Hi Leif, > > sorry you are having issues with the WSJT-X v1.4.0-rc2 beta release. > > I have recently added fixes to hamlib for both the IC-7700 and t

Re: [wsjt-devel] Rig control problem with WSJT-X 1.4.0-rc2 on Linux

On 21/11/2014 14:48, Chris Elmquist wrote: Hi Chris, > On Friday (11/21/2014 at 01:23AM +), Bill Somerville wrote: >> On 21/11/2014 01:17, Chris Elmquist wrote: >> Hi Chris, >>> I am having an issue with WSJT-X v1.4.0-rc2 on Linux with a MicroHam-III >>> USB sound card interface and an Icom 74

Re: [wsjt-devel] Rig control problem with WSJT-X 1.4.0-rc2 on Linux

On Friday (11/21/2014 at 07:14PM +), Bill Somerville wrote: > > Hamlib does deal with this issue but only when you select either DTR or > RTS as the PTT port. Your set up is a little unusual in that you are > using CAT commands for PTT and also have the DTR line linked to PTT. So, this is t

Re: [wsjt-devel] Rig control problem with WSJT-X 1.4.0-rc2 on Linux

On 21/11/2014 19:48, Chris Elmquist wrote: Hi Chris, > On Friday (11/21/2014 at 07:14PM +), Bill Somerville wrote: >> Hamlib does deal with this issue but only when you select either DTR or >> RTS as the PTT port. Your set up is a little unusual in that you are >> using CAT commands for PTT a

Re: [wsjt-devel] Rig control problem with WSJT-X 1.4.0-rc2 on Linux

On 21/11/2014 20:12, Bill Somerville wrote: Hi again Chris, more info below ... > On 21/11/2014 19:48, Chris Elmquist wrote: > > Hi Chris, > >> On Friday (11/21/2014 at 07:14PM +), Bill Somerville wrote: >>> Hamlib does deal with this issue but only when you select either DTR or >>> RTS as th

Re: [wsjt-devel] Rig control problem with WSJT-X 1.4.0-rc2 on Linux

On 21/11/2014 20:38, Bill Somerville wrote: > On 21/11/2014 20:12, Bill Somerville wrote: > > Hi again Chris, > > more info below ... >> On 21/11/2014 19:48, Chris Elmquist wrote: >> >> Hi Chris, >> >>> On Friday (11/21/2014 at 07:14PM +), Bill Somerville wrote: Hamlib does deal with this

Re: [wsjt-devel] Decoder optimizations

Joe Taylor writes: > One of the changes is to make use of the "wisdom" feature in FFTW. This > requires running the program fftwf-wisdom[.exe] once, at the time of > program installation. A batch script "wisdom1[.bat]" can be used to do > this; I added an example of such a file to the direc

Re: [wsjt-devel] Rig control problem with WSJT-X 1.4.0-rc2 on Linux

On Saturday (11/22/2014 at 12:38AM +), Bill Somerville wrote: > > > > I will sort out a patch for hamlib and send you a test version shortly. > Here is a build of WSJT-X v1.4.0-rc3 with the patched hamlib code. > Please try it using "PTT Method" DTR and the PTT serial port set to the > same p