[wsjt-devel] Lots of progress

[Joe Taylor]

Hi all,

My thanks to all who have been so productive during my recent absence 
from this list.  My trip to the Netherlands to participate in reopening 
ceremonies for the Dwingeloo radio telescope -- once the largest radio 
telescopes in the world -- was great fun.  Unfortunately, while there I 
developed an impacted wisdom tooth, which was extracted ASAP after my 
return home.  My mouth feels a lot better now than last week!

I'm doing my best to catch up with what others have been up to with 
WSJT-X and our documentation.  Fair warning: I have a number of other 
obligations coming up in the next six weeks or so, so my presence here 
may be spotty at times.

-- 73, Joe, K1JT

PS: For a few examples of what was going on at Dwingeloo, see the 
following links:

http://www.camras.nl/index.php?lang=en

https://www.astron.nl/about-astron/press-public/news/renovated-dwingeloo-telescope-opened-nobel-prize-winner-joe-taylor/re

http://www.arrl.org/news/nobel-prize-winner-joe-taylor-k1jt-helps-reopen-dutch-radio-telescope

--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X Linux packaging - man pages.

[Joe Taylor]

Hi Bill,

 Except we don't have a program called jt9.  Guess you mean wsjt?  The
 full suite (in order of their birth years) is WSJT, MAP65, WSPR, WSJT-X,
 and WSPR-X.
 We do in terms of Linux packaging. Technically any executable that is
 bundled into a package should have a man page and that is policed by the
 package checking tools like 'lintian' which would be used by
 distribution repository guardians to check validity of new packages
 being submitted.

 Either way I hope it will become moot sometime in the near future.

Thanks -- now I understand why you were talking about the program jt9. 
  As you can tell, I'm not generally familiar with these details about 
acceptable packaging criteria for Linux.  Thanks for thinking about it.

-- Joe

--
Learn Graph Databases - Download FREE O'Reilly Book
Graph Databases is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Taskbar Icon

[Joe Taylor]

Hi Bill and all,

I have forgotten where the issue about a missing WSJT taskbar icon now 
stands.  In my build of WSJT-X r4061, all the icons look reasonable 
*except* the one in the Windows 7 taskbar.  As shown in the attached 
excerpt from a screen shot, the taskbar shows a blank white rectangle 
with its top-right corner folded over.


-- Joe, K1JT
--
Start Your Social Network Today - Download eXo Platform
Build your Enterprise Intranet with eXo Platform Software
Java Based Open Source Intranet - Social, Extensible, Cloud Ready
Get Started Now And Turn Your Intranet Into A Collaboration Platform
http://p.sf.net/sfu/ExoPlatform___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Taskbar Icon

[Joe Taylor]

Hi Bill and all,

Problem solved.  I had copied the *exe files from the ...\Release\bin 
directory to another location (so as to build onto the wsjtx_log.adi 
file already there).  Doing this produced the blank-page icon in the 
taskbar.

By doing it the other way -- copying the *.adi file into 
...\Release\bin, and running WSJT-X from there -- everything works as it 
should.

I probably should have known.

-- Joe, K1JT

On 4/25/2014 4:55 PM, Bill Somerville wrote:
 On 25/04/2014 21:44, Joe Taylor wrote:
 Hi Bill and all,
 Hi Joe,

 I have forgotten where the issue about a missing WSJT taskbar icon now
 stands.  In my build of WSJT-X r4061, all the icons look reasonable
 *except* the one in the Windows 7 taskbar.  As shown in the attached
 excerpt from a screen shot, the taskbar shows a blank white rectangle
 with its top-right corner folded over.
 The status as I remember it is that I couldn't reproduce the issue and I
 suggested a link that explained how to delete the Windows small icon
 cache which sometimes gets corrupted. Here is a summary in case you
 hadn't rediscovered it after your return from the Netherlands:

 del C:\Users\username\AppData\Local\IconCache.db

 then reboot.

  -- Joe, K1JT
 73
 Bill
 G4WJS.

 --
 Start Your Social Network Today - Download eXo Platform
 Build your Enterprise Intranet with eXo Platform Software
 Java Based Open Source Intranet - Social, Extensible, Cloud Ready
 Get Started Now And Turn Your Intranet Into A Collaboration Platform
 http://p.sf.net/sfu/ExoPlatform
 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free.
http://p.sf.net/sfu/SauceLabs
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Tx Audio Glitches (NOT)

[Joe Taylor]

Hi all,

I'm happy to report that I haven't heard a Tx audio glitch from WSJT-X 
for some time.  Bill probably knows exactly when (and why, at least 
approximately) this stopped happening.  As far as I can see, the Tx 
audio is now as rock-solid as it is in WSJT and WSPR -- and as it was in 
WSJT-X before we switched from PortAudio to QtMultiMedia.

Well done, Bill!

-- Joe, K1JT

--
Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free.
http://p.sf.net/sfu/SauceLabs
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Revision 4138, and OnmiRig.h

[Joe Taylor]

Hi Bill,

 What am I missing, here?  Should OmniRig.h be in the SVN?  Why does my
 CMake build work without it?

 OmniRig.h and OmniRig.cpp are generated files. They are produced by the
 Qt 'dumpcpp' utility that generates a stub library for a proxy to a
 Windows COM component. I though I had put the necessary incantation into
 the qmake .pro file to have it do the generation as the CMake scripts do.

 Are you using the latest wsjtx.pro file? the 'axcontainer' option and
 'TYPELIBS' variable should be all that is needed.

Yes, I have the latest wsjtx.pro file.  In my Windows setup, doing 
qmake followed by mingw32-make Release fails to create the OmniRig.* 
files.  I have not discovered why.

Perhaps we should agree to abandon building via qmake?  maintaining that 
path may be more trouble than it's worth.

-- Joe

--
Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free.
http://p.sf.net/sfu/SauceLabs
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Revision 4138, and OnmiRig.h

[Joe Taylor]

Thanks, Bill.  With the changes I put into wsjtx.pro in r4140, the qmake 
build is functional again.  (There were no problems with my OmniRig 
installation.)

-- Joe

On 5/14/2014 1:39 PM, Bill Somerville wrote:
 On 14/05/2014 18:15, Joe Taylor wrote:
 Hi Bill,
 Hi Joe,

 What am I missing, here?  Should OmniRig.h be in the SVN?  Why does my
 CMake build work without it?
 OmniRig.h and OmniRig.cpp are generated files. They are produced by the
 Qt 'dumpcpp' utility that generates a stub library for a proxy to a
 Windows COM component. I though I had put the necessary incantation into
 the qmake .pro file to have it do the generation as the CMake scripts do.

 Are you using the latest wsjtx.pro file? the 'axcontainer' option and
 'TYPELIBS' variable should be all that is needed.
 Yes, I have the latest wsjtx.pro file.  In my Windows setup, doing
 qmake followed by mingw32-make Release fails to create the OmniRig.*
 files.  I have not discovered why.
 I don't think this is a qmake issue. It works for me but I get the
 missing file error if I uninstall OmniRig. I suspect something has
 happened to your OmniRig installation. I think you may need to reinstall
 OmniRig.

 Your CMake build is probably working because the OmniRig.h and
 OmniRig.cpp files in your build workspace were generated some time ago
 before this issue appeared.

 Perhaps we should agree to abandon building via qmake?  maintaining that
 path may be more trouble than it's worth.
 I did hit another small issue with the qmake based build which I have
 fixed, it was self inflicted.

 IMHO keeping the qmake build alive is not too difficult, so far. I am
 very aware that several of the development team expressed an interest in
 build from within QtCreator and I haven't seen a definitive set of
 instructions for setting up the QtCreator CMake integration with our
 CMakeLists.txt file. Until such a process is available I am happy to
 hack at the qmake project file to make it work when someone raises an
 issue or I find it myself.

  -- Joe
 73
 Bill
 G4WJS.

 --
 Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
 Instantly run your Selenium tests across 300+ browser/OS combos.
 Get unparalleled scalability from the best Selenium testing platform available
 Simple to use. Nothing to install. Get started now for free.
 http://p.sf.net/sfu/SauceLabs
 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free.
http://p.sf.net/sfu/SauceLabs
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSPR 4.0

[Joe Taylor]

Hi Greg,

Thanks for helping W7IUV with the Microsoft dll.

I'm not sure why CX_Freeze has not done this for us; is there a 
licensing issue that would prevent us from including MSVCR100.dll in the 
distribution package, as needed?

-- Joe, K1JT

--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing  Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] PyCObject_Type ??

[Joe Taylor]

Checking out source code from the SVN repository does not install 
WSPR.  It gives you a copy pf the source code, from which you must build 
the program.

The error message is telling you that you have not built the required 
module w.so.

-- Joe, K1JT

On 6/19/2014 2:31 AM, Mike Long wrote:
 Hello,

 After installing the latest version of WSPR via SVN, I was greeted with
 this error when trying to execute wspr. I have no idea what it means. Can
 anyone help me correct this?  OS is Linux Mint Cinnamon.

 Traceback (most recent call last):
 File wspr.py, line 63, in
 from WsprMod import w
 ImportError: /home/nl3d/.wspr/WsprMod/w.so: undefined symbol: PyCObject_Type

 Thanks!
 Mike




 --
 HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
 Find What Matters Most in Your Big Data with HPCC Systems
 Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
 Leverages Graph Analysis for Fast Processing  Easy Data Exploration
 http://p.sf.net/sfu/hpccsystems



 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing  Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X JT9W options.

[Joe Taylor]

Hi Bill and all,

I'm copying this answer to the wsjt-devel list, so that everyone can 
know what's going on -- and can chime in, if they have pertinent ideas.

 Chase W4TI is getting stuck into updating the WSJT-X docs for the latest
 enhancements. Because of this and his need to generate new graphics for
 the manual I think we need to do something with the visible JT9W parts.
 I would like to make them optional with a CMake option but I'm not sure
 I can do that easily with the parts in the UI modules that are written
 with Qt Designer. I could insert code to call hide on the UI
 components if the option is not ON at build time, which may be enough.

Yes, hiding the visible JT9W parts would be OK.  Or perhaps better, 
graying them out.  I don't see any particular downside to having some 
visible indications of features that are still to come.  It lets people 
know something about our plans.

 What is you intention with JT9W, are we going to make WSJT-X suitable
 for all bands or is it just being used as a test bed for the mode? If it
 is the former, the configuration changes I've made should be Ok for all
 recognised amateur bands up to 1mm including transverter support.

My original plan was to move the other WSJT modes (FSK441, JTMS, 
ISCAT-[AB], JT6M, JT65[BC], JT4[A-G]) into WSJT-X.  This would be a big 
job, and probably rather disruptive.

One possibility would be to recognize some clear distinctions between 
Fast Modes (JTMS, FSK441, ISCAT, and JT6M) and Slow Modes (JT65, 
JT4, and JT9).  Modes within each group share many characteristics, 
including length of T/R period and assumed signal type (e.g., 
meteor/ionospheric scatter, or roughly constant SNR).  Of course, each 
mode uses its own particular scheme for coding and modulation.

One might then move only slow modes into WSJT-X, or at least move them 
first.  I think this probably makes sense.

JT9W is probably the smallest perturbation of all, so it makes sense to 
do that one first.  I've been reluctant to start any of this development 
until after we release an existing WSJT-X -- first as a beta, for more 
thorough field testing, and then as a full release with an up-to-date 
manual.  Then we can tag that release and I can start on the mode 
additions, perhaps in a new SVN branch.

-- Joe, K1JT

--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing  Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT 10.0 beta

[Joe Taylor]

Hi all,

I have posted a link to WSJT v10.0, r4181 on the WSJT web site:
http://physics.princeton.edu/pulsar/K1JT/wsjt.html

Might as well let people know in a more open way that WSJT 10.0 is 
available, stable, and working well.  I've called this a beta release, 
but I imagine that it could soon be tagged and made into a full release.

For information: I will soon be traveling once again, this time from 
June 22 to July 3, and will not be reading email for much or all of that 
time.

-- 73, Joe, K1JT

--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing  Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT 10.0 beta

[Joe Taylor]

Mike -- Thanks, it's fixed now.

-- Joe, K1JT

On 6/19/2014 11:51 AM, Mike Thompson wrote:
 Just FYI, The 10.0 User guide is not functional.

 Thanks!


 On Thu, Jun 19, 2014 at 10:31 AM, Joe Taylorj...@princeton.edu  wrote:

 Hi all,

 I have posted a link to WSJT v10.0, r4181 on the WSJT web site:
 http://physics.princeton.edu/pulsar/K1JT/wsjt.html

 Might as well let people know in a more open way that WSJT 10.0 is
 available, stable, and working well.  I've called this a beta release,
 but I imagine that it could soon be tagged and made into a full release.

 For information: I will soon be traveling once again, this time from
 June 22 to July 3, and will not be reading email for much or all of that
 time.

  -- 73, Joe, K1JT


 --
 HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
 Find What Matters Most in Your Big Data with HPCC Systems
 Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
 Leverages Graph Analysis for Fast Processing  Easy Data Exploration
 http://p.sf.net/sfu/hpccsystems
 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel




 --
 HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
 Find What Matters Most in Your Big Data with HPCC Systems
 Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
 Leverages Graph Analysis for Fast Processing  Easy Data Exploration
 http://p.sf.net/sfu/hpccsystems



 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing  Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT 10.0 beta

[Joe Taylor]

On 6/19/2014 12:19 PM, Mike Thompson wrote:
 Any idea how long this will take to come to Linux?

It runs fine in Linux now... but you need to compile it yourself.

How long before you can do a sudo apt-get install wsjt, or the 
equivalent?  Hard for me to tell...

-- Joe, K1JT

--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing  Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Font size in printed doc

[Joe Taylor]

Hi Greg (or anyone else who might know...),

After generating the User Guides for WSJT and WSPR in the usual way, 
displaying the resulting html files in Firefox shows them with the same 
font size (as expected).

However, if I use Firefox to print the User Guides (or just to print the 
first page, to save paper) the WSPR guide comes out in a smaller font 
size.

This behavior is NOT what's wanted, and I haven't been able to isolate 
what's causing it.  Do you have a clue?

-- Joe, K1JT

--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing  Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] moving station/wsjt-x update

[Joe Taylor]

Hi All,

As you will have noticed, I've been busy with other obligations 
recently.  I expect to have some time for WSJT-related matters in the 
next few weeks, so I'm trying to get plugged in once more.

Many thanks to Chase, W4TI, for all the effort put into the WSJT-X Users 
Guide for v1.4.  As you will see in the latest commit, r4210, I have 
been editing the early part of the Guide -- the present Sections 1-4 -- 
and have changed things quite a bit.  I want to give you some feeling 
for my underlying rationale for these changes.

1. To be most useful to the largest possible number of users, including 
those whose first language is not English, I think the User Guide should 
adopt a rather terse style: Do this, Do that, etc.

2. We should be uniform about voice and who we're talking to.  Write 
You can set *Parameter X* or simply Set *Parameter X*, rather than 
*Parameter X* can be set by the user.

3. Use of colors, special fonts, etc., should be uniform.  I've tried to 
be consistent in using adoc formatting commands like *Bold Blue* for the 
names of on-screen controls or parameters, and _italics_ for the 
identifying names of groups of controls on our GUI.  See, in particular, 
the new Section 4 for many examples.

4. Early parts of the Users Guide should be short and sweet: enough 
information for reasonably adept users to get started, but not a lot of 
extra descriptive material about why, or special cases.

5. Detailed descriptions of some options -- especially those whose 
functions will be obvious to experienced users -- should be moved to a 
section of their own.  In r4210 I've made a dummy Section 9, 
Configuration Details, that might serve.

6. Special cases, gotchas, etc., should be dealt with either in 
Configuration Details or in Frequently Asked Questions.

7. This Guide should be for v1.4.  In general I see no need for 
references to earlier versions.

8. I will move on soon to Transceiver Setup and following sections.
Like the other early sections, I think this one should be short and 
sweet.  But even within that constraint, the present text can surely be 
improved.  We can also add extra help in the FAQ section.

9. We should make specific reference to the very useful (but Windows 
only) companion program, JT-Alert.

Comments on any or all of the above will be welcome!

-- 73, Joe, K1JT

--
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Back in town

[Joe Taylor]

Hi all,

I'm home again after recent travels, once again getting back up to speed 
on all the good things done by others.

