Hi Joe,
Yeah, I've been working S.Pac / IO ( or trying too ) on 20m in the (AM)
my time. Been after VR2, FR5 but every (W6) in CA is calling me, I I
really don't understand it as I can work W6 almost 24x7 on 20m, but when
FR5, VR2, YB8, 3B9 are on and coming in well, I really don't want to
As Joe said, for EME we probably want to run very large numbers of trials. If
one were to start multiple calls to sfrsd2, each with its own random seed, all
at once, and ensure that each call runs in its own thread, would this
accomplish much of what we are after?
Steve
> On Sep 30, 2015, at
Hi Bill,
Thanks for the information on Apple compilers.
Yes, there are several possible ways to slice the JT65 decoding task
that could benefit from parallel processing. Divide-by-frequency is one
possibility.
A disadvantage is that it would provide little or no help in most EME
situations,
Mike --
I was fearful that as soon as I committed code using sfrsd that anyone
could compile, there would be reports that "it did this" or "it didn't
do that" ...
It is *far* too early for any casual on-the-air comparisons to be
useful. The new sfrsd code has simply been "dropped in" after
Hi Steve,
I'm scratching my head...
At SVN revision r5949, WSJT-X v1.6.1 uses sfrsd2 in place of kvasd. It
seems to work well, but so far the only tuning I've done is to try both
the original (kvasd-inspired) metrics and the simple ones based on
p1/psum and p2/psum. In this instance the
If r5949 is indeed using sfrsd (is it just calling it kvasd to make the
code happy?)
Saw the 1st instance of different decodes at 17347running WSJT-X 1.6.0
r5881 along side.
Got two decodes on r5949 at -15 and -20 that 1.6.0 did not see.
Follow at 1738 by a -1 decode on 1.6.0 that r5949 did
Joe -
Just a quick note - I played a bit over lunch and can verify that things tune
right up if the erasure matrix is matched to the metric. So far, no apparent
advantage for the p1/psum form, but I haven’t tried the mr2 probabilities yet.
Will look at it some more tonight.
Steve k9an
> On
Hi,
Please modify the Makefiles in the rsdtest directory, so that they can
be used in the Linux environment too. Thank you.
Best 88 de Claude
--
___
wsjt-devel mailing list
Thanks for your comments, both Laurie and Bill. I am quite satisfied that
one of the power settings available in Win 10 Control Panel is not the
problem. I have scoured (several times) every device I can find that has a
power setting and made sure that nothing gets turned off.
That is not to
Hi Steve,
On 9/30/2015 2:57 PM, Steven Franke wrote:
> As Joe said, for EME we probably want to run very large numbers
> of trials. If one were to start multiple calls to sfrsd2, each
> with its own random seed, all at once, and ensure that each
> call runs in its own thread, would this
Hi Claude,
I have done all of my recent development work on sfrsd2.c on a linux virtual
machine, and the Makefile in rsdtest works for me.
Steve k9an
> On Sep 30, 2015, at 1:43 AM, Claude Frantz
> wrote:
>
> Hi,
>
> Please modify the Makefiles in the rsdtest
On 30/09/2015 09:00, Dave Halbakken wrote:
> Bill, I understand your hesitance add a recovery feature for audio cards,
> but such a feature might be similar to the way some OS's display a
> notification that a network cable has been unplugged. As soon as you plug
> the network cable in again, the
Thanks Joe. Interesting. It could be, I suppose, that with large ntrials the
mr2syms are helping us find more decodes, but they are rejected by the soft
distance check.
In any case, I agree that we should just stick with the current erasures-only
scheme. but let's keep sfrsd3 on the side and
Hi Steve,
Agreed on all counts.
A surprise discovery: it seems that all of our recent tests have been
using the original code in .../trunk/demod64a.f90, with its exp(x)
symbol metrics. I tried switching back to your simple p1/psum, p2/psum
mnetrics computed in .../trunk/rsdtest/demod64b.f90,
> A surprise discovery: it seems that all of our recent tests have been
> using the original code in .../trunk/demod64a.f90, with its exp(x)
> symbol metrics. I tried switching back to your simple p1/psum, p2/psum
> mnetrics computed in .../trunk/rsdtest/demod64b.f90, with much degraded
>
Hi Steve,
On 9/30/2015 8:52 AM, Steven Franke wrote:
>> A surprise discovery: it seems that all of our recent tests have been
>> using the original code in .../trunk/demod64a.f90, with its exp(x)
>> symbol metrics. I tried switching back to your simple p1/psum, p2/psum
>> mnetrics computed in
Joe,
1. This summarizes decoding results using exp(x) (aka “jt”) symbol metrics and
power-percentage (aka “sf”) symbol metrics.
The procedure in each case was to self-tune the algorithm by (i) running with
an arbitrary erasure probability matrix and then (ii) using probability of
Joe,
> On 9/30/2015 2:57 PM, Steven Franke wrote:
>> As Joe said, for EME we probably want to run very large numbers
>> of trials. If one were to start multiple calls to sfrsd2, each
>> with its own random seed, all at once, and ensure that each
>> call runs in its own thread, would this
Hi Steve,
Thanks for sharing your further test results. The iterative self-tuning
procedure seems to work very well, and guess we are agreed that
stochastic substitution of second-best symbols isn't buying us enough to
make the performance hit worthwhile. We should, however, remain
Joe,
RR on all.
I think that I have now arrived at where you were some hours ago - scratching
my head.
I’m running WSJT-X r5950 on OS X. The sfrsd2.c routine is set up for the jt
symbol metrics. If demod64a uses jt metrics, results are very poor - maybe
100/1000 decodes. If I change
On 09/30/2015 01:14 PM, Steven Franke wrote:
Hi Steven,
> Hi Claude, I have done all of my recent development work on sfrsd2.c
> on a linux virtual machine, and the Makefile in rsdtest works for
> me. Steve k9an
At my site, it ends in the following manner:
gcc -I. -DWIN32 -DWin32 -DBIGSYM
Hi all,
For the record: I have built a version of WSJT that calls sfrsd (with
ntrials=1) rather than kvasd. Results in line 20, below, show that
for the test data the new decoder is slightly better than kvasd (line 10).
# Test Decodes False Time
Hi Claude,
I have added the file int.h to the rsdtest directory.
Please note that successfully executing this Makefile is unlikely to
produce anything that you will find useful.
-- Joe, K1JT
On 9/30/2015 10:59 AM, Claude Frantz wrote:
> On 09/30/2015 01:14 PM, Steven Franke wrote:
>
>
I'm not a Mac guy...but this claims a solution...
http://stackoverflow.com/questions/29057437/compile-openmp-programs-with-gcc-compiler-on-os-x-yosemite
On Wed, Sep 30, 2015 at 10:57 AM, Joe Taylor wrote:
> Hi Bill,
>
> A week or so ago you wrote "On the concurrency side
On 30/09/2015 16:57, Joe Taylor wrote:
> Hi Bill,
Hi Joe,
>
> A week or so ago you wrote "On the concurrency side the option to use
> OpenMP is not available as there is no C/C++ OpenMP available on Mac".
>
> Aren't we using OpenMP now in jt9[.exe], on all platforms? Are you
> saying that on the
Hi Bill,
A week or so ago you wrote "On the concurrency side the option to use
OpenMP is not available as there is no C/C++ OpenMP available on Mac".
Aren't we using OpenMP now in jt9[.exe], on all platforms? Are you
saying that on the Mac we can use OpenMP from Fortran, but not from C/C++ ??
Hi Greg,
Amusing tidbit.
I just finished building WSJT-X v1.6.1 r5949 on my in-shack computer.
The attached screen shot shows its first decodes of on-the-air JT65
signals, including KI7MT.
-- Joe
--
27 matches
Mail list logo