-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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
.
-- 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
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
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
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
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
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
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
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:
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?
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,
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
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
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
###
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
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
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
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
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
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
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
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
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
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
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
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:
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
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
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
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
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
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
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
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
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
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,
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
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
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
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
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
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
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.
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
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
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
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
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
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 -
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
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,
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
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
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
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
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
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,
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)
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
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
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
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
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
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:
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
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
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
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
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.
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
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
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
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
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
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
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
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
1 - 100 of 1515 matches
Mail list logo