We have a lot of good new code, documentation, and development aids in 
the repository.  Can we agree that it's reasonable to plan for a beta 
release of WSJT-X v1.4 before too many more weeks have passed?

-- Joe, K1JT

--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Back in town

[Joe Taylor]

Hi Bill and all,

 Hope the travels were enjoyable, I gather from Dave G4RGK that the WX in
 France wasn't too pleasant.

Some rain, to be sure.  But we had a delightful time nevertheless!

Thanks for detailing the remaining issues you're aware of in WSJT-X v1.4.

I'm working on bringing the User Guide up to date.  I should be able to 
post a new version soon.  It will be accessible to those who are 
compiling v1.4 for themselves.

I was not aware that we had CAT problems that can affect all users.  (I 
haven't seen any examples of frequency walking up/down the band on my 
TS-2000, but admittedly my usage represents a small sample.)

As for the problems with FT817/857/897 and HRD... Couldn't we specify up 
front that these issues are there, and warn users that might be affected 
that they might want to delay upgrading to v1.4 a bit longer?

It seems to me that v1.4 is significantly better than v1.3 for many -- 
probably most? -- users.  Certainly I'm happy to be using it myself. 
Wouldn't it be helpful to start getting some user feedback on it, pretty 
soon?

-- Joe, K1JT

 We have a lot of good new code, documentation, and development aids in
 the repository.  Can we agree that it's reasonable to plan for a beta
 release of WSJT-X v1.4 before too many more weeks have passed?
 I guess this is aimed at me more than most. I'd love to say Yes let's
 do it! but I'm afraid my opinion hasn't moved on much from the last
 time we had this discussion. For this I must apologise since I have not
 been able to apply as much effort since then as I would have liked. I
 have only really been able to respond to issue reports and requests and
 not the the core issues that I know are still there. Here is a quick
 summary:

 CAT in general - there is a fundamental flaw in the strategy I have used
 that can cause the frequency to walk up/down the band on some
 rig/interface combinations. I know basically how to fix it but the
 changes will need much testing since they lie largely in the remaining
 MainWindow class CAT code which is defect prone due its close coupling
 with the rest of the application logic.

 Hamlib FT817/857/897 enhancements - this project is currently stalled on
 what appears to be a show stopper. Unfortunately since I am relying on
 undocumented CAT commands for these rigs the non-cooperation of one of
 the key commands has stalled my efforts. I need to put in a lot of time
 trying to work around this issue before giving up since this rig group
 is such a popular and common feature in many shacks.

 HRD - recent issues raised by Mike W9MDB have revealed what appears to
 be serious problem talking to HRD when the HRD logbook is active. Given
 that one of the main reasons for using HRD to interface to the rig is
 because the user uses the HRD logbook, I believe this issue is critical
 for HRD users. Mike is helping with trying to get to the root cause
 which currently seems to be at the HRD end, but we don't know that for
 sure yet. Again undocumented commands are problematic since HRD don't
 document any of their TCP/IP interface.

 Documentation - when I asked if anyone would like to help with
 documentation of the new config and CAT features, Chase W4TI kindly
 offered to help and I thought we were making good progress with me
 feeding him technical details of the implementation and its implications
 and he starting to make extensive edits to the user guide. Unfortunately
 this effort stalled for which I must take some blame for not posting
 enough public information of our work progress. Chase has now stepped
 back from the project feeling that he was mislead and misinformed about
 what was needed. This is great shame as people stepping up to contribute
 are hard to find, but that is where we stand.

 Of these areas the 1st and last to a lesser extent are probably the ones
 I would most worry about as they potentially effect all users.

  -- Joe, K1JT
 73
 Bill
 G4WJS.

 --
 Slashdot TV.
 Video for Nerds.  Stuff that matters.
 http://tv.slashdot.org/
 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] jt65code, jt9code

[Joe Taylor]

Hi Bill,

When you get a chance, could you modify CMakeLists.txt so that the 
executables jt65code[.exe] and jt9code[.exe] are once again built as 
part of the WSJT-X build procedure.

These utility programs are described in the User Guide (currently in 
Section 14), so the executables should also be included in the 
distribution packages.  Most users don't need them, but they help to 
document the JT65 and JT9 protocols.

-- Joe, K1JT

--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Bug?

[Joe Taylor]

Hi John,

Here's what should happen, as things are (supposedly) coded.

1. A new *.wav file should appear in the Save directory at the end of 
every Rx period (about t=50 s).

2. If the program continues running and Save is not enabled, the file 
from the previous Rx period is deleted at about t=40 s.

This means that if you kill the program, the most recent file will 
likely still be there.

We could, of course, do it in another (perhaps cleaner) way.  I have 
taken the somewhat lazy point of view that it's better to save too many 
files, than too few.

-- Joe, K1JT

On 9/14/2014 10:36 AM, John Nelson wrote:
 Mike writes:

 I've noticed lately that once in a while when I double click on an entry in 
 the Rx window the Enable Tx will turn on….but it won't start transmitting.

 I can report that I am also using a SignaLink USB with VOX PTT but haven't 
 see this (yet).   I am using a Mac...

 --- John G4KLA



 --
 Want excitement?
 Manually upgrade your production database.
 When you want reliability, choose Perforce
 Perforce version control. Predictably reliable.
 http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk



 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Plan for beta release of WSJT-X v1.4

[Joe Taylor]

Hi all,

We seem to be converging on a release procedure something like the 
following:

1. Minor bug fixes and tweaks to the packaging scripts are OK, but from 
today no new program features will be added to WSJT-X before we freeze 
code for the candidate release of v1.4.

2. G4WJS may make a few more tweaks to the hamlib library.  (Important 
question for Bill:  How will the state of that library be effectively 
frozen into the tagged candidate release?)

3. By 00:00 UTC Sept 26, one week from today, we'll agree on the SVN 
revision number of our mainline development branch,
.../branches/wsjtx, that will be tagged for the candidate release. 
We'll call the tag something like .../tags/wsjtx-1.4.0-rc1.  Code in 
this tag is frozen forever.

4. Code in the new tag will be checked out, compiled, and packaged on 
each platform for which we'll provide a binary installation package.  It 
will also be made into a compressed source tarfile.

5. The tagged source code will be SVN-copied into a new branch, 
something like .../branches/wsjtx-1.4.  Subsequent bug fixes to v1.4 
will be made there, and (if applicable) merged into the main development 
branch .../branches/wsjtx.

6. On Oct 1 I will post the new source-code tarfile at SourceForge and 
links to the binary packages (or instructions for obtaining and 
installing them) on the WSJT Home Page.

7. The mainline development branch will be bumped to v1.5.  Subsequent 
development (new program features, etc.) will take place there.

Note: All of the above refers to WSJT-X only; activity in other branches 
of our repository may continue normally.

Does this sound right?  Have I got something wrong, or left out anything 
important?

-- Joe, K1JT

--
Slashdot TV.  Video for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Plan for beta release of WSJT-X v1.4

[Joe Taylor]

 Does this sound right?  Have I got something wrong, or left out anything
 important?
 We need to carry out a similar process on the WSJT-X docs although that
 need not necessarily happen until the final RC is deemed to be v1.4.0. I
 don't think we want to exactly mirror the RC tags and branches for the
 docs, I say this because IMHO merges on documents are often messy and
 have many conflicts although if there is no activity on the main line
 documents the merges will be trivial.

We can include the best available wsjtx-main.html with installation 
packages built from the tagged revision.  However, I'm presently 
inclined to allow the manual that's brought up in a browser (when the 
user hits F1) to keep changing as further improvements are made.

-- Joe

--
Slashdot TV.  Video for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X Hamlib 3 fork updates.

[Joe Taylor]

Hi Bill,

Some feedback on your build procedure for hamlib on Windows.

I followed your suggested procedure:

 In an MSYS shell:-

 mkdir ~/hamib-prefix
 cd ~/hamlib-prefix
 git clone git://git.code.sf.net/u/bsomervi/hamlib src
 cd src
 git checkout integration
 mkdir ../build
 cd ../build
 ../src/autogen.sh --prefix=$HOME/hamlib-prefix \
   --disable-shared --enable-static \
   --without-cxx-binding --disable-winradio \
   CC=path-to-Qt-MinGW-tools/gcc \
   CXX=path-to-Qt-MinGW-tools/g++ \
   CFLAGS=-fdata-sections -ffunction-sections \
   LDFLAGS=-Wl,--gc-sections
 make
 make install

Since I have Greg's JTSDK-QT installed, for path-to-Qt-MinGW-tools I 
substituted C:/JTSDK-QT/qt5/Tools/mingw48_32/bin.

 this will leave a hamlib binary package installed at
 c:/Users/user-name/hamlib-prefix which is what needs to be on your
 CMAKE_PREFIX_PATH. On Windows you almost certainly will be using a CMake
 toolchain file and this is where you will need to specify the hamlib
 binary location as one of the paths in CMAKE_PREFIX_PATH.

Both make and make install ran to completion without errors.
I find no hamlib binary package installed at
c:/Users/user-name/hamlib-prefix :

joe@phy-joe ~/hamlib_g4wjs
$ ls -l
total 24
drwxr-xr-x 50 joe Administrators  8192 Sep 24 09:11 build
drwxr-xr-x 58 joe Administrators 16384 Sep 24 09:05 src

However, I do find libhamlib.a and libhamlib.la in
.../build/src/.libs, and after copying them to their normal location in 
Greg's JTSDK-QT, WSJT-X seems to build correctly.  (The build was, 
however, using the old (4/2/2014) include files, and perhaps other parts 
of the April 2014 build of hamlib.)

So...

1. Has something in make install failed to work for me as you expected?

2. I see no use of CMAKE_PREFIX_PATH anywhere in CMakeLists.txt, and
inserting the line
set (CMAKE_PREFIX_PATH C:/Users/Joe/hamlib_g4wjs)
at the top of CMakeLists.txt seems to do nothing.  Have I got something 
wrong here?

-- Joe, K1JT

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X Hamlib 3 fork updates.

[Joe Taylor]

Hi Bill and Greg,

As you recognized, the procedure I went through installed the newly 
built hamlib files, but not in the places I had expected.  My mistake.

I have now changed the --prefix=... part of the command that invokes 
autogen.sh to read --prefix=C:/JTSDK-QT/hamlib3/mingw32, and all 
appears to be well.  Newly built files appear in the bin, lib, include, 
and share directories there, and the usual JTSDK-QT commands build 
WSJT-X properly.

The only complaint issued by any of the scripts is this one from  the 
JTSDK-QT command build wsjtx package:

###
CPack: Create package
CPack: - package: 
C:/JTSDK-QT/wsjtx/build/Release/wsjtx-1.4.0-rc1-win32.exe gene
rated.

-
INSTALLER BUILD ERROR
-

  There was a problem building the package, or the script
  could not find:

  C:\JTSDK-QT\wsjtx\build\Release\wsjtx-1.4.0-win32.exe

  Check the Cmake logs for any errors, or correct any build
  script issues that were obverved and try to rebuild the package.
###

The message is completely benign: the script just did not understand 
that the package name would include the modifier -rc1.


For the record then, here's what I did to build the latest version of 
hamlib3 in Windows:

In an MSYS shell:-

mkdir ~/hamib_g4wjs
cd ~/hamlib_g4wjs
git clone git://git.code.sf.net/u/bsomervi/hamlib src
cd src
git checkout integration
mkdir ../build
cd ../build
../src/autogen.sh --prefix=C:/JTSDK-QT/hamlib3/mingw32 \
  --disable-shared --enable-static \
  --without-cxx-binding --disable-winradio \
  CC=C:/JTSDK-QT/qt5/Tools/mingw48_32/bin/gcc \
  CXX=C:/JTSDK-QT/qt5/Tools/mingw48_32/bin/g++ \
  CFLAGS=-fdata-sections -ffunction-sections \
  LDFLAGS=-Wl,--gc-sections
make
make install

... and then, in the JTSDK-QT environment CMD shell:

build wsjtx rinstall
build wsjtx package

-- Joe

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Packaging for -rc1

[Joe Taylor]

Hi all,

Should the installation packages for wsjtx-1.4.0-rc1 include the 
latest-and-greatest version of the WSJT-C User Guide?  It's online at

http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main.html

Which is good, since that lets us continue to improve the manual. 
However, for occasions when internet is not available, maybe it should 
be installed locally as well.  Perhaps even add an item such as Local 
User Guide on the Help menu?

While I'm at it, nit-picking: since the manual's name is WSJT-X User 
Guide, we should change the Help menu item Online User's Guide to 
read Online User Guide.

Bill, are you going to commit the change with a box for Allow Tx 
frequency changes while transmitting?

-- Joe

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Packaging for -rc1

[Joe Taylor]

Bill, Greg, and all --

I'd say display the local copy of :WSJT-X User Guide in the default 
web browser -- just as we do, already, with the online URL.

And yes, go ahead with committing the lockout behavior code.

I agree that building rinstall before the package target is not 
necessary.

Greg -- I think maybe I asked this before, but don't remember the 
answer.  After build wsjtx package, the package directory remains 
empty but wsjtx-1.4.0-rc1-win32.exe appears in the build directory. 
Is this really what you want?  I can't recall that I've ever seen 
anything in the package directory.

-- Joe

On 9/24/2014 1:11 PM, Bill Somerville wrote:
 On 24/09/2014 18:00, Joe Taylor wrote:
 Hi all,
 Hi Joe,

 Should the installation packages for wsjtx-1.4.0-rc1 include the
 latest-and-greatest version of the WSJT-C User Guide?  It's online at

 http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main.html

 Which is good, since that lets us continue to improve the manual.
 However, for occasions when internet is not available, maybe it should
 be installed locally as well.  Perhaps even add an item such as Local
 User Guide on the Help menu?
 We can certainly do that. The installer already creates a web link in
 the start menu and the programs and features entry but they are WIndows
 specific places. A local help menu item is no problem and a good idea,
 should we use a Qt window to display it (might be expensive in terms of
 installer size if we need other DLLs) or shell out to the default web
 browser. I need to check what Qt has in the way of launching a default
 web browser in a portable fashion.

 While I'm at it, nit-picking: since the manual's name is WSJT-X User
 Guide, we should change the Help menu item Online User's Guide to
 read Online User Guide.
 Yes.

 Bill, are you going to commit the change with a box for Allow Tx
 frequency changes while transmitting?
 I was waiting for any opinions on the whole lockout behaviour stuff I
 sent you which is in front on my local commit queue, the change is made
 and committed locally here. If you are OK with the other changes I'll
 push the lot out to the repo.

  -- Joe
 73
 Bill
 G4WJS.

 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
 http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Packaging for -rc1

[Joe Taylor]

RR Greg, thanks.  After updating from C:/JTSDK-DOC/doc,
wsjtx-1.4.0-rc1-win32.exe shows up in the package directory.

-- Joe

On 9/24/2014 1:44 PM, KI7MT wrote:
 Hi Joe,

 On 9/24/2014 17:21, Joe Taylor wrote:
 Bill, Greg, and all --

 I'd say display the local copy of :WSJT-X User Guide in the default
 web browser -- just as we do, already, with the online URL.

 And yes, go ahead with committing the lockout behavior code.

 I agree that building rinstall before the package target is not
 necessary.

 Greg -- I think maybe I asked this before, but don't remember the
 answer.  After build wsjtx package, the package directory remains
 empty but wsjtx-1.4.0-rc1-win32.exe appears in the build directory.
 Is this really what you want?  I can't recall that I've ever seen
 anything in the package directory.

 I just built: build wsjtx package

 and wsjtx-1.4.0-rc1.exe is in the package directory

 See Lines 205 to 209 in jtsdk-cmake.bat
 -
 :NSIS_PKG
 cmake --build . --target package
 IF NOT EXIST %BUILDD%\%OPTION%\%WSJTXPKG% ( GOTO NSIS_BUILD_ERROR )
 mv -u %BUILDD%\%OPTION%\%WSJTXPKG% %PACKAGED%
 GOTO FINISH_PKG
 -

 The mv line should be putting the file in ../package, this may have been
 an artifact of having the wrong file name in the build scripts, %WSJTXPKG%.

 Try updating from Docs, then rebuild the package target, it should land
 in ../package

 73's
 Greg, KI7MT

  -- Joe

 On 9/24/2014 1:11 PM, Bill Somerville wrote:
 On 24/09/2014 18:00, Joe Taylor wrote:
 Hi all,
 Hi Joe,

 Should the installation packages for wsjtx-1.4.0-rc1 include the
 latest-and-greatest version of the WSJT-C User Guide?  It's online at

 http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main.html

 Which is good, since that lets us continue to improve the manual.
 However, for occasions when internet is not available, maybe it should
 be installed locally as well.  Perhaps even add an item such as Local
 User Guide on the Help menu?
 We can certainly do that. The installer already creates a web link in
 the start menu and the programs and features entry but they are WIndows
 specific places. A local help menu item is no problem and a good idea,
 should we use a Qt window to display it (might be expensive in terms of
 installer size if we need other DLLs) or shell out to the default web
 browser. I need to check what Qt has in the way of launching a default
 web browser in a portable fashion.

 While I'm at it, nit-picking: since the manual's name is WSJT-X User
 Guide, we should change the Help menu item Online User's Guide to
 read Online User Guide.
 Yes.

 Bill, are you going to commit the change with a box for Allow Tx
 frequency changes while transmitting?
 I was waiting for any opinions on the whole lockout behaviour stuff I
 sent you which is in front on my local commit queue, the change is made
 and committed locally here. If you are OK with the other changes I'll
 push the lot out to the repo.

