Hello Paul,
thanks for the information, that is what I need to know right now.
Just one more thing: the CPU / RAM /OS of the computer used.
73, Rik ON7YD
________________________________________
Van: [email protected] <[email protected]>
namens N1BUG <[email protected]>
Verzonden: zaterdag 17 november 2018 14:26
Aan: [email protected]; [email protected];
[email protected]
Onderwerp: Re: LF: SlowJT9 update
Hi Rik, all,
I can send debug.txt to you directly if you need it.
I ran SlowJT9 in JT9-1 mode overnight on 630m. System is Windows 10
64 bit with a 6 core CPU at 3.2 GHz.
With 0 messages decoded the decode time runs about 0.2 to 0.25
seconds. The most messages decoded in one period was 7, that took
0.429 seconds. There were a few periods with 5 messages decoded,
times run from about 0.3 to 0.45 seconds on those.
The variability in time might depend on exactly what my system
is doing at decode time. In addition to Slow_JT9 I was running most
of the DXLab suite (Launcher, SpotCollector - which is known to
spike CPU usage when processing spots, DXKeeper, Commander,
PropView, DXView), SpotSpy, DX Atlas, two instances of HDSDR, two
instances of WSJT-X 1.91.1, four instances of Spectrum Lab, two
instance of Qlock, WSPR-X, and Firefox with three to four open tabs.
Like I said, it's a busy system. :) Oh, I forgot a few background
tasks. Well, anyway you get the idea.
I am leaning more and more toward preferring the 'original' timing
for the slow submodes, even if that means being able to decode only
one mode at a time.
73,
Paul N1BUG
On 11/16/18 4:55 AM, Rik Strobbe wrote:
> Dear all,
>
>
> I just uploaded a now beta-release of SlowJT9 (v0.9.03).
>
> The main changes are
>
> - The option to save all decoded messages in a text file (file
> "decoded.txt" in the folder "extra")
>
> - The option to save a number of actions the application goes
> through in a text file (file "debug.txt" in the folder "extra").
>
> I hope this last will be useful to trace down bugs. So if you are
> encountering problems, please run SlowJT9 with "Save debug
> information" enabled until the problem occurs and include (the
> relevant part of) debug.txt in your bug report.
>
>
> This weekend and maybe also next week (time permitting) I will
> have a closer look at
>
> - switch to the original symbol length of JT9-2 and JT9-5
>
> - the possibility of simultaneous decoding of JT9(-1), JT9-2 and
> JT9-5.
>
> As simultaneous decoding might be a time critical event, in
> particular in combination with switching to the original JT9-2
> and JT9-5 parameters, the debug file will include all decoding
> events, including the time it takes:
>
>
> 18-11-16 10:25:51 : decoding started 18-11-16 10:25:51 : decoding
> ended (0.596 s - 4 msg decoded)
>
> In order to have an idea how much time decoding takes (on
> different computers, different OS) I would appreciate it if you
> could run SlowJT9 for some hours (overnight) in JT9-1 mode with
> "Save debug information" enabled and provide me with the decoding
> time information (in particular the "decoding ended" lines of
> debug.txt).
>
>
> Whoever is interested can download the SlowJT9 installation file
> at http://472khz.org/SlowJT9/SlowJT9_setup.exe.
>
>
> For now only a Windows version of SlowJT9 is available. But as
> the used IDE has cross platform facilities it should be possible
> to support other operating systems as well in the future.
>
>
> The aim of this beta version is: - To test if the application is
> working properly. - To find out if JT9-2 and/or JT9-5 have a
> sufficient S/N advantage over JT9(-1). - To find out if there is
> sufficient interest in using these modes to continue the
> project. Therefore all comments, bug reports and suggestions are
> most welcome via the Blacksheep RSGB LF Reflector, Yahoo RSGB LF
> Group or directly at [email protected].
>
> 73, Rik ON7YD - OR7T
|
