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
w
Joe -
If you get a chance, it might be interesting to plot decodes vs ntrials for the
sfrsd3.c that I committed just now. Bottom line is that I eventually found a
setting that does a significant number of mr2sym insertions and “does no harm”
at ntrials=1, i.e. the number of decodes is not
Mike --
On 9/29/2015 5:29 PM, Michael Black wrote:
> So the failures are a separate section?
No. Have you looked at what the decoder is doing?
If 25 or fewer of 63 received symbols are in error, the deterministic
Berlekamp_Massey (BM) algorithm is guaranteed to succeed. With more
than 25 err
So the failures are a separate section? So a quad core should get
something approaching 3X barring cache contention.
Question would be how often in real life do failures occur?
And would you make the # of trials dependent on # of cores?
On Tue, Sep 29, 2015 at 3:50 PM, Joe Taylor wrote:
> On 9/
Hi Hans,
Thanks for the report.
I am not aware of any problems that have been reported with spot uploading in
WSJT-X.
I do not know the answer to your question about why WSJT-X might transmit on a
slightly different frequency than WSPR-X, even when the TX settings are the
same. Very early o
On 9/29/2015 4:28 PM, Michael Black wrote:
> What kind of time is it taking now? The overhead of splitting the work can
> kill any advantage as I'm sure you know from the previous multi-threading
> of JT9.
Increasing ntrials from 10^4 to 10^5 increased running time by x 6.4:
about 22 minutes for
What kind of time is it taking now? The overhead of splitting the work can
kill any advantage as I'm sure you know from the previous multi-threading
of JT9.
Mike W9MDB
On Tue, Sep 29, 2015 at 2:16 PM, Joe Taylor wrote:
> Hi all,
>
> Some further information on the new Reed Solomon decoder.
>
>
Hi all,
Some further information on the new Reed Solomon decoder.
A simple timing measurement shows that for test program "rsdtest" 97% of
the execution time is spent in the Berlekamp-Massey
errors-and-erasures decoder.
This is good. It means that if/when we decide more speed is desirable,
it
Hi Steve,
Congratulations -- those are really good results using the 8x8
probability matrix.
With revision 5942 I have made minor adjustments to the criteria used
for rejecting potentially bad decodes. It gives 837/1000 good decodes
and NO bad decodes with ntrials=1.
I have put this best
Joe,
One more comment - I think that I may have mis-interpreted the good/bad columns
in the rsdtest output. I interpreted the first number as total number of
decodes and the second number as the number of bad decodes. So I had been
subtracting the second from the first to get “good” decodes. I
Joe -
I’ve just committed sfrsd3.c. This uses the probability of error derived from
your fort.40 data to set the erasure probabilities. I modified extract2.f90 to
print the 8x8 array out and then imported it directly into sfrsd3.c I manually
edited the probabilities in the regions that had zer
On 29/09/2015 02:18, Dave Halbakken wrote:
Hi Dave,
> Thanks for your reply, Mike.
>
> I found that this problem can be reproduced by unplugging and re-plugging
> the USB cable to my soundcard. To get WSJT-X fully working again you have to
> swap the soundcard settings away and back on both input a
12 matches
Mail list logo