-- Joe
 73
 Bill
 G4WJS.

 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
 http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
 http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel



--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X-1.4.0-rc1 ?

[Joe Taylor]

Hi all,

Does anyone have last-minute must do commits for the WSJT-X code?
Are we converging toward tagging revision 4363 as release candidate 1 
for version 1.4.0 ?

-- Joe, K1JT

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X-1.4.0-rc1 ?

[Joe Taylor]

Hi all,

 OK, I think I'm done.

Full marks, indeed -- to all who have contributed so much!  Bill, would 
you like to create a tag of .../branches/wsjtx at r4370?  Packages for 
WSJT-X-1.4.0-rc1 would then be built from that revision, for all 
supported platforms.

-- Joe

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Credits mismatch

[Joe Taylor]

Mike --

 Credits mismatch between About window and the manual

Thanks for catching this discrepancy.  The online manual has been fixed; 
we'll need to correct the list in About in rc2.

-- Joe, K1JT

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X v1.4 branched from trunk.

[Joe Taylor]

Hi Bill,

Joe:
 All seems OK to me, except possibly for your parenthetical statement
 one day we really need to move this to trunk.
 We can't do this unless we give up the notion that WSJT, MAP65, WSPR,
 WSPR-X, and WSJT-X are all part of the same project.  Historically,
 the trunk: of the project is WSJT.

Bill:
 Not a problem. Multi project repos usually have
 project1/{trunk,branches,tags} project2/{trunk,branches,tags} etc..

 The reason it is important is that most other source control systems
 have much stronger concepts for branches and tags and moving to them
 while maintaining all history is normally supported with tools if you
 have a conventional repo layout.

 It's not critical or urgent but an example use case is my situation. I
 use git-svn because it gives me lots of excellent git features while
 working with svn but because of our repo layout I can't easily have two
 projects checked out at once ...

I'm sure you have far more experience with such things than I do.  Maybe 
it's not just what you want, but I nearly always have the main branch 
all of our programs -- WSJT, MAP65, WSPR, WSPR-X, and WSJT-X -- checked 
out at once, and the SVN-versioned documentation for them as well. 
Switching between them is no problem at all, I just open a new 
command-line terminal and cd to the right place.

Quite possibly, I'm missing something here -- or don't know about some 
important feature(s) that you want.

For the record, I have no reason not to like a layout such as 
project1/{trunk,branches,tags} project2/{trunk,branches,tags} etc., 
except that it's not what we have now -- and as yet I don't appreciate 
why it might be better.

Bill:
 because it expects everything to reside in
 the trunk with only branches and tags in their respective locations. For
 example if I want to build the docs I have to switch my working tree to
 docs, another branch, which hides the branch I was on 'wsjtx' while I'm
 there. This is the main reason that I don't edit the docs or contribute
 to other JT projects as it is so painful to coerce git-svn to bend the
 standard layout rules.

If there's a significant reason why it's inconvenient for you to edit 
the docs or contribute to the other JT programs, we should certainly 
address it.  But since I don't find such multi-tasking inconvenient at 
all, I need to better understand the problem.

-- 73, Joe, K1JT

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Credits mismatch

[Joe Taylor]

Hi Greg,

For what it's worth: on my rather elderly Linux box running (X)ubuntu 
14.04, hamlib is built without problems.  But the machine is brought to 
a crawl (presumably with very many page faults?) when trying to build 
wsjtx.  I notice many copies of cc1plus are running in parallel.  I 
removed the -j... flag on the call to make, but still no joy.  The 
machine is a Xeon with 2 processors and 1 GB memory.  It builds wsjtx 
without problems from within jtsdk.

FYI: I'll be tied up all day tomorrow (Saturday).

-- Joe

On 9/26/2014 5:22 AM, ki7mt wrote:
 Hi David, All,

 I use a script on new VM's (clones from unmodified VM installs) to
 perform quick build tests with. I added a modified version to JTSDK-NIX
 that incorporates all of Bills latest updates for the rc1 build as well
 as, the HEAD development branch ../wsjtx This script is only for WSJT-X.

 It's a single stand-alone script (nothing fancy, with minimal error
 handling), setup and tested on Ubuntu 14.04 amd64, i386 (which I'm on
 now), Debian Sid and Jessie. With the exception of the package list
 section, it should run on most Linux distros. Update that section as
 needed for package manager / package list for other distro's. It should
 be run from a temp location, does *not* install Hamlib3, only builds it
 for use with Cmake. Deleting the temp folder rids the system of
 everything other than the installed deps, which is better left to the
 user to determine if they should be removed or not.

 *EXPECTATIONS ( the scripts trys to )
 *---
 -Install Build and Runtime Deps
 -Checkout and Build Bill's Hamlib3
 -Perform a Basic Hamlib3 test
 -Checkout / Update WSJT-X from SVN
 -Configure / Build Release Tree
 -Build the WSJT-X Install Target
 -Yield a fully working WSJT-X application
 -It *does not* build the Manpages. If you want them, you can edit the
 package list, add AsciiDoc and remove -D WSJT_SKIP_MANPAGES=ON from the
 build tree config invocation.

 *USAGE*
 -
 Open a terminal
 mkdir ~/temp
 cd ~/temp
 svn export
 https://svn.code.sf.net/p/wsjt/wsjt/branches/jtsdk/nix/scripts/wsjtx-build.sh


 * Two Build Options:

 Build the Current Dev Branch

 *./wsjtx-build.sh*

 Final Location: ~/temp/wsjtx/install/Release/bin

 and / or

 Build The Release Candidate

 *./wsjtx-build.sh rc1*

 Final location: ~/temp/wsjtx-1.4.0-rc1/install/Release/bin

 When your finished testing, simply delete ~/temp if you no longer need
 it. If you have any troubles, let me know, I'm sure we can get it sorted
 out.

 73's
 Greg, KI7MT


 Hi Joe and all.i have just done an update of WSJT-X using a script i
 put together from the origional lines for cmake sent out by Bill
 im now showing WSJT-X v1.5.0-c1 r4375
 looks goodwill check it all out and report any problems

 Bill...im still using your origonal hamlib 3 files you sent out...do i
 have to upgradethe instructions you sent out for the upgrade look a
 bit daunting

 73 David VK4BDJ



 On 26/09/14 05:50, Joe Taylor wrote:
 Mike --

 Credits mismatch between About window and the manual
 Thanks for catching this discrepancy. The online manual has been fixed;
 we'll need to correct the list in About in rc2.

 -- Joe, K1JT

 --

 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
 http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk

 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel





 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
 http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk



 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel

[wsjt-devel] Release of WSJT-X 1.4.0

[Joe Taylor]

Hi all,

Tomorrow I plan to post several updated web pages at the *WSJT Home 
Page*, http://physics.princeton.edu/pulsar/K1JT/ .  The revised page for 
WSJT-X will include instructions and links to WSJT-X version 1.4.0 
installation files, as follows:

Windows:

wsjtx-1.4.0-rc2-win32.exe

Linux:

wsjtx_1.4.0-rc2_i386.deb(for Debian, Ubuntu, etc.)
wsjtx_1.4.0-rc2_amd64.deb   (64-bit)
wsjtx-1.4.0-rc2.i686.rpm(for Fedora, Red Hat, etc.)
wsjtx-1.4.0-rc2.x86_64.rpm  (64-bit)

Macintosh:

WSJT-X_rc1_10.7.dmg  (for OS X 10.7, 10.8)
WSJT-X_rc1_10.9.dmg  (for OS X 10.9)

Source Code:

wsjtx-1.4.0-rc2-Source.tar.gz


I will also post public messages to the wsjt-devel and wsjtgroup 
reflectors announcing availability of these beta releases of WSJT-X 1.4.0.

PLEASE: If you find errors or anything that could be improved in the new 
WSJT-X User Guide that will be posted tomorrow, do let me know! 
Compiled binaries for our release candidates are frozen as they now 
stand, but the User Guide will continue to be improved, as needed.

-- 73, Joe, K1JT

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Double-click causes unnecessary changes of VFO A ?

[Joe Taylor]

I have noticed that when operating in Split mode, double-clicking on a 
line of decoded text causes a momentary change of VFO A frequency, 
whenever the final result will also change the frequency of VFO B.

Yes, at the end VFO A is reset back where it should be; but why is it 
changed, at all?  Is this necessary?  It causes a brief gap in received 
audio, presumably degrading (slightly) the chances for successful decodes.

-- Joe, K1JT

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

[Joe Taylor]

Greg --

SVN revisions 4425 and 4426 break everything here.

I think all that's needed is

SET LIBRARY_PATH=

in jtsdk-qtenv.bat, and possibly also in jtsdk-pyenv.bat.  Don't put 
LIBRARY_PATH into PATH... they're two different things.  You don't use 
LIBRARY_PATH anywhere in your scripts, but some of the tools do.  We 
want it defined as NULL, even if a user normally has it set otherwise 
(for use in other environments).

-- Joe

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] LIBRARY_PATH in JTSDK-QT

[Joe Taylor]

RR, 4427 is OK.

But if LIBRARY_PATH defined to be a NULL string, why include it in PATH 
at all?

-- Joe

On 10/1/2014 2:40 PM, KI7MT wrote:
 Hi Joe,

 Yes, it did here too. Had to move the %LIBRARY_PATH% to the end of the
 %PATH%

 Should be ok now, I just built WSPR and WSJT-X

 73's
 Greg, KI7MT




 On 10/1/2014 18:34, Joe Taylor wrote:
 Greg --

 SVN revisions 4425 and 4426 break everything here.

 I think all that's needed is

  SET LIBRARY_PATH=

 in jtsdk-qtenv.bat, and possibly also in jtsdk-pyenv.bat.  Don't put
 LIBRARY_PATH into PATH... they're two different things.  You don't use
 LIBRARY_PATH anywhere in your scripts, but some of the tools do.  We
 want it defined as NULL, even if a user normally has it set otherwise
 (for use in other environments).

  -- Joe

 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
 http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt-x html manual date

[Joe Taylor]

Thanks, Sandro!  Probably the script(s) should be modified so that the 
local copy of wsjtx-main.html is always deleted and a new copy is 
downloaded.

Please join the wsjt-devel mailing list -- otherwise your posts will 
always require administrator approval.

-- Joe, K1JT

On 10/2/2014 12:17 PM, Alessandro Gorobey wrote:

 Hi all,
 I respond to myself.
 When I compile a debug, release or package wsjtx the manual used is
 downloaded from WSJT main page, not from C:/JTSDK-DOC/doc/wsjtx.
 If wsjtx-main.html is present it is NOT downloaded.

 Manually remove it from the build directory, eg.:
 C:\JTSDK-QT\wsjtx\build\Release\contrib
 C:\JTSDK-QT\wsjtx-1.4\build\Release\contrib
 .
 The cmake download the last version.

 73's Sandro IW3RAB

 Hi all,

 I noticed that last line of wsjtx-main.html manual contain different
 dates:

 http://physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main.html
 Last updated 2014-10-01 09:50:46 EDT

 http://physics.princeton.edu/pulsar/K1JT/wsjtx-1.4.0-rc2-win32.exe after
 installation
 Last updated 2014-09-25 11:16:20 EDT

 Compiled on my PC:

 file:///C:/JTSDK-DOC/doc/wsjtx/wsjtx-main.html
 Last updated 2014-10-01 16:18:56 ora legale Europa occidentale (it is
 compiled on an Italian OS)

 file:///C:/JTSDK-QT/wsjtx-1.4/install/Release/bin/doc/wsjtx-main.html
 Last updated 2014-09-25 11:16:20 EDT

 file:///C:/JTSDK-QT/wsjtx/install/Release/bin/doc/wsjtx-main.html
 Last updated 2014-09-25 11:16:20 EDT

 Seem that svn update only the C:/JTSDK-DOC not also C:/JTSDK-QT

 73's Sandro IW3RAB









 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
 http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk



 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] CW synthesizer

[Joe Taylor]

Bill --

For what it's worth: the CW ID message with shaping sounds very good on 
all systems I've tested.

-- Joe, K1JT

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Fwd: Back on dry land...

[Joe Taylor]

Hi all,

For the record, I have copied below a few messages sent by WSJT-X v1.4
users to me directly.  Bill, in particular, might want to respond to some.

-- Joe

###
 Original Message 
Subject: Latest WSJT x ver 1.4
Date: Sat, 4 Oct 2014 20:08:04 +0100
From: David Sylvester daveg3...@ntlworld.com
To: k...@arrl.net k...@arrl.net

Hi
I have downloaded this , I can get it to read the txt freq. I have an
ic7800 and signalink.
The test ptt is greyed out ? Version 1.3. Works!
Any ideas?
Dave de g3red

###
 Original Message 
Subject: WSJTX 1.4.0-rc2-win32
Date: Sun, 5 Oct 2014 08:34:05 +0400
From: Serge Smirnoff R6YY r...@r6yy.ru
To: k...@arrl.net

Hi Joe,
Thanks for the new version WSJTX.
1.4.0-rc2-win32 is stable. Early versions of the program randomly
stopped working and folded.
My problems:
1. CAT does not work together PowerSDR.
2. PTT does not work.

TRX Hermes w PowerSDR mrx PS
Desktop Core I5-3470, RAM 4gb, NVidia GF GT 440, WinXP SP3

73, Serge R6YY

###
 Original Message 
Subject: wsjtx-1.4.0-rc2-win32.exe
Date: Sun, 5 Oct 2014 16:29:53 +
From: Bob Wilton bmwil...@live.com
To: k...@arrl.net k...@arrl.net

Hi Joe,


I have 1.3 installed and then I tried to download the beta 1.4 and my
virus software (Vipre) intercepted the file and said there was a Trojan
in this file. It could be my virus software, but I thought I would send
you a note just in case.


Bob

KF5TPQ

 Original Message 
Subject: Fwd: wsjtx-1.4.0-rc2-win32.exe
Date: Sun, 5 Oct 2014 13:18:46 -0400
From: Bob Wilton bmwil...@live.com
To: k...@arrl.net

Hi Joe,

I have submitted this to Vipre Tech Support (ThreatTrack Security) and
their analysis will check to see if it was a false positive detection. I
will send you a quick note when I hear back from them.

Bob
KF5TPQ

###
 Original Message 
Subject: RE: WSJTX 1.4 beta testing
Date: Mon, 6 Oct 2014 07:15:36 +
From: Pollet, Johan (Johan) johan.pol...@alcatel-lucent.com
To: Joe Taylor j...@princeton.edu

Hi Joe,

The problem is that there is a misunderstanding or not understanding the
modes supported
by HRD when using it with PowerSDR.

I have a flex-3000 connected: (working with previous version of WSJTX)

HRD talks with PowerSDR and when selecting DIGU that's to be used in
digimodes WSJTX doesn't understand
that mode.

Is there a way to enable more detailed tracing in WSJTX ?

Rgds
73 de ON3VNA

Johan

###
-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Friday, October 03, 2014 2:51 PM
To: Pollet, Johan (Johan)
Subject: Re: WSJTX 1.4 beta testing

Johan --

Many others are using HRD without problems, and we have tested it
extensively, so I think you must have something configured wrong.

 Last night I installed the beta version to test it out with HRD V5,
 but is doesn't seem to want to talk to HRD.

 When doing test CAT command I get error invalid mode sent.

