On 03/08/2017 14:34, Steve Huston wrote:
On Mon, Jul 24, 2017 at 3:35 PM, Bill Somerville wrote:
I want this change to go into WSJT-X v1.8.0 RC2
but I am aware that it is an awfully large change to drop in at this late
stage, nevertheless I feel it fixes more critical issues than it introduces.
On Mon, Jul 24, 2017 at 3:35 PM, Bill Somerville wrote:
> I want this change to go into WSJT-X v1.8.0 RC2
> but I am aware that it is an awfully large change to drop in at this late
> stage, nevertheless I feel it fixes more critical issues than it introduces.
> Currently it is only in the develop
Hi Joe,
> I trust you understand that these are the full execution times to decode
> however many signals were present. In your example file I think there
> were 16.
Yes.
> Are you happy now with the ordering or displayed Rx and Tx messages in
> your "Rx Frequency" window?
Yes, thank you. I was
Hi Richard,
Summary of resultsr7944 r7956 r7956
(AP off) (AP on)
Fast 0.605 0.137 0.148
Normal1.176 0.676 0.750
Deep 2.785 0.809 1.535
So, it looks as though things have
On 26/07/2017 17:26, Bill Somerville wrote:
AP decoding places more diligence on the operator as such decodes can
be deceptively valid and you should look at the quality and other
decoder information added after the message before making an
assessment on the accuracy of the decode.
I should a
On 7/26/2017 12:01 PM, W9MDB Black Michael via wsjt-devel wrote:
What is "AP" decoding?
Decoding a message with aid of "a priori" information gathered
cumulatively during the progress of a QSO. It has been in WSJT-X for
about a year, in mode QRA64. It's now available in FT8.
-- Jo
On 26/07/2017 17:01, Black Michael via wsjt-devel wrote:
What is "AP" decoding?
Hi Mike,
let me try a dumbed down explanation, not because I want to dumb it down
but because that is probably as deep as my understanding goes.
When decoding a signal we have some fixed criteria for a good deco
Hello Mike,
according to the manual: "the available a priori (AP) information "
= content of ALL.TXT (?) but I am not 100% sure ;-)
73 de Wolfgang
OE1MWW
--
Amateur radio is the most expensive type of free-of-charge communication!
Amateurfunk ist die teuerste Art der kostenlosen Kommunik
Hi Richard,
... (Haven't yet found out how to persuade JTSDK to pick a specific revision
e.g. r7946. Maybe I should RTFM.)
Questions regarding JTSDK-{win32/nix} should go here: jt...@groups.io
73's
Greg, KI7MT
--
C
What is "AP" decoding?
de Mike W9MDB--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel ma
On 25/07/17 22:50, Steven Franke wrote:
> FWIW, you may find that r7946 is somewhat faster than r7944, on all settings.
> I have made a change that will reduce the number of non-viable candidates
> that are sent to the decoders.
Thanks Steve. Thanks also to Joe for the tip on timer.out.
I've d
Hi Richard,
On 7/25/2017 4:58 PM, Richard Lamont G4DYA wrote:
On 25/07/17 00:17, Joe Taylor wrote:
Ubuntu MATE 16.04 amd64
1.7.1-devel r7939
Auto seq and call 1st enabled
Tried it and it looks as though FT8 now has a two-pass decoder, which is
nice.
Since you're providing feedback on develo
July 25, 2017 3:44 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X: review of message reply and sequencing
logic
On 25/07/17 22:09, Steven Franke wrote:
> Hi Richard,
>
>> As Bill mentioned in his OP, the FT8 decoder is still a work in
>> progress bu
Hi Richard,
> 1.8.0-rc1 fast/normal/deep 0.2s/0.5s/0.7s
> 1.8.0-rc2-r7924fast/normal/deep 0.2s/0.5s/0.7s
> 1.7.1-devel-r7944 fast/normal/deep 0.4s/0.8s/2.5s
FWIW, you may find that r7946 is somewhat faster than r7944, on all settings. I
have made a change that will reduce the
On 25/07/17 22:09, Steven Franke wrote:
> Hi Richard,
>
>> As Bill mentioned in his OP, the FT8 decoder is still a work in progress
>> but I have noticed that the r7939/r7944 decoder is currently too slow to
>> be usable on my machine, which uses a Core 2 Duo E6700 CPU (2 x 2.66 GHz
>> cores), eve
On 25/07/2017 21:58, Richard Lamont wrote:
As Bill mentioned in his OP, the FT8 decoder is still a work in progress
but I have noticed that the r7939/r7944 decoder is currently too slow to
be usable on my machine, which uses a Core 2 Duo E6700 CPU (2 x 2.66 GHz
cores), even with nothing much else
Hi Richard,
> As Bill mentioned in his OP, the FT8 decoder is still a work in progress
> but I have noticed that the r7939/r7944 decoder is currently too slow to
> be usable on my machine, which uses a Core 2 Duo E6700 CPU (2 x 2.66 GHz
> cores), even with nothing much else running. (Admittedly th
> On Jul 24, 2017, at 8:24 PM, igwt1939 wrote:
>
> The biggest problems I have is it jumping around and I think it confuses the
> other op so that sometime they don't come back to the finish ,but I still
> enjoy it but will be glad when it gets stable.
Could you explain what you mean by jumpi
Monday, July 24, 2017 5:10 PM
Subject: Re: [wsjt-devel] WSJT-X: review of message reply and sequencing
logic
On 24/07/17 20:35, Bill Somerville wrote:
Currently it is only in the development branch but I
urge those brave enough to build the development branch to try it and
report back. You s
Hi Richard,
Richard G4DYA wrote:
Ubuntu MATE 16.04 amd64
1.7.1-devel r7939
Auto seq and call 1st enabled
Tried it and it looks as though FT8 now has a two-pass decoder, which is
nice.
Since you're providing feedback on development code, you should not need
to guess or make inferences abou
On 24/07/2017 23:10, Richard Lamont wrote:
On 24/07/17 20:35, Bill Somerville wrote:
Currently it is only in the development branch but I
urge those brave enough to build the development branch to try it and
report back. You should note that the development branch also contains
FT8 decoder chang
On 24/07/17 20:35, Bill Somerville wrote:
> Currently it is only in the development branch but I
> urge those brave enough to build the development branch to try it and
> report back. You should note that the development branch also contains
> FT8 decoder changes that are not yet finalized and may
Hi Bill
I just built r7939 and Sh messages in JT4 and QRA64 now seem to be working
correctly with Type 1 compound mycall.
73
Charlie
> Hi All,
>
> I have finally got to a point where I can commit the large round of
> changes that came from doing the above. The change (r7939) comment is
> this:
Thanks Bill. That is what I thought the "policy" was. Just clarifying.
73,
Tom - KQ5S
On Mon, Jul 24, 2017 at 3:55 PM, Bill Somerville
wrote:
> On 24/07/2017 21:50, Tom-KQ5S wrote:
>
> I built and installed 7939. You mentioned " Auto sequencing has been
> made generic such that it can be
On 24/07/2017 21:50, Tom-KQ5S wrote:
I built and installed 7939. You mentioned " Auto sequencing has been
made generic such that it can be used for more than one mode if
desired."
Does this mean JT9/65? If so where do you toggle it on?
Hi Tom,
the "if desired" refers to the developers
Thanks Bill. I built and installed 7939. You mentioned " Auto sequencing
has been made generic such that it can be used for more than one mode if
desired."
Does this mean JT9/65? If so where do you toggle it on?
73,
Tom - KQ5S
On Mon, Jul 24, 2017 at 2:35 PM, Bill Somerville
wrote:
> Hi
Hi All,
I have finally got to a point where I can commit the large round of
changes that came from doing the above. The change (r7939) comment is this:
+
Add the option to ALT+click a decoded CQ or QRZ message which only
moves the Rx frequency to theirs
27 matches
Mail list logo