This message implies that the program *is* talking to HRD, but HRD does
not like what it receives for Mode.  Have you specified a Mode not
supported by your radio?

Perhaps you have already solved your problem.  If not, I suggest that
you post a more detailed description of what you have done, and what
seems not to work, on the wsjtgroup email reflector.

-- 73, Joe, K1JT

###



--
Slashdot TV.  Videos for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FFT question

[Joe Taylor]

W9MDB wrote:
 As a bit of an FFT nut I was wondering about the fidelity of the FFT's done
 in JT65 and JT9.
...
 My question has to do with how the frequencies in the modes correspond to
 the bins in the FFT?

 If they aren't exact multiples of those bin frequencies a lot of energy in
 the FFT will be put into side frequencies.

 Does the code allow for this spreading of the energy that will occur for
 such frequency mismatches or are the frequencies made to take this into
 account?

The WSJT modes are all motivated by the goal of getting the most out of 
very weak signals -- think EME and the like.  So yes, you should expect 
that the decoders are coded to do the best possible job with whatever 
signal is available.  Moreover, oscillators in our radios are not 
perfectly stable, and EME Doppler shifts change significantly with time, 
even over a single WSJT transmission.  Decoding software must be able to 
cope with such effects without losing much sensitivity.

 I looked a bit at the coding and it's pretty obtuse so wasn't sure how to
 examine this.

You give no indication of where you were looking in the code, or what 
functions you considered pretty obtuse, so it's hard to know where you 
might want help.  But it never hurts to start with the available 
documentation.

For JT65 read the 2005 paper in QEX describing the protocol and its 
implementation.  (Go to the WSJT Home Page,
http://physics.princeton.edu/pulsar/K1JT/ ; click on References at the 
left, and then on entry #4 in the list.)  In WSJT-X the procedures 
described in Section 9 of that paper take place in subroutine 
decode65a.f90 and routines called therein.

For JT9 start with Section 13, Implementation Details, in the WSJT-X 
User Guide:
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main.html#TXRX
You can follow the sequence of DSP operations there, and then look at 
the code for additional details.

-- 73, Joe, K1JT

--
Slashdot TV.  Videos for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Problem with v 1.4.0-rc2: no Log-file created

[Joe Taylor]

Alois --

On 10/6/2014 4:59 PM, Alois Windpassinger wrote:
 Sri Bill, there ist no .adi-File on My harddrives...so what can I do?

 Thanks Alois,  DL8RBL

Open Windows Explorer and copy-and-paste this exact line into the 
address field at its top:

%APPDATA%\..\Local\WSJT-X\

You will then see a listing of files in the WSJT-X writeable-files 
directory, including your ADIF log file.

-- 73, Joe, K1JT

--
Slashdot TV.  Videos for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X Beta Version 1.4 -- Report

[Joe Taylor]

Hi Paul,

Thanks for calling my attention to the fact that the second message 
under Calling CQ on Tab 2 is not generated correctly.  It will be 
fixed in the next release.

On Tab 1 I am presently inclined to leave things as they are.  The idea 
is that when you double-click on, say, CQ DL1SBY JN49 the 
automatically generated messages on Tab 1 give you the choice of 
responding with Tx1 (DL1SBY WA8UGN PK08) or Tx2 (DE DU2/WA8UGN 
PK08).  Tx1 is usually preferred, and therefore the default.  It makes 
it perfectly clear who you are calling, but it does not identify your 
special status in DU2 and probably does not contain your legally 
assigned callsign.  Tx2 satisfies these concerns, but DL1SBY might not 
realize you are calling him.

If you are using Tab 1 and calling CQ, double-clicking on a responding 
callsign will automatically generate something like
DL1SBY WA8UGN R-15 for Tx3.  You can use this to respond; or better 
still, use Tx3 but manually change R-15 to -15.

We could, of course, generate DL1SBY WA8UGN -15 for Tx2... it's a 
judgment call whether that would be more useful than generating
DE DU2/WA8UGN PK08.

I am taking the liberty of copying this response to the wsjt-devel 
mailing list, so that others in our development group will know what we 
have discussed.

-- 73, Joe, K1JT

On 10/7/2014 10:51 AM, Paul Keating wrote:
 Am testing  “wstjx-1.4.0-rc2”  (Beta Version 1.4) and noted a problem when
 generating standard messages:

 For either Tab 1 Message “Tx 2” or Tab 2 Message “dB” the beta program does
 not generate the proper message of “Call1 Call2 dB”  but generates the
 message of “DE Call2 Locn” in its place.

 Problem appears to be peculiar to “My Call” using a portable designator and
 10 characters in length.

 Examples of all messages generated, using “My Call” of DU2/WA8UGN:

Tab 1Tab 2

 DL1SBY WA8UGN PK08   Tx 1 CQ:CQ DU2/WA8UGN PK0
 DE DU2/WA8UGN PK08   Tx 2 Grid:  DL1SBY WA8UGN PK08
 DL1SBY WA8UGN R-15   Tx 3 Db:DE DU2/WA8UGN PK08 ß
 DL1SBY WA8UGN RRRTx 4 R+Db:  DL1SBY WA8UGN R-15
 DE DU2/WA8UGN 73 Tx 5 RRR:   DL1SBY WA8UGN RRR
 CQ DU2/WA8UGN PK08   Tx 6 73:DE DU2/WA8UGN 73

 In “WSJT-X v1.3, r3673,” a similar problem exists, but only on Tab 2 Message
 “Grid” (so work-around via Tab 1 is possible):

Tab 1Tab 2

 DE DU2/WA8UGN PK08   Tx 1 CQ:CQ DU2/WA8UGN PK08
 DL1SBY WA8UGN -10Tx 2 Grid:  DE DU2/WA8UGN PK08 ß
 DL1SBY WA8UGN R-15   Tx 3 Db:DL1SBY WA8UGN -10
 DL1SBY WA8UGN RRRTx 4 R+Db:  DL1SBY WA8UGN R-15
 DE DU2/WA8UGN 73 Tx 5 RRR:   DL1SBY WA8UGN RRR
 CQ DU2/WA8UGN PK08   Tx 6 73:DE DU2/WA8UGN 73

 Platform:  SONY VAIO model VPCCB25FX
 O/S:  Windows 7
 Interface:  SignaLink USB
 Ancillary Program:  JTAlert-X 2.4.20

 Best regards  73,

 Paul A. Keating
 DU2/WA8UGN
 Pasuquin, Ilocos Norte, Philippines

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X Beta Version 1.4 -- Report

[Joe Taylor]

W9MDB wrote:
 I noticed this morning when working W1AW/6 that the only message generated
 with W1AW/6 was TX 2 and it had W1AW/6 W9MDB with no signal report.
 All others just had the first 4.  Shouldn't all messages be able to contain
 W1AW/6 since it's six letters?

No, because W1AW/6 is a compound callsign.

I could spell out much more about why these must be treated differently 
here, but for completeness it's better for you to read the existing 
documentation.

For details on acceptable messages in the JT65 (and JT9) protocols, see 
the WSJT-X User Guide at
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main.html#PROTOCOLS
and
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main.html#COMP-CALL

To understand the motivation for such restrictions, see the original QEX 
paper on the JT65 protocol:
http://physics.princeton.edu/pulsar/K1JT/JT65.pdf

You might also want to experiment with the utility programs 
jt9code[.exe] and jt65code[.exe].  They are described in the WSJT-X User 
Guide at
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main.html#UTIL

-- 73, Joe, K1JT

--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Fwd: Re: WSJT-X Beta Version 1.4 -- Report

[Joe Taylor]

Follow-up, for information on the wsjt-devel list:

 Original Message 
Subject: Re: WSJT-X Beta Version 1.4 -- Report
Date: Wed, 8 Oct 2014 18:49:05 +0800
From: Paul A. Keating keat...@msn.com
To: Joe Taylor j...@princeton.edu

QSL, Joe -

Agree with all you say - have been using work-arounds quite frequently 
to help the uninitiated realize that I am calling them and not just 
throwing QRM their way!  ;-)

Thanks for considering my input.  Am waiting for that next release as 
Version 1.4 is (IMHO) a considerable step up.

73  GL,

Paul DU2/WA8UGN



Sent from my Xperia™ tablet

 Joe Taylor wrote 

Hi Paul,

Thanks for calling my attention to the fact that the second message
under Calling CQ on Tab 2 is not generated correctly.  It will be
fixed in the next release.

On Tab 1 I am presently inclined to leave things as they are.  The idea
is that when you double-click on, say, CQ DL1SBY JN49 the
automatically generated messages on Tab 1 give you the choice of
responding with Tx1 (DL1SBY WA8UGN PK08) or Tx2 (DE DU2/WA8UGN
PK08).  Tx1 is usually preferred, and therefore the default.  It makes
it perfectly clear who you are calling, but it does not identify your
special status in DU2 and probably does not contain your legally
assigned callsign.  Tx2 satisfies these concerns, but DL1SBY might not
realize you are calling him.

If you are using Tab 1 and calling CQ, double-clicking on a responding
callsign will automatically generate something like
DL1SBY WA8UGN R-15 for Tx3.  You can use this to respond; or better
still, use Tx3 but manually change R-15 to -15.

We could, of course, generate DL1SBY WA8UGN -15 for Tx2... it's a
judgment call whether that would be more useful than generating
DE DU2/WA8UGN PK08.

I am taking the liberty of copying this response to the wsjt-devel
mailing list, so that others in our development group will know what we
have discussed.

   -- 73, Joe, K1JT

On 10/7/2014 10:51 AM, Paul Keating wrote:
 Am testing  “wstjx-1.4.0-rc2”  (Beta Version 1.4) and noted a problem when
 generating standard messages:

 For either Tab 1 Message “Tx 2” or Tab 2 Message “dB” the beta program does
 not generate the proper message of “Call1 Call2 dB”  but generates the
 message of “DE Call2 Locn” in its place.

 Problem appears to be peculiar to “My Call” using a portable designator and
 10 characters in length.

 Examples of all messages generated, using “My Call” of DU2/WA8UGN:

Tab 1Tab 2

 DL1SBY WA8UGN PK08   Tx 1 CQ:CQ DU2/WA8UGN PK0
 DE DU2/WA8UGN PK08   Tx 2 Grid:  DL1SBY WA8UGN PK08
 DL1SBY WA8UGN R-15   Tx 3 Db:DE DU2/WA8UGN PK08 ß
 DL1SBY WA8UGN RRRTx 4 R+Db:  DL1SBY WA8UGN R-15
 DE DU2/WA8UGN 73 Tx 5 RRR:   DL1SBY WA8UGN RRR
 CQ DU2/WA8UGN PK08   Tx 6 73:DE DU2/WA8UGN 73

 In “WSJT-X v1.3, r3673,” a similar problem exists, but only on Tab 2 Message
 “Grid” (so work-around via Tab 1 is possible):

Tab 1Tab 2

 DE DU2/WA8UGN PK08   Tx 1 CQ:CQ DU2/WA8UGN PK08
 DL1SBY WA8UGN -10Tx 2 Grid:  DE DU2/WA8UGN PK08 ß
 DL1SBY WA8UGN R-15   Tx 3 Db:DL1SBY WA8UGN -10
 DL1SBY WA8UGN RRRTx 4 R+Db:  DL1SBY WA8UGN R-15
 DE DU2/WA8UGN 73 Tx 5 RRR:   DL1SBY WA8UGN RRR
 CQ DU2/WA8UGN PK08   Tx 6 73:DE DU2/WA8UGN 73

 Platform:  SONY VAIO model VPCCB25FX
 O/S:  Windows 7
 Interface:  SignaLink USB
 Ancillary Program:  JTAlert-X 2.4.20

 Best regards  73,

 Paul A. Keating
 DU2/WA8UGN
 Pasuquin, Ilocos Norte, Philippines


--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT Developers Guide

[Joe Taylor]

Hi Alessandro,

You are correct: the posted version of file wsjt-dev-guide.html is very 
old, and has now been deleted.  I have posted instead a current copy of
http://physics.princeton.edu/pulsar/K1JT/wsjtx-doc/dev-guide-main.html

It is not complete, but is currently the best we have.

Thanks for catching the typo in the source file environment.adoc, also!

-- 73, Joe, K1JT

On 10/11/2014 7:36 PM, Alessandro Gorobey wrote:
 Hi All,

 Just a small clarification on dev-guide.

 http://physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjt-dev-guide.html
 contain a lot of references to svn.berlios.de

 It will be replaced with
 file:///C:/JTSDK-DOC/doc/dev-guide/dev-guide-main.html
 when completed?

 Note:
 branches/doc/dev-guide/source/environment.adoc
 line 89 contain Souorce instead of Source

 73
 Sandro
 IW3RAB



 --
 Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
 Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
 Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
 Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
 http://p.sf.net/sfu/Zoho



 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Compiler hassles

[Joe Taylor]

I have spent 1.5 days trying to understand why kvasd[.exe], the 
Koetter-Vardy algebraic soft-decision decoder, compiled correctly with 
versions 4.6.1 and 4.6.3 of gcc and gfortran, but fails with versions 
4.8.1 and 4.8.2.

With the code as it has been for some years, the build appears 
successful but the program fails to execute correctly.

After scratching my head with long gcc/gdb debugging sessions, I 
discovered that the combination clang (v3.5) + gfortran 4.8.2 worked 
perfectly.  More importantly, clang identified the problem.

Ralf Koetter's code used a number of constructions like the following:

   for (y = m2-1-x; y; ) d[y--] = p[y];

The clang compiler flagged these with warnings like this:

   warning: unsequenced modification and access to 'y'

 From context it's clear that the intended ordering is to decrement y 
after the copy operation.  An unambiguous way to write the statement is thus

   for (y = m2-1-x; y; y--) d[y] = p[y];

Somewhere between gcc 4.6.3 and gcc 4.8.1, the GNU folks did something 
that changed the ordering of copy and decrement in the original statement.

Anyway, the good news is that I fixed all the ambiguous unsequenced 
modifications, and the code now executes correctly with all the 
compilers I've been testing.

Three cheers for clang!!!

-- Joe, K1JT

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Threading

[Joe Taylor]

Hi Mike,

On 10/16/2014 4:12 PM, Michael Black wrote:
 Has any thought or attempt been given to multi-threading the decoding
 process?

To what end?  Are you concerned about decoding speed?  Have you looked 
at the statistics in file 'timer.out', results from the built-in 
execution profiler for jt9.exe ?

-- Joe, K1JT

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Compiler hassles

[Joe Taylor]

Hi Diane,

 O!! Perhaps we can get a version compiled up for FreeBSD now? This
 is exactly what we saw the last time you compiled up kvasd for FreeBSD.
 No output except 0's.

By all means -- let me know how best to proceed!

-- Joe, K1JT

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Threading

[Joe Taylor]

On 10/17/2014 12:59 PM, Michael Black wrote:
 Is showing up all at once a problem?

None of this is a problem, as far as I'm aware.

Is showing up all at once undesirable?  Yes, if that means that the 
first decode shows up later than it otherwise would have.  The first 
decode is always the one at your selected Rx frequency.  That's the 
station you're working, and you want to see his message as soon as possible.

 That flush could be adding 10's of MS per decode.

I think a test will show you that this estimate is orders-of-magnitude 
too large.
-- Joe

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Omnirig.h is nonexisting

[Joe Taylor]

Hi Matthias,

You are correct that Omnirig.h is included not in the tarfile.  It is 
created during the build procedure using CMake.

If you need help in building WSJT-X, you might want to join the 
wsjt-devel email list.

-- 73, Joe, K1JT

On 10/17/2014 1:58 PM, Matthias Buchwald wrote:
 Hallo Joe,
 I think in 'wsjtx-1.4.0-rc2-Source.tar.gz' is a error. In
 'OmnirigTransceiver.hpp' is calling the 'Omnirig.h'-file but is nowhere
 in the projekt.

 Sorry for my bad english - 73 de Matthias, DL3VCO

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Routines common to WSJT, WSJT-X, etc

[Joe Taylor]

Hi all,

Bill responded to a recent query on wsjtgroup about the use of compound 
callsigns.

As we all know, these are bit of a nuisance in JT65, JT9, and JT4, in 
part because of the need to maintain backward compatibility with the 
original JT65 protocol specification, defined more than ten years ago.

The original question posed by KE4PT was this:

 Suppose I am operating as ZL/KE4PT.
 Suppose I hear:   CQ N8PR EL96 calling and SNR = -20

 I wish to generate message, and expect to find the generated message:
   N8PR ZL/KE4PT
 in the Grid button, or the TX2 message, but instead WSJT-X 1.4 generates:
   N8PR KE4PT -20
 thus N8PR never knows that ZL/KE4PT answered his CQ.

Of course, a savvy user would edit the automatically generated message 
so that N8PR ZL/KE4PT is sent.  That's a legal message, because ZL 
is one of the 339 standard prefixes defined in pfx.f90.  They are 
legitimate for the compound-callsign messages we call Type 1 in the 
WSJT-X User Guide.

However, suppose the authorities in ZL required him to sign his call as 
ZL3/KE4PT.  ZL3 is not in the list of standard prefixes, so he must use 
Type 2 messages.  The automatic message-generating facility in WSJT-X 
assumes that Type 2 messages will be used.

In fact we could do slightly better for users.  The program could 
generate Type 1 messages when possible, and Type 2 otherwise.  I would 
see about making such a change... but it occurs to me that now might be 
the right time to do something that we have been putting off.

For consistency it would be better, by far, to put all the pack/unpack 
routines (and a few support routines) in a separate library of their 
own.  That library should be used by our Qt-based programs (WSJT-X and 
MAP65) and also by the Python-based WSJT -- in short, by any program 
that uses the 72-bit compressed messages pioneered by JT65.

I would be happy to hear opinions from others about how best to organize 
the code for such a separate library.  I suppose it should be something 
like making a new SVN branch, say packmsg, for the pack/unpack source 
code, and having the relevant build scripts go there to build the 
library.  Does this sound right?

-- Joe, K1JT

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Routines common to WSJT, WSJT-X, etc

[Joe Taylor]

Hi Bill,

 Of course, a savvy user would edit the automatically generated message
 so that N8PR ZL/KE4PT is sent.  That's a legal message, because ZL
 is one of the 339 standard prefixes defined in pfx.f90.  They are
 legitimate for the compound-callsign messages we call Type 1 in the
 WSJT-X User Guide.
 Oops, so my answer was partially incorrect and I should have suggested
 that as another alternative.

 Also that particular example response you give is valid as a free text
 message.

One might think so; but in fact it won't be encoded and sent as one. Nor 
would the message N8PR XL/KE4PT, which also has 13 characters.  Try it 
with jt65code or jt9code to see what happens.

I agree that our repository could have a more logical layout.  By all 
means, let's arrange to build the common library with CMake.

I had a brief try at using git-svn.  I found it usable but not 
immediately advantageous.  Perhaps I would change my mind, in the 
fullness of time. ;-)

-- Joe

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JT9 freq range

[Joe Taylor]

Mike --

On 10/13/2014 5:50 PM, Michael Black wrote:
 I just made a boo-boo which I think could have been prevented.

 I had the JT9 frequency range set to JT65 2600 JT9.  I had my offset set
 to 2600 also.  I couldn't decode anything.

 So perhaps WSJT-X shouldn't let you transmit JT9 at or near the cutoff
 frequency?  Perhaps at least 10Hz above it?

I can't figure out what this was about.

I tried to reproduce what you describe.  I set the blue dividing line to 
JT65 2600 JT9, and the Tx and Rx frequencies both to 2600.  Received 
signals in both modes continue to decode as usual.

If you think there is a bug, or some undesirable behavior, could you 
please provide a recipe for reproducing the problem?

-- Joe, K1JT

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Routines common to WSJT, WSJT-X, etc

[Joe Taylor]

Hi Greg,

About a possible common library:

 I would like to see any common libraries built with CMake, this is
 because CMake has powerful tools for exporting library code for use in
 other CMake built projects. This doesn't make them any less useful for
 non-CMake projects.
 Unless you plan on coveting WSJT and / or WSPR over to Cmake, I
 wouldn’t' want to deal with this at all, WSPR may not factor in, but
 still. The builds for those two packages are already hybrids, adding a
 third layer would compound things further. I'm sure there is a long list
 of reasons why X is better that Y, but, seems to me, there are plenty of
 fish to fry, so no urgent need to go throw a line in the water :-)

It may not need to be very complicated.  A simple CMakeLists.txt (or a 
simple Makefile) can build the library, say libpackmsg.a, from sources 
moved into a new branch.  Building the library would be a prerequisite 
to building the programs, and would be managed by the CMakeLists.txt 
file (WSJT-X and MAP65) or Makefile.jtsdk (WSJT).

 I certainly see the benefits of having a common library set, but if
 that's to be done, do them all, not just one or two for a particular
 need. Clearly a roadmap of some kind could be beneficial here, maybe
 include long term integration plans for all the apps, if that is on the
 cards.

It's mainly the message packing and unpacking that needs to be 
consistent across all three programs.  As you say, there is other 
potentially common code as well; but the benefits of making all of that 
code uniform across all programs are much smaller.

 A few months back, 6+ or so, I tried to do some commonality checks
 between the different .F90 / .f90 files. I found allot of delta's, but I
 had no way of knowing which file was truth, so, kinda of gave up on that
 adventure. I think this would be benifical for sure, but do them all,
 and publish the libs.

Those deltas, of course, are the main motivation for maintaining a 
single set of source files.

-- Joe, K1JT

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Routines common to WSJT, WSJT-X, etc

[Joe Taylor]

Hi Bill and Greg,

 Of course you are correct but I see Greg's point too. I expect he is
 concerned about the complexities of delivering an application on Linux
 for example where the whole thing must be built from sources plus
 existing packages. A statement like Building the library would be a
 prerequisite to building the program ... is not trivial in the package
 building world because the prerequisite build has to be part of the
 product build. This is because the only binary inputs to the packaging
 process allowed are other already in place packages.

 We have just attacked that same problem for WSJT-X where an autoconf
 based hamlib build must be aggregated with the CMake WSJT-X build.
 Fortunately in that case CMake provides the tools as we have
 demonstrated with the new wsjtx-superbuild project. The same probably
 isn't true of an autoconf based project which I believe some of our
 applications are.
  ...
 I can see a few other possibilities like rig control, location, distance
 and, bearing functions.

No need to rush into this.

When I find time, I'll make a list of all routines that are common to 
WSJT, MAP65, and WSJT-X and probably should be identical in all three 
programs.  (Probably not rig control, since neither WSJT not MAP65 does 
this; but there are many others...)

Then I'll look into why they are presently different, and what needs to 
be done to remove the differences.

-- Joe

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X USB/DATA recognition observation

[Joe Taylor]

Hi Bill,

I am copying this brief reply to the wsjt-devel list, where I'm sure one 
of our group working with HRD can get you straightened out.

You'll need to specify which version of WSJT-X you are using.

-- Joe, K1JT

On 10/18/2014 2:21 PM, N7ZAL wrote:
 Hi Joe:

 First, thanks for developing JT-65, a great mode that I
 enjoy...especially being able to work worldwide QRP.

 I'm using a FT-450D, SignaLink USB interface, Windows 7, and RT systems
 CAT cable.

 I'm evaluating a trial version of Ham Radio Deluxe and have noticed an
 issue (I think) with the WSJT-X program. I run the rig in USB/DATA. If
 the HRD is set up with the USB/DATA mode, and I start the WSJT-X, I get
 an error indicating the HRD sent an unrecognized mode. The WSJT-X
 works fine by its self with the USB/DATA mode.

 73's
 Bill
 N7ZAL

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Feedback on the latest WSJTX beta

[Joe Taylor]

Hi Chris,

Obviously we can't test every possible rig and control software 
combination in advance, so we depend on reports like yours.  Most of the 
CAT-control issues are being handled by Bill, G4WJS, and usually he can 
fix such problems very quickly, once identified.  I am copying this 
brief reply to the wsjt-devel list.  You will probably hear from Bill 
soon, with a request for more info.

 -- 73, Joe, K1JT

On 10/19/2014 12:40 AM, Chris Long wrote:
 Thanks up front for all your hard work for the community. I for one really
 appreciate it.

 I can't get the latest beta to work as well (not really at all) as the 1.3
 release on my system. I am running a Flex5000A, Win7 x64 Ultimate, and I use
 DDUTIL to manage the CAT for me. DDUTIL has an HRD server function that
 takes the place of HRD itself, and allows HRD compatible programs to
 communicate with the Flex (HRD logbook, DM780, etc.). This function works
 fine with V1.3, but not with the beta. It throws an unrecognized command
 type error when I try and set up the CAT on V1.4 targeting HRD. Thought that
 you might want to know. Probably not a lot of Flexers out there, but most of
 us use DDUTIL so we can have multiple DSP apps using the same resources.

 73, and Cheers,

 Chris N1CL


--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Compound callsigns

[Joe Taylor]

Hi all,

Over the weekend I made some changes to the way WSJT-X generates 
suggested user messages when a compound callsign is involved.  I also 
made a minor change in the way the encoder decides when to use the 
free-text format in a message.  These changes are intended to make 
compound callsigns more convenient, when needed.

The original specification of the JT65 protocol included a list of 339 
DXCC prefixes, supposedly the most commonly used ones, plus 12 common 
single-character suffixes.  As described in Section 7.3 of the WSJT-X 
User Guide, they can be used to make Type 1 compound callsigns.  Other 
arbitrary prefixes (up to 4 characters) and suffixes (up to 3 
characters) may be used in Type 2 compound callsigns, with different 
restrictions in usage.

WSJT-X generates suggested messages automatically when the user clicks 
Generate Std Msgs on Tab 1 or one of the six buttons on Tab 2.  Here's 
a brief summary of what messages are affected by compound-callsign usage.

1. When MyCall is a Type 1 compound callsign, messages 1 and 6 contain 
the compound callsign as the second word.  Examples:

K1ABC ZL/W9XYZ  (Tx1, also Grid button on Tab 2)
CQ ZL/W9XYZ (Tx6, also CQ button on Tab 2)

All other messages use the base callsigns only (no prefix/suffix).

2. When MyCall is a Type 2 compound callsign, messages 2, 5, and 6 
contain the compound callsign as the second word.  Examples:

DE W9XYZ/VE1   (Tx2)
DE W9XYZ/VE1 73(Tx5, also 73 on Tab 2)
CQ W9XYZ/VE1 FN75  (Tx6, also CQ on Tab 2)

Message numbers 1 (Grid on Tab 2), 3 (R+dB) , and 4 (RRR) use the 
base callsigns only.

3. When HisCall is a Type 1 compound callsign, message 1 uses it as 
the first word.  Example:

ZL/K1ABC W9XYZ (Tx1, also Grid on Tab 2)

All other messages use the base callsigns only.

4. When HisCall is a Type 1 compound callsign, message 5 uses it as 
the first word.  Example:

K1ABC/VE1 73   (Tx5, also 73 on Tab 2)

All other messages use the base callsigns only.

[In the rare case where both MyCall and HisCall are compound, automatic 
message generation is not very useful.  Operators will need to edit 
messages manually, to be sure they will both know the full callsign of 
the station being worked.]

What happens if a user tries to send a message similar to the one in 
item #3 above, but with a prefix or suffix NOT in the short list?  For 
example, suppose the message is XL/K1ABC W9XYZ.  Since XL is not in 
the short list, XL/K1ABC is a Type 2 compound callsign.  But the first 
word in a message with a Type 2 compound callsigns must be CQ, QRZ, or 
DE.  Since the attempted message fails to satisfy either Type 1 or Type 
2 criteria, subroutine packmsg() encodes the first 13 characters as free 
text and sends XL/K1ABC W9XY.  This procedure may be useful for those 
with short callsigns.


These changes were made in the development branch, .../branches/wsjtx.

Should they be merged back into wsjtx-1.4?  This is a policy question, 
and I'm not sure or the proper answer.  The changes don't exactly fix a 
bug in v1.4-rc2; rather, they correct a perceived flaw in the way that 
version chose to generate messages automatically.

Your views on this matter would be welcome.  I would also appreciate any 
comments on whether you think the new code makes the best possible 
compromises for handling compound callsigns.

-- 73. Joe, K1JT

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Compound callsigns

[Joe Taylor]

PS to my message of a few minutes ago:

Perhaps we should also discuss whether the time for taggind and posting 
wsjtx-1.4.0-rc3 is approaching?  (Is that the proper nomenclature, or 
should it be wsjtx-1.4.1-rc1, or ???)

-- Joe

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] v1.4 release matters - was: Compound callsigns

[Joe Taylor]

Hi Bill and all,

 Perhaps we should also discuss whether the time for taggind and posting
 wsjtx-1.4.0-rc3 is approaching?  (Is that the proper nomenclature, or
 should it be wsjtx-1.4.1-rc1, or ???)
 Easy one first - wsjtx-1.4.0-rc3 since we haven't had a successful
 release candidate yet.

OK, agreed.  Also agree that we have a few more issues to sort out, 
before making another candidate release.

I'm inclined to think, then, that the changes I made to message 
generation should be considered as bug fixes and merged back into 
wsjtx-1.4 -- even though they do, in fact, add some new functionality.
Does this sound right?

And then a final question, so that I do this right.  I have parallel 
working directories for .../branches/wsjtx and .../branches/wsjtx-1.4.
Will the following commands do the desired merge?

  cd wsjtx
  svn merge -r4532:4544 ../wsjtx-1.4 .

-- Joe

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] v1.4 release matters - was: Compound callsigns

[Joe Taylor]

 And then a final question, so that I do this right.  I have parallel
 working directories for .../branches/wsjtx and .../branches/wsjtx-1.4.
 Will the following commands do the desired merge?

 cd wsjtx
 svn merge -r4532:4544 ../wsjtx-1.4 .

Sorry to be stupid about this.  I think the correct steps I should take 
to merge my changes (from r4533 to r4544) into .../branches/wsjtx-1.4 
are these:

 cd wsjtx-1.4
 svn up
 svn merge -r4532:4544 ../wsjtx .

Do I have it right, now?

-- Joe

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] v1.4 release matters - was: Compound callsigns

[Joe Taylor]

Many thanks, Bill -- your reply has exactly the help I needed.

-- Joe

On 10/20/2014 5:58 PM, Bill Somerville wrote:
 On 20/10/2014 20:20, Joe Taylor wrote:

 Hi Joe,
 And then a final question, so that I do this right.  I have parallel
 working directories for .../branches/wsjtx and .../branches/wsjtx-1.4.
 Will the following commands do the desired merge?

cd wsjtx
svn merge -r4532:4544 ../wsjtx-1.4 .
 Sorry to be stupid about this.  I think the correct steps I should take
 to merge my changes (from r4533 to r4544) into .../branches/wsjtx-1.4
 are these:

cd wsjtx-1.4
svn up
svn merge -r4532:4544 ../wsjtx .

 Do I have it right, now?
 No that includes changes other than yours which will cause issues.

 First think to note is that the way svn merge works is that the changes
 are applied to the current working directory but the source of the
 changes is the repository. So you only need a checkout of the
 destination branch to do a merge. It doesn't matter that you have
 another working directory, it just isn't relevant here.

 I tend to use the '-c' switch to select the changsets I wish to merge,
 that takes individual changeset numbers and IMHO is clearer than the
 '-r' version so long as the list of changesets to merge is not too long.
 So first I would list the changesets in the source branch to confirm I
 have the correct ones e.g.

 svn log -c4533,4534,4535,4536,4537,4540,4544 ^/branches/wsjtx

 This command is standalone as it references the repository only.

 Once you are happy that you have the correct changesets, you can then do
 the merge in a destination branch workspace. So in your workspace that
 has the wsjtx-1.4 branch checkout:

 svn merge -c4533,4534,4535,4536,4537,4540,4544 ^/branches/wsjtx

 Note that this is conveniently the same as the log command above with
 'merge' substituted for 'log'. That will update your workspace with the
 results of the merge. Then resolve any conflicts, note that conflicts
 are possible even if you have no local edits. Then compile and test and
 once you are happy that nothing is broken, commit the changes.

  -- Joe
 73
 Bill
 G4WJS.

 --
 Comprehensive Server Monitoring with Site24x7.
 Monitor 10 servers for $9/Month.
 Get alerted through email, SMS, voice calls or mobile push notifications.
 Take corrective actions from your mobile device.
 http://p.sf.net/sfu/Zoho
 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Problem with WSJT-X

[Joe Taylor]

Hi Russell

We can't test every possible rig in advance, so we depend on reports 
like yours.  Most of the rig-control issues are being handled by Bill, 
G4WJS, and usually he can fix such problems fairly quickly.  I am 
copying this brief reply to the wsjt-devel list.  You will probably hear 
from Bill soon, with a request for more info.

 -- 73, Joe, K1JT

On 10/21/2014 3:35 PM, Rusty wrote:
 Greetings Joe,

 I have been an avid user of JT-65 and JT-9 for quite a while. Was using
 a TS-2000 for that purpose and have since upgraded to an Icom IC-9100.
 Therein lies the problem I am writing to you concerning.

 Using version 1.4.0-rc2 r4400, I cannot seem to get the radio to respond
 to transmit. I have checked, double checked, and triple checked my
 settings to make sure everything matched and nothing. Had a friend of
 mine who works in the IT industry as a troubleshooter remote to my
 computer and he could not get it to work. 2 other friends of mine came
 over that are electrical engineers and it left both of them scratching
 their heads.

 The only thing we have been able to figure out is that there is a bug in
 your program. Has anyone else contacted you about this problem and if so
 was there a fix for it. I really want to use the 9100 for digital work.

 Thank you for taking time out of your busy day to assist with this
 matter. If you need more information do not hesitate to contact me.

 --
 Russell Plocheck, KF5REP


--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] KVASD 1.12 status

[Joe Taylor]

Hi Greg and all,

KI7MT:
 I know you've been busy with WSJT-X updates, but was wondering if you
 came to any conclusions on KVASD v1.12 decoder (32/64) and if there will
 be a central location to pull the decoder from for the apps that use it?

I presently have versions of kvasd v1.12 compiled for Windows, linux32, 
and linux64.  Also kvasd v1.11 compiled for ARM, OSX_32, OSX_64, and 
linux64.  I could make others, if there's a good reason to do so.

The only difference between v1.11 and v1.12 is that 1.12 also does a 
decode test (on internally stored data) when you ask for its version number.

Where is the best place to put them, for easy access?  Maybe not on 
SourceForge, since they're not open source?  Perhaps on the WSJT web 
site, instead?

Is static linking of these a bad idea, for any licensing reasons?  (I'm 
fairly clueless about these things...)

-- Joe, K1JT

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] KVASD 1.12 status

[Joe Taylor]

Thanks for all the comments.

I agree that for consistency we should provide kvasd v1.12 for all 
platforms.  We should use static linking of code that implements the 
patented (and licensed) Koetter-Vardy algorithm, but dynamic linking of 
all compiler and system libraries.

Version 1.12 is a drop-in replacement for v1.11, on all platforms.  The 
comments in extract.F90 are obsolete (and should be removed).  I have 
not yet built kvasd 1.12 for OSX and ARM, so that still needs to be done.

Temporarily, so that people here can test them on suitable systems, I've 
posted the following versions of kvasd at
http://physics.princeton.edu/pulsar/K1JT/kvasd/

  kvasd_1.11_arm*
  kvasd_1.11_osx32*
  kvasd_1.11_osx64*
  kvasd_1.12.exe*
  kvasd_1.12_linux32*
  kvasd_1.12_linux64*

To use one of these with WSJT, WSJT-X, or MAP65 you will need to rename 
it -- probably to kvasd (Linux, OS X) or to kvasd.exe (Windows).

-- Joe

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] KVASD 1.12 status

[Joe Taylor]

Bill --

 Version 1.12 is a drop-in replacement for v1.11, on all platforms.  The
 comments in extract.F90 are obsolete (and should be removed).  I have
 not yet built kvasd 1.12 for OSX and ARM, so that still needs to be done.
 I'm not sure that is correct. There is commented out code in extract.F90
 that was waiting for 1.12. The reason being that WSJT-X has to run with
 a cwd in a temporary directory and arrange to copy kvasd.dat into that
 directory. IIRC the changes to kvasd 1.12 were to allow a full path to
 kvasd.dat to be passed to kvasd and therefore allow it to be run from
 any cwd.

 This all dates back to changes made to get rid of code writing files in
 the install directories.

 The reason I put the code in to use the temporary directory cwd was
 because at the time there was no Mac version of kavsd 1.12 produced.

 While the workaround in WSJT-X does work, it adds complexity and has
 since had other impacts causing even more complexity.

You're correct.  Version 1.12 will work as a drop-in replacement for 
v1.11, but it also has the enhancement that enables it to communicate 
with WSJT-X through a file defined by any pathname, rather than just 
kvasd.dat in the current working directory.

 Currently the WSJT-X build still has the capability of fetching kvasd
 and still does so for everything but Linux non-Debug configurations.
 This is to make testing WSJT-X relatively seamless and also goes as far
 as bundling kvasd into installers on Windows and Mac non-Debug configure
 builds and packaging.

 Should I remove this capability?

It seems to me that this capability should be retained.  So, after they 
have been tested by someone else beside me, I suppose the v1.12 
executables for all platforms should replace those now in the SVN 
repository under .../trunk/kvasd-binary ?

-- Joe

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] KVASD 1.12 status

[Joe Taylor]

Hi John,

Welcome home!

 Joe:  I'll have computers up and running tomorrow so you can have
 a Mac OSX platform to build KVASD 1.12 as before.   I'll send
 connection details tomorrow.

No hurry... I need to be in Chicago tomorrow, will be home again late 
Saturday.  Next week is good enough.

-- Joe

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wspr-x error

[Joe Taylor]

I suggest installing to a directory name that does not contain an 
embedded space: For example, C:\HamRadio or C:\Radio rather than
C:\Ham Radio.

-- 73, Joe, K1JT

On 10/26/2014 11:27 AM, Doug Wetzel wrote:
 Hello developers,

 Sorry for the non-wsjt bandwidth, but I'm wondering if there's an easy fix
 to this error toss:

 [image: Inline image 1]

 wspr-x is installed in C:\Ham Radio\wsprx.

 Thanks!

 Doug
 K7IP




 --



 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Comment on beta release of Version 1.4 rc2 of WSJT-X

[Joe Taylor]

Hi Mike,

 This is Mike - N5INP. Been the beta release of Version 1.4 rc2 of WSJT-X
 for a while. Wanted to report one thing. When I first start the program for
 the day, and try to transmit (or tune) with it, it first does a whole lot
 of disk access for abut 30 seconds. Until this access is done, it will not
 transmit. I have no idea what it's doing. I've gotten used to just clicking
 the Tune button first, letting it do it's disk access and getting that
 out of the way. After that it works OK. Do you know what it's doing during
 this disk access or if that's normal?

 Thanks,

 Mike - N5INP

WSJT-X does not do anything like that here.  Most of the recent program 
changes have to do with rig control, and hamlib control of a few rigs 
is still not very stable.

I'll copy this message to the WSJT-X Developers list, where Bill (G4WJS) 
will be interested in your report.  He may contact you directly.

-- 73, Joe, K1JT

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X: Decode improvements

[Joe Taylor]

Hi Bill,

Thanks for sharing your experience with the decoder improvements.  I was 
waiting for some confirmation from others that the changes are good... 
Perhaps now these should be merged into the wsjtx-1.4 branch, so they 
can be part of rc3.

-- Joe

On 11/5/2014 8:47 PM, Bill Somerville wrote:
 Hi All,

 Having been focused mainly on v1.4 issues I haven't had much time on air
 recently with the latest code, nice to see ongoing improvements in
 WSJT-X decoding. Joe's latest changes causing JT9 signals that would not
 decode in Fastest or Normal mode now decoding nicely in all modes. I
 am seeing -20dB signals decoding in a flash in Fastest that would only
 decode in Deepest mode after a few seconds before.

 73
 Bill
 G4WJS.

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X Superbuild Script.

[Joe Taylor]

Hi Bill and all,

Back to more-or-less normal here, after a busy weekend in the ARRL EME 
Contest -- a total of 215 QSOs by our multi-op crew.  :-)

I just wanted you to know that I have now done both a Type 1 and a 
Type 2 build using your Superbuild script.  Both worked without 
problems.

The man pages for wsjtx, jt65code, and rigctld-wajtx also look very 
nice.  Many thanks for setting these up!

-- Joe, K1JT

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Lower frequency limit

[Joe Taylor]

Hi Nick and all,

Apologies for this slow response to your query.  The simple answer is 
that the decoder does its work in order of increasing frequency, 
starting at the left edge of your waterfall display.  If your receiver 
is reasonably flat down to this edge, decodes will be possible down to 
that limit as well.

-- 73, Joe, K1JT

On 11/1/2014 1:46 PM, nick wrote:
 What is the lowest baseband frequency that wsjt-x will decode down to?

 I have seen instances on the wide graph where signals fail to decode at
   250Hz.

 73

 Nick G3VNC

 --
 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Option --rig-name

[Joe Taylor]

Hi Bill,

I notice that when I invoke wsjtx under Linux using the command

  $ wsjtx -r TS2000

the auxiliary files and directories are created with names containing 
embedded blanks.  For example:

  $ pwd
  /home/joe/.config
  $ ls *ini
  -rw-rw-r-- 1 joe joe 2918 Nov 12 15:46 WSJT-X - TS2000.ini

I would much prefer the file names to be WSJT-X-TS2000.ini, etc.

-- Joe, K1JT

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Migrating WSPR to using Hamlib 3 run problem...

[Joe Taylor]

Hi John,

N6RCD wrote:
 I'm not using a shortcut to start WSPR. I double-click on wspr.bat in the
 build directory :

 c:\JTSDK-PY\wspr\wspr-r4522\wspr.bat

OK.  You're using WSPR in a way that was not intended, or planned for, 
but it should be possible to make it work.

I copied the rigctl.exe (built with hamlib3) from

C:\JTSDK-QT\hamlib3\mingw32\bin\rigctl.exe

to

C:\JTSDK-PY\wspr\wspr-r4522\rigctl.exe

and then copied libwinpthread.dll from

C:\JTSDK-QT\appsupport\runtime\libwinpthread.dll

to

C:\\JTSDK-PY\wspr\wspr-r4522\libwinpthread.dll

WSPR now runs OK including rig control via the hamlib3 version if 
rigctl.exe.  This is true both from the command prompt and by clicking 
on C:\JTSDK-PY\wspr\wspr-r4522\wspr.bat in Windows explorer.

-- 73, Joe, K1JT

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X and KVASD and License Conformance

[Joe Taylor]

Hi Greg,

N1DAM wrote:
...
 Longer term, it would be good to have a roadmap for removing the
 need/desire to use non-Free code, as it seems to be causing signficant
 practical problems (with the resulting lack of portability arguably
 being the largest issue).  I've seen some comments on the list, but am
 unclear on the status/prognosis.

 How bad is it for someone to choose not to use KVASD?  Does it cost them
 decode performance, or CPU time, or both?  Or is it really not a
 feasible choice?  The documentation I've found doesn't address this; it
 just says go get this non-free code, with an implicit assuming it's
 available for the os/version/cpu that you want to run it on.

WSJT-X works well without kvasd.  The program has a built-in 
hard-decision Reed Solomon decoder.  The patented soft-decision decoder 
implemented in kvasd with proprietary code is about 2 dB more sensitive.

At HF one might consider a 2 dB penalty rather moderate.  But for EME, 
the purpose for which JT65 was originally designed and now widely used, 
those 2 dB are very important.

-- 73, Joe, K1JT

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSPR-X Building on all platforms.

[Joe Taylor]

Hi Bill,

No development effort is currently being devoted to WSPR-X. When that 
happens (and if it does), an better solution might be to do what we did 
with WSJT-X -- abandon use of PortAudio entirely, and use the audio 
subsystem in Qt.

-- Joe

On 11/15/2014 8:16 AM, Bill Somerville wrote:
 Hi All,

 I had a question about building WSPR-X on Mac off list. I looked at the
 CMake script and it uses a Windows only construct in that it references
 a DLL in the source tree for portaudio.

 What is needed is a CMake Findportaudio.cmake finder, I have checked
 around and several projects have written such a finder module but TBH I
 think I can do better by using the standard CMake helpers for writing
 finders.

 Any objections to me adding such a finder to the WSPR-X project?

 The consequences would be that the build will work on all supported
 platforms. There is a small downside in that the WIndows build would
 require the developer to install portaudio themselves (the JTSDK-QT may
 already do this) rather than relying on the DLL being part of the source
 tree.

 73
 Bill
 G4WJS.

 --
 Comprehensive Server Monitoring with Site24x7.
 Monitor 10 servers for $9/Month.
 Get alerted through email, SMS, voice calls or mobile push notifications.
 Take corrective actions from your mobile device.
 http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk
 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://pubads.g.doubleclick.net/gampad/clk?id=154624111iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Copyright, Licensing, and Attribution of Credit

[Joe Taylor]

Dear Colleagues,

I've given some thought recently to issues of Copyright, Licensing, and 
attribution of credits related to our software. I want to share my 
thinking with you and ask for possible input from others.

As I see it, we should work toward satisfying the following goals:

1. A basic notice of copyright, licensing, and warranty disclaimer 
should be included in every distribution package and installed along 
with the program.  Its content should be something like the following 
text that Greg recently put into the file .../branches/wspr/COPYRIGHT in 
our SVN repository:

#
Copyright (C) 2001-2014 by Joseph H Taylor, Jr, K1JT

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see http://www.gnu.org/licenses/.
#

2. A copy of GPLv3 should be installed along with our programs. See file 
.../branches/wspr/COPYRIGHT.

3. To comply with GPLv3 we must provide all source code necessary to 
build the program, or instructions on how to obtain it.  (I believe we 
are already doing this.)

4. We should include suitable acknowledgments to individuals and 
essential prior work that has made our program possible.  Suitable 
places may be the Acknowledgments section of our User Guides, 'About' 
windows in our programs, a 'README' file installed along with each 
program, etc.  (I believe we are already doing this, too; but we should 
be on the lookout for possible omissions or inconsistencies.)

5. In the case of KVASD, which implements the patent-licensed algorithm 
for the Koetter-Vardy Algebraic Soft-Decision Reed-Solomon Decoder, we 
must ensure that users who install it have seen and accepted the terms 
of its End User License Agreement.

-

I should mention that among my motivations for again looking into these 
matters was my recent examination of downloadable packages for the 
program JT65-HF HB9HQX-EDition, available on SourceForge.  There are 
two packages: a Windows binary installer and a Source code package. 
This program is licensed under GPLv2.  A 'readme' file says The program 
is mainly based on W6CQz, Joe Large's JT65-HF.  It does not mention WSJT.

The HB9HQX 'readme' file includes some highlights of program features, 
including Rapid decode result with singledecoder and multidecode. That 
line caught my eye, so I started looking into whether he (or perhaps 
someone else) had developed independent code for the JT65 protocol (as 
specified in my September-October 2005 article in QEX,
http://physics.princeton.edu/pulsar/K1JT/JT65.pdf).  No: it turns out 
that like W6CQZ in the original JT65-HF, and I guess anyone else who has 
created a program that decodes JT65, he has simply taken code from our 
WSJT repository, applied the multi-decoding ideas from MAP65, compiled 
it into a windows dll, and used it pretty much as is, including 
invocation of the closed-source KVASD decoder.

I have no problem with the use of our open-source code in another 
program.  After all, that's a major reason for why it is open source! 
Surely this can be done in the good ham spirit of sharing information 
and techniques among enthusiastic hobbyists.  However, some necessary 
issues related to copyright, licensing, and attribution must receive 
suitable attention.  We have been somewhat lax about these things in the 
past -- and so have some others making use of our code.

I have had some brief communication with Beat, HB9HQX.  I believe he 
is in agreement with most or all of the above, and will do what's 
necessary to bring his version of JT65-HF into compliance with both our 
license and his.  I am sending him a copy of this message.

Your comments and suggestions will be most welcome.

-- 73, Joe, K1JT

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net

[wsjt-devel] Decoder optimizations

[Joe Taylor]

Hi all,

I have committed some changes that significantly improve the decoding 
speed of WSJT-X in both modes, with no change in its effectiveness.
The changes affect only the jt9.exe executable.

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 directory
.../branches/wsjt/lib.  When run, it creates a file fftwf_wisdom.dat 
that should go in the .../bin installation directory.

Bill, could you suggest the best way to incorporate the necessary 
features in the CMake script?  On Windows it will need to install
fftwf-wisdom.exe and wisdom1.bat along with other executables in the 
.../bin directory, and the installer should offer to run widwom1.bat, 
warning the user that it will take several minutes to complete.

The final wisdom1[.bat] file will be slightly different from the example 
now in the repository, since it won't need the hard-coded path I used 
for fftwf-wisdom[.exe].

Comments and test results are welcome.  On my development machine the 
speedup is about 35% when a velid fftwf_wisdom.dat (necessarily computed 
on the same machine) is present.

-- Joe, K1JT

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Decoder optimizations

[Joe Taylor]

Hi Bill,

Yes, there are many possible ways to take advantage of FFTW's wisdom 
capability.  I've been using it for some years now -- both for 
professional research purposes and in MAP65, which processes a 96 KHz 
signal bandwidth in each of two polarizations and thus has much higher 
CPU demands.

It's well worth the effort required to implement wisdom, especially with 
large FFTs whose lengths are not powers of two.

There's no speed advantage to accumulating wisdom within the executing 
program(s) rather than beforehand.  Having it done once at program 
installation has worked well in MAP65.  It's true, though, that for 
MAP65 I was not particularly worrying about installers on OS X.

I've implemented wisdom the other way, as well -- which in this case 
means importing/exporting it from within wsjtx[.exe] and jt9[.exe]. 
Given your comments about complicating the installers, I'll try doing it 
that way before going on to other things.

-- Joe

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Wsjtx v1.4

[Joe Taylor]

Hi Chris,

There is no problem running wsjtx.exe on 64-bit Windows 8.1.  However, 
we can't test every possible rig and control software combination in 
advance, so we depend on reports like yours.  Most of the CAT-control 
issues are being handled by Bill, G4WJS, and usually he can fix such 
problems very quickly, once identified.  I am copying this brief reply 
to the wsjt-devel list.  You will probably hear from Bill soon, with a 
request for more info.

 -- 73, Joe, K1JT

On 11/20/2014 12:05 PM, LA9BM - Leif wrote:
 Hi
 Thank you for a great software.
 I downloaded v1.3 and 1.4 and do know the 1.4 is a beta version.

 The name of the exe file has the 32 in the name. Can I ask if this is a 32 
 bits software? I am running the windows 8.1 64 bits. It is working Ok but I 
 am not ablle to definate my Rig IC 7700 or my other rig IC 7100. I have to 
 set the HRD as my rig. I know another ham had to do the same with 2 other 
 rigs. Is ther any easy tricks you reccomend? I am not able to make a 
 connection to my rigs. Not with the version 1.3 nor 1.4 without using the HRD 
 settup.

 I have problems changing the sample rates on my soundcard from 44100 to 48000 
 as long as I am using the HRD. 'Will probably cause the other proram not 
 working' is the warning.

 Thank you for answering if you have time
 73s from

 LA9BM -Leif B in Norway

 Mange hilsen fra
 Leif B

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] [wsjt:wsjt] [r4611] - k1jt: Should have been included in previous commit.

[Joe Taylor]

Hi John,

 But along with this is a Fortran runtime error:
 Actual string length is shorter than the declared one for dummy argument 'c' 
 (0/1)

 Unfortunately - no other information about where this occurred.  I'll have a 
 look...

I have seen a similar error message in Windows, as well, although not in 
the wsjtx.exe built from r4611.  Since the problem went away on the 
system I was testing, I stopped trying to fix it at the source. 
However, I think it occurs in subroutine write_char(), at the top of 
file f77_wisdom.f90.

subroutine write_char(c, iunit)
   character c
   integer iunit
   write(iunit,1000) c
1000 format(a,$)
end subroutine write_char

I suggest changing the write statement so that it reads as follows:

   if(len(c).eq.1) write(iunit,1000) c

-- Joe

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

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

[Joe Taylor]

Hi John,

You might want to try the work-around I created in r4614.  Presumably 
the same thing could be done with the import, as well.

-- Joe

On 11/20/2014 5:52 PM, John Nelson wrote:
 Hi,

 I get a Fortran runtime error on line 1 of f77_wisdom.f90:

 subroutine write_char(c, iunit)
   character c
   integer iunit
   ! if (len(c).eq.1) write(iunit,1000) c
 1000 format(a,$)
 end subroutine write_char

 with an error:  Actual string length is shorter than the declared one for 
 dummy argument 'c'

 This routine is called internally by sfftw_export_wisdom.The pointer to 
 'c' is not valid when presented to the write_char routine.

 Question:   fftw is compiled in single-precision so arguments are 32-bit.   
 f77_wisdom is compiled in 64-bit and argument passing between 32-bit routines 
 and 64-bit routines is not straight-forward.   Is this a reason why this 
 problem is occuring?

 It is present with 3 different OSX and with three different Fortran 
 compilers

 I cannot find a solution...all suggestions are welcome.

 --- John G4KLA
 --
 Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
 from Actuate! Instantly Supercharge Your Business Reports and Dashboards
 with Interactivity, Sharing, Native Excel Exports, App Integration  more
 Get technology previously reserved for billion-dollar corporations, FREE
 http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FFTW3 Wisdom

[Joe Taylor]

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 fairly new.  It did not exist when last I 
messed around with FFTW wisdom.  Probably we can use it now; we made 
wisdom.c because the older wrapper, invoked through f77_wisdom.f90, 
failed on OS X.

 2) I see that you have named the wisdom data file as jt9_wisdom.dat.
 Looking at the FFTW implementation it would seem that a single wisdom
 data file for all applications is not a great overhead. The default
 system wisdom data file (not available on Windows) is named
 /etc/fftw/{wisdomf,wisdom,wisdoml} and is intended to contain many
 optimized plan choices for various type and sizes of transform. I would
 have thought that a single wisdom data file for all WSJT-X programs and
 utilities would be sufficient. Was your intention to have a different
 wisdom data file for wsjt and jt9?

Revision 4617 also reads/writes wsjtx_wisdom.dat.  We're presently 
running two processes in parallel, jt9[.exe] and wsjtx[.exe].  We don't 
want them writing to the same file, possibly over-writing information 
that the other process wanted to save.

It will be trivial to change to one file if/when we change to a 
single-process model.

System wisdom is convenient in *nix but not very convenient in Windows. 
  The whole idea is not particularly useful when we are using oddball 
FFT lengths like some of those used in WSJT-X, e.g., 77175, 672000, and 
884736.

 3) I was also thinking of adding a header line to the exported wisdom
 data file including the program version. Something like:

 version:last-change-svn-revision{-dirty,-local}

Could be done, but my informed guess is that it's not worth the effort. 
  These optimizations lead to speed improvements that are rather minor. 
  The code is already carefully tuned and optimized; the FFTs do not 
dominate execution times.

-- Joe

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Decoding problems

[Joe Taylor]

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 decode.  Signals are visible in the waterfall down to at least -30 dB 
(details depend on scrolling speed, bin averaging, etc.).

The most common reasons for failure of strong enough signals to decode 
are QRM, timing, and frequency drift.  None of these would seem to 
explain what's wrong with your third file. It looks like there is a 
discontinuity about two-thirds of the way in...

-- Joe, K1JT

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] KVASD for Mac

[Joe Taylor]

Richard --

On 11/21/2014 11:59 AM, Richard Shaw wrote:
 On Fri, Nov 21, 2014 at 10:44 AM, Joe Taylorj...@princeton.edu  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.o usleep.o


 Are you only manually building for mac? Or all platforms?

 I'm sure either I or Bill could come up with a quick cmake config and we
 don't need to know anything more than the source file names to include.
 Then you could have one source directory and a build directory per
 target/platform/arch.

No need for CMake here, this is a trivial (and infrequently required) 
build operation.

-- Joe, K1JT

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X Action on F4 clear DX call.

[Joe Taylor]

Bill --

 ...  How about leaving things as is
 except that the newly generated CQ message gets displayed in the Gen
 msg box (this is a clear defect as it stands now) and the Gen msg
 radio button gets selected. The custom free text message can stay
 unchanged. That way we don't have too much difference in behaviour
 between tab 1 and tab 2.

OK, that's a reasonable solution.  Tab 1 stays as is.

-- Joe

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Crazy test

[Joe Taylor]

Hi Alessandro,

I replicated your tests as exactly as possible, modifying 
CMAKE_CXX_FLAGS and General_FFLAGS by the addition of -mtune=native.
Using WSJT-X and the Shift+F6 command, the sequence of ten files 
(01.wav, 02,wav, ... 10.wav) was processed in 21 seconds with or without 
the addition of -mtune=native before building the program from 
scratch.  I could find no measurable difference in execution speed for 
the two cases.  Certainly they were the same to within 1 second.

I note also that the total execution time is very nearly the same as 
what I reported yesterday for the execution of jt9[.exe] from the 
command line.  Almost all of the CPU-intensive number crunching in 
WSJT-X occurs in the Fortran code in jt9.  Other tasks such as display 
of graphical information and decoded text, writing output files, etc.,
make comparatively trivial demands on CPU resources.

It remains a mystery to me why you have seen large differences in 
execution speed after adding the compiler flag -mtune=native.

-- 73, Joe, K1JT

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Crazy test

[Joe Taylor]

Mike --

 I didn't quite realize that jt9 didn't use the dll.

What dll are you referring to?  If you mean the FFTW library, jt9[.exe] 
definitely *does* use it.

 What's the command line to run jt9?

Type jt9 by itself at the command prompt, to get a brief usage
message.  For example:

C:\JTSDK-QT\wsjtx\install\Release\binjt9
  Usage: jt9 -p TRperiod [-d ndepth] [-f rxfreq] {-w patience] -e 
exe_dir file1 [
file2 ...]
 Reads data from *.wav files.

 jt9 -s key [-w patience] -e exe_dir -a data_dir -t temp_dir
 Gets data from shared memory region with key==key

 Not sure what args to give since neither of you mentioned what you're
 passing to it.

My tests used the command

  jt9 -p 1 -d 3 /tmp5/0?.wav

Directory /tmp5 contained the files 00.wav, 01.wav, ... 09.wav -- ten 
files in all, each a copy of the example file 130610_2343.wav.

-- Joe, K1JT

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSPR crashes, error starting rx thread

[Joe Taylor]

Hi Alan,

On 12/17/2014 6:19 PM, Alan VK2ZIW wrote:
 WSPR is not much use if it only runs 10 or 11 hours.

Many people run production releases of WSPR for many weeks, or even 
longer, without problems.

It appears that you're running an executable you compiled yourself, 
using various tools and packages that I haven't used, on hardware that I 
don't have.  (I think you're running Fedora on an ARM processor, a 
Banana Pi?)

Troubleshooting your build is necessarily a task you must assume mostly 
on your own -- or possibly together with others who have a similar 
interest and similar hardware.

Do let us know what you find out!

-- 73, Joe, K1JT

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSPR crashes, error starting rx thread

[Joe Taylor]

Alan --

For several years already the SVN repository has included two 
lightweight WSPR tools:

   wspr0.exe
   wspr_nogui.py

If running on minimal hardware is a high-priority goal for you (or for 
your balloonists, or ???) have you considered either of these?

These programs have not received much attention of late, but should be 
relatively easy to make functional and useful to play with.  The first 
one, in particular, is *extremely* lightweight.

-- Joe, K1JT

On 12/18/2014 1:54 PM, Alan VK2ZIW wrote:
 Yes Joe,

 We'll let you know what we find.

 And yes, I'm using ARMv7 hardware, because size of equipment
 and power are VERY important.

 How many hams in India could afford to run a 100W PC 24x7
 for WSPR?

 That's $300 per year here in Australia.

 Can you fly a Windows x86 PC in a balloon?

 We MUST consider, as developers, the use or our products.

 BTW: I quite clearly specified the hardware and O/S with problems.

 73

 Alan VK2ZIW

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSPR crashes, error starting rx thread

[Joe Taylor]

Hi Alan,

VK2ZIW wrote:
 ...
 In the end, we all need a Low Power, Low Price way to run WSPR or WSJT.
 That is repeatable and reliable.

Several questions seem relevant to me:

Who are we all (the many potential users) you are thinking of?

What do they want to do, or would you like them to be able to do?

Are you aware of the many lightweight WSPR/WSJT solutions that have 
already been achieved, and are in regular use?  Is there a reason you 
want to proceed in a different way from any of these?

-- Joe, K1JT

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X Decoder Performance

[Joe Taylor]

Dear Colleagues,

I have made some further performance tests of the decoders in WSJT-X.

I copied a collection of 25 *.wav files into a clean directory.  The 
files wererecorded in *JT9+JT65* mode during a busy period of activity 
on 20 meters.  On average, around a dozen decodable signals are present 
in each file -- typically 7 or 8 JT65 signals and 4 or 5 JT9 signals.

My procedure was as follows:

1. Start the program.

2. Activate File | Erase ALL.TXT.

3. Activate File | Open and select first file in the test directory,
clicking the Open button exactly at the top of a UTC minute.

4. Allow decoding of the first file to finish, then hit Shift+F6 as
soon as the blue background has cleared from the *Decode* button.

5. The program then proceeds to decode the remaining 24 files.

6. Manually record the UTC when the last decode has finished, thereby
producing the total wall clock time to decode the 25 files.

7. Record the number of decoded lines in the file ALL.TXT.  (Don't
count the date line, at the top.)

8. Record the larger of the two bottom-line numbers from the file
timer.out.  This is the time that would be spent in the decoders at
the end of an Rx minute -- in this case, it is essentially the
wall-clock time minus the time spent reading files, producing the
waterfall, etc.

Here's a summary of my results:

Program Version  Wall Clock   Time   Decode#
---
v1.3 r3673   90 s62.14 s Deepest  290
v1.4.0-rc2, r440076  53.98   Deepest  302
v1.5, r4926  46  24.27   Deepest  309
v1.5, r4926  42  21.47   Normal   307
v1.5, r4926  40  20.14   Fast 305

Bottom line: The decoder in v1.5 r4926 is 2.2 to 3 times faster than the 
ones in v1.3 r3673 and v1.4.0-rc2, and it also decodes more signals.

Note that in revision v1.5 r4926 we are not yet taking advantage of 
concurrent processing in the decoder, on computers with more than one 
CPU.  Further gains can probably be achieved, if we put the effort into it.

-- 73, Joe, K1JT

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X: Using the latest decoder improvements in WSJT-X

[Joe Taylor]

On 2/4/2015 2:26 PM, Michael Black wrote:
 Not sure we want more than 1 thread

As I demonstrated and wrote here several hours ago:

When using OpenMP to run JT9 and JT65 decoders in parallel, we gain
almost nothing by using multi-threading for the FFTW plans.

I think this will remain true.  I recommend using -w 2 -m 1 to set up 
the FFTW plans, and using two threads (and only two) for the parallel 
sections initiated in decoder.f90 on multi-core machines.

-- Joe

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r4932

[Joe Taylor]

Hi Mike,

The change was to replace slope, a currently undefined, vestigial 
remnant of some old code, to nflatten -- the correct argument to pass 
to symspec.   The variable slope was undefined in jt9.f90.  Inside 
symspec, its value supposedly controlled whether the spectrum being 
computed for the waterfall would be flattened, or not.  Since the 
variable was undefined, it might sometimes be zero, sometimes nonzero. 
Not a good situation if we're trying to make comparative timing tests.

Perhaps you will like it better to set nflatten=0 in jt9.f90.  That will 
make jt9 or jt9_omp run faster from the command line, especially since 
flat3 is kinda slow.  But if you normally check the Flatten box in 
the GUI, your decoding results may not be exactly the same.

In normal operation the timing difference is moot, because the extra 
work takes place during the Rx minute rather than at its end.  It's for 
the CPU-bound stuff at the end of the Rx minute that I have been 
speeding things up.

Perhaps I should look at flat3, to see why it's so slow -- even though 
its slow behavior has essentially no effect noticeable to an operator.

-- Joe

On 2/4/2015 3:45 PM, Michael Black wrote:
 The change on jt9.for replacing nflatten with slope really made processing
 times much worse.

 Mainwindow.cpp is using nflatten.so I don't quite understand the log comment
 about making them consistent.



 On my testing jt9_omp went from 1.12 to 1.81 seconds.



 Mike W9MDB





 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/



 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] r4932

[Joe Taylor]

Hi all,

On 2/4/2015 4:49 PM, Michael Black wrote:
 So does this also mean if you don't check the Flatten box that your decodes
 would be slower since it does the flatten later if the GUi doesn't do it?

No.  And I realized after hitting Send that I was wrong to say the 
decodes would be different with nflatten=0.  Flatten affects only the 
difplayed spectrum and waterfall.  The decoders take care of their own 
flattening as required.

 What does this if check look for in jt9.f90
 if(nhsym.ge.1 .and. nhsym.ne.nhsym0) then

I have no idea what you're asking about here.

That if() statement just checks (in jt9 commend-line mode) to see 
whether enough data have been read from disk that it's time to call symspec.

-- Joe

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] WSJT-X Decoder Performance

[Joe Taylor]

Hi all,

I have made further improvements to the speed of the decoders in WSJT-X, 
independently of any recourse to concurrent processing in machines with 
multiple CPUs.  The changes involve

1. Making better choices for NFFT1 and NFFT2 (the lengths of forward and 
inverse FFTs in the JT9 downsampler.

2. Adjusting values of limit (the Fano timeout parameter) and ccflim 
(JT9 synchronizing threshold) under specified conditions.

3. Using -O3 for the gfortran optimizer level.

The following table presents measurements of decoding speed for a number 
of tests using WSJT-X versions 1.3, 1.4.0-rc2, 1.5r4925, and 1.5r4926. 
Time gives the time is seconds to decode the sample file 
130610_2343.wav, which has 8 decodable JT9 signals and 9 decodable JT65 
signals.  Decode is the setting on the WSJT-X *Decode* menu.  The 
column labeled # gives the number of decoded signals.  (Note that 
selecting Deepest is required in order to decode one of the JT9 
signals.)

These measurements were made on a Windows 7 machine with 4-core i5-2500 CPU.

Program VersionTimeDecode   #
---
v1.3 r3673 2.48 s  Deepest  17
v1.4.0-rc2, r4400  2.28Deepest  17
v1.5, r49251.01Deepest  17
v1.5, r49260.83Deepest  17
v1.5, r4926 -w 2 -m 2  0.80Deepest  17
v1.5, r49260.75Normal   16
v1.5, r49260.69Fast 16

The bottom line: At this stage, much has been gained by some careful 
algorithmic tuning.  The decoder in r4926 is 3 times faster than the one 
in r3673, and 2.7 times faster than the one in r4400.  In r4926 a small 
further improvement (about 4%) is obtained by using patience level -w 
2 and two threads (-m 2) for the FFTs.

Similar speed improvements were measured on a linux machine (Core 2 Duo, 
E6750 CPU).

A further speed improvement around 10% should be obtainable by computing 
the JT65 symbol spectra (subroutine symspec65) on the fly, during the Rx 
minute, rather than as part of the end-of-minute *Decode* procedure. 
(This is already done for the JT9 symbol spectra.)  My current view is 
that beyond that step, further speed improvement on single-core machines 
(or single-core processing on multi-core machines, as in all of the 
tabulated tests except one) will be difficult.

Further improvements can probably be made by using more than one core 
concurrently, e.g., by using OpenMP.  As I mentioned before, the biggest 
(or at least easiest) gain may come from running the JT9 and JT65 
decoders concurrently.  It's hard to know whether the gains will be 
worthwhile, without trying.  The programming effort may not be trivial.

-- Joe, K1JT

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X Decoder Performance

[Joe Taylor]

I should have mentioned that if you're especially interested in snappy 
performance of the JT9 decoder, you may consider the penalty for using 
menu setting Decode | Fast to be unimportant.  It will cost you 
nothing at all at the QSO frequency: that first decoding attempt is 
always done at Deepest level.

-- Joe, K1JT

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X Decoder Performance

[Joe Taylor]

Hi Jim,


On 2/2/2015 5:11 PM, Jim Pennino wrote:
 Can one download an executable with these changes?

No, not yet.  Like everything else in the development (aka v1.5) branch, 
these changes are available only on a compile-it-yourself basis.

-- 73, Joe, K1JT

 
 On Mon, 2/2/15, Joe Taylorj...@princeton.edu  wrote:

   Subject: [wsjt-devel] WSJT-X Decoder Performance
   To: wsjt-devel@lists.sourceforge.net
   Date: Monday, February 2, 2015, 11:45 AM

   Hi all,

   I have made further improvements to the speed of the
   decoders in WSJT-X,
   independently of any recourse to concurrent processing in
   machines with
   multiple CPUs.  The changes involve

   1. Making better choices for NFFT1 and NFFT2 (the lengths of
   forward and
   inverse FFTs in the JT9 downsampler.

   2. Adjusting values of limit (the Fano timeout parameter)
   and ccflim
   (JT9 synchronizing threshold) under specified conditions.

   3. Using -O3 for the gfortran optimizer level.

   The following table presents measurements of decoding speed
   for a number
   of tests using WSJT-X versions 1.3, 1.4.0-rc2, 1.5r4925, and
   1.5r4926.
   Time gives the time is seconds to decode the sample file
   130610_2343.wav, which has 8 decodable JT9 signals and 9
   decodable JT65
   signals.  Decode is the setting on the WSJT-X
   *Decode* menu.  The
   column labeled # gives the number of decoded
   signals.  (Note that
   selecting Deepest is required in order to decode one of
   the JT9
   signals.)

   These measurements were made on a Windows 7 machine with
   4-core i5-2500 CPU.

   Program VersionTime
   Decode   #
   ---
   v1.3 r3673
  2.48 s  Deepest  17
   v1.4.0-rc2, r4400  2.28
   Deepest  17
   v1.5, r4925
   1.01Deepest  17
   v1.5, r4926
   0.83Deepest  17
   v1.5, r4926 -w 2 -m 2  0.80Deepest
   17
   v1.5, r4926
   0.75Normal   16
   v1.5, r4926
   0.69Fast 16

   The bottom line: At this stage, much has been gained by some
   careful
   algorithmic tuning.  The decoder in r4926 is 3 times
   faster than the one
   in r3673, and 2.7 times faster than the one in r4400.
   In r4926 a small
   further improvement (about 4%) is obtained by using patience
   level -w
   2 and two threads (-m 2) for the FFTs.

   Similar speed improvements were measured on a linux machine
   (Core 2 Duo,
   E6750 CPU).

   A further speed improvement around 10% should be obtainable
   by computing
   the JT65 symbol spectra (subroutine symspec65) on the fly,
   during the Rx
   minute, rather than as part of the end-of-minute *Decode*
   procedure.
   (This is already done for the JT9 symbol spectra.)  My
   current view is
   that beyond that step, further speed improvement on
   single-core machines
   (or single-core processing on multi-core machines, as in all
   of the
   tabulated tests except one) will be difficult.

   Further improvements can probably be made by using more than
   one core
   concurrently, e.g., by using OpenMP.  As I mentioned
   before, the biggest
   (or at least easiest) gain may come from running the JT9 and
   JT65
   decoders concurrently.  It's hard to know whether the
   gains will be
   worthwhile, without trying.  The programming effort may
   not be trivial.

   -- Joe, K1JT

   
 --
   Dive into the World of Parallel Programming. The Go Parallel
   Website,
   sponsored by Intel and developed in partnership with
   Slashdot Media, is your
   hub for all things parallel software development, from
   weekly thought
   leadership blogs to news, videos, case studies, tutorials
   and more. Take a
   look and join the conversation now. http://goparallel.sourceforge.net/
   ___
   wsjt-devel mailing list
   wsjt-devel@lists.sourceforge.net
   https://lists.sourceforge.net/lists/listinfo/wsjt-devel


 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/
 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. 

Re: [wsjt-devel] WSJT-X Decoder Performance

[Joe Taylor]

Hi Bill and all,

Perhaps you already tried jt9_omp in Linux, but I had not.  I tried it 
today, and it seems to work OK, as is.

Here are some timing tests made on my rather elderly 2-core Linux 
machine.  This time all tests were made with the Deepest setting, 
ndepth=3, and all resulted in 17 good decodes of the sample file 
130610_2343.wav.  To get the times I measured real time to execute jt9 
or jt9_omp from the command-prompt.

Program Version ParamsTime
(s)

jt9 v1.3 r36732.467
jt9 v1.4.0-rc2, r4400 2.658
jt9 v1.5 r4926 -w 1 -m 1  1.243
jt9 v1.5 r4926 -w 2 -m 1  1.202
jt9 v1.5 r4926 -w 2 -m 2  1.140
jt9_omp v1.5 r4926 -w 2 -m 1  0.834
jt9_omp v1.5 r4926 -w 2 -m 2  0.843

When jt9_omp is used it's better *not* to use the multi-threaded FFTW 
plans, at least on this 2-core machine.  The two cores are already being 
used effectively by running the two big FFTs concurrently.


For interest, here are the actual outputs of a pair of timing runs with 
jt9 and jt9_omp.  Note that the decoded lines are the same, but JT65 
lines are intermingled with JT9 lines.  (I like the original ordering 
better -- first the one at the decode frequency; then others in the same 
mode in order of increasing frequancy; then thos in the other mode, 
again in order of increasing frequancy.  With effort, I guess we could 
have it both ways by letting the GUI insert decodes (after the first 
one) in the proper place in the sequence.)

#
$ time jt9 -p 1 -d 3 -w 2 -m 1 130610_2343.wav  junk
2343  -9  0.3 3196 @ WB8QPG IZ0MIT -11
2343 -18  1.0 3372 @ KK4HEG KE0CO CN87
2343  14  0.1 3490 @ CQ AG4M EM75
2343 -20 -1.3 3567 @ CQ TA4A KM37
2343 -15  0.1 3627 @ CT1FBK IK5YZT R+02
2343 -23  0.3 3721 @ KF5SLN KB1SUA FN42
2343 -16  0.2 3774 @ CQ M0ABA JO01
2343  -2  0.2 3843 @ EI3HGB DD2EE JO31
2343 -20  0.3  718 # VE6WQ SQ2NIJ -14
2343  -7  0.3  815 # KK4DSD W7VP -16
2343 -10  0.5  975 # CQ DL7ACA JO40
2343  -9  0.8 1089 # N2SU W0JMW R-14
2343 -11  0.8 1259 # YV6BFE F6GUU R-08
2343  -9  1.7 1471 # VA3UG F1HMR 73
2343  -1  0.6 1718 # BG THX JOE 73
2343 -15  1.3 1951 # RA3Y VE3NLS 73
2343 -20  0.4 2065 # K2OI AJ4UU R-20
DecodeFinished   0   1

real0m1.196s
user0m1.157s
sys 0m0.037s


$ time jt9_omp -p 1 -d 3 -w 2 -m 1 130610_2343.wav  junk
2343 -20  0.3  718 # VE6WQ SQ2NIJ -14
2343  -9  0.3 3196 @ WB8QPG IZ0MIT -11
2343  -7  0.3  815 # KK4DSD W7VP -16
2343 -18  1.0 3372 @ KK4HEG KE0CO CN87
2343 -10  0.5  975 # CQ DL7ACA JO40
2343  -9  0.8 1089 # N2SU W0JMW R-14
2343 -11  0.8 1259 # YV6BFE F6GUU R-08
2343  -9  1.7 1471 # VA3UG F1HMR 73
2343  14  0.1 3490 @ CQ AG4M EM75
2343 -20 -1.3 3567 @ CQ TA4A KM37
2343 -15  0.1 3627 @ CT1FBK IK5YZT R+02
2343 -23  0.3 3721 @ KF5SLN KB1SUA FN42
2343 -16  0.2 3774 @ CQ M0ABA JO01
2343  -1  0.6 1718 # BG THX JOE 73
2343 -15  1.3 1951 # RA3Y VE3NLS 73
2343  -2  0.2 3843 @ EI3HGB DD2EE JO31
2343 -20  0.4 2065 # K2OI AJ4UU R-20
DecodeFinished   0   1

real0m0.806s
user0m1.260s
sys 0m0.055s

#

In its present state the jt9_omp code does not run in Windows.  I 
haven't yet determined why.

-- Joe, K1JT

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X Decoder Performance

[Joe Taylor]

Hi Claude,

Thanks for your timing report.

Your first test may have used the correct executables, too.  To get a 
good test you must run a configuration at least twice.  In the first 
run, the program accumulates wisdom about the best way to configure 
the FFT calculations.  This wisdom is saved and used for subsequent 
runs.  If you change the -w # or -m # parameters, new wisdom will 
need to be accumulated.

-- 73, Joe, K1JT

On 2/4/2015 5:44 AM, Claude Frantz wrote:
 On 02/04/2015 08:42 AM, Claude Frantz wrote:

 Please see here the result I have got with SVNVERSION 4928.

 I'm very sorry, I have used the wrong executables. Here the right output
 now:

 $ time ./jt9 -p 1 -d 3 -w 2 -m 1
 /home/claude/.wsjtx/bin/save/samples/130610_2343.wav
 2343  -9  0.3 3196 @ WB8QPG IZ0MIT -11
 2343 -18  1.0 3372 @ KK4HEG KE0CO CN87
 2343  14  0.1 3490 @ CQ AG4M EM75
 2343 -20 -1.3 3567 @ CQ TA4A KM37
 2343 -15  0.1 3627 @ CT1FBK IK5YZT R+02
 2343 -23  0.3 3721 @ KF5SLN KB1SUA FN42
 2343 -16  0.2 3774 @ CQ M0ABA JO01
 2343  -2  0.2 3843 @ EI3HGB DD2EE JO31
 2343 -20  0.3  718 # VE6WQ SQ2NIJ -14
 2343  -7  0.3  815 # KK4DSD W7VP -16
 2343 -10  0.5  975 # CQ DL7ACA JO40
 2343  -9  0.8 1089 # N2SU W0JMW R-14
 2343 -11  0.8 1259 # YV6BFE F6GUU R-08
 2343  -9  1.7 1471 # VA3UG F1HMR 73
 2343  -1  0.6 1718 # BG THX JOE 73
 2343 -15  1.3 1951 # RA3Y VE3NLS 73
 2343 -20  0.4 2065 # K2OI AJ4UU R-20
 DecodeFinished0   1

 real  0m2.407s
 user  0m2.324s
 sys   0m0.073s

 

 $ time ./jt9_omp -p 1 -d 3 -w 2 -m 1
 /home/claude/.wsjtx/bin/save/samples/130610_2343.wav
 2343 -20  0.3  718 # VE6WQ SQ2NIJ -14
 2343  -9  0.3 3196 @ WB8QPG IZ0MIT -11
 2343  -7  0.3  815 # KK4DSD W7VP -16
 2343 -18  1.0 3372 @ KK4HEG KE0CO CN87
 2343 -10  0.5  975 # CQ DL7ACA JO40
 2343  -9  0.8 1089 # N2SU W0JMW R-14
 2343 -11  0.8 1259 # YV6BFE F6GUU R-08
 2343  14  0.1 3490 @ CQ AG4M EM75
 2343 -20 -1.3 3567 @ CQ TA4A KM37
 2343  -9  1.7 1471 # VA3UG F1HMR 73
 2343 -15  0.1 3627 @ CT1FBK IK5YZT R+02
 2343 -23  0.3 3721 @ KF5SLN KB1SUA FN42
 2343 -16  0.2 3774 @ CQ M0ABA JO01
 2343  -2  0.2 3843 @ EI3HGB DD2EE JO31
 2343  -1  0.6 1718 # BG THX JOE 73
 2343 -15  1.3 1951 # RA3Y VE3NLS 73
 2343 -20  0.4 2065 # K2OI AJ4UU R-20
 DecodeFinished0   1

 real  0m1.663s
 user  0m2.502s
 sys   0m0.090s



 --
 Dive into the World of Parallel Programming. The Go Parallel Website,
 sponsored by Intel and developed in partnership with Slashdot Media, is your
 hub for all things parallel software development, from weekly thought
 leadership blogs to news, videos, case studies, tutorials and more. Take a
 look and join the conversation now. http://goparallel.sourceforge.net/
 ___
 wsjt-devel mailing list
 wsjt-devel@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/wsjt-devel

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X Decoder Performance

[Joe Taylor]

Hi Bill and all,

Tests here suggest that r4929 produces a Windows jt9_omp.exe that runs 
correctly.  At least, it runs to completion on my sequence of 25 test 
files -- which r4928 does not.

Timing results on a 4-core Win7 machine:

Params   jt9   jt9_omp
--
-w 2 -m 1   25.5 s  21.1 s
-w 2 -m 2   24.921.0

When using OpenMP to run JT9 and JT65 decoders in parallel, we gain 
almost nothing by using multi-threading for the FFTW plans.

Note that decoder.f90 now decodes the two modes in parallel sections 
*ONLY* if txmode is JT9.  I will fix this.

I may also look for additional places where concurrent processing could 
help performance... but I don't consider this a very high priority.

-- Joe

--
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel