Re: [wsjt-devel] Spanish translation

[Joe Taylor]

Hi Borja,

On 12/31/2015 4:46 AM, ea2...@gmail.com wrote:
> While getting acquainted with the project sources, there is a
> contribution I can make, translating the manual to Spanish.
> Has it ever been considered?
>
> 73,
> Borja EA2EKH

In general we have been delighted to have translations of manuals for 
WSJT and its sister programs into other languages.  See, for example, 
the list at the bottom of this page
http://www.physics.princeton.edu/pulsar/K1JT/wsjt.html
on the WSJT web site.

In the past, the English versions of the manuals were prepared as MS 
Word files.  One possible complication is that we now use the markup 
language Asciidoc (see https://en.wikipedia.org/wiki/AsciiDoc).  The 
English-language source files, images, etc., are stored in the same SVN 
repository as the source code.

If these starting points present no serious obstacles for you, we here 
on the  email list will happy to help you get started!

-- 73, Joe, K1JT

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Spanish translation

[ea2ekh]

Hello,

While getting acquainted with the project sources, there is a contribution I 
can make, translating the manual to Spanish. Has it ever been considered?

73,


Borja EA2EKH



--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] QT55

[Bill Somerville]

On 31/12/2015 16:14, Michael Black wrote:
> Any thought to letting 1.7.0 be QT 5.5?
> Is there a technical reason not to?
> I've been running it here and all seems well on Windows 10.
> Anybody else using it on another OS?

Hi Mike,

the official WSJT-X v1.6.0 for Windows & OS X is already released built 
with Qt 5.5.

On Linux the version of Qt depends on the distribution. My key testing 
is done on Ubuntu 14.04 LTS which is Qt 5.2.1 and Fedora Core 23 which 
is Qt 5.5.1.

I have elected to use any useful Qt features only available later than 
Qt 5.2 inside #ifdef blocks so that the LTS Ubuntu users are able to build.

So basically we are currently requiring Qt 5.2.1 and support building 
with up Qt 5.5. I haven't tried Qt 5.6 beta yet but I am aware that 
there is a WindowsXP compatibility issue at present that I expect will 
be fixed before Qt 5.6 is released.

73
Bill
G4WJS.

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] QT55

[Bill Somerville]

On 31/12/2015 16:42, Michael Black wrote:
> Is it possible to put something similar to #ifdef in the ui code?

Hi Mike,

not that I'm aware of but the uic generated code is build against 
whatever version of Qt & C++ being used. The only advantage of such a 
construct I could think of would be some widget that is not available in 
an older version of Qt.

What prompts the question Mike?

73
Bill
G4WJS.

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] QT55

[Michael Black]

I'm currently using some sounds for different events (Transmitting,
Watchdog alarm, and Rx Frequency message not addressed to my call).  I've
found them quite useful.  For example when monitoring an offset I can have
other windows in front and WSJT-X tells me when a message comes in on the
offsetif the message has my call no sound is made (that's JTAlerts job).
Wanted to add an audio card checkbox & chooser and was going to use QT55
ability to do so on the audio chooser.

I know this idea was kind of frowned on before but if we can make it
optional it should be harmless, yes?

RRR
Mike W9MDB

On Thu, Dec 31, 2015 at 10:46 AM, Bill Somerville 
wrote:

> On 31/12/2015 16:42, Michael Black wrote:
> > Is it possible to put something similar to #ifdef in the ui code?
>
> Hi Mike,
>
> not that I'm aware of but the uic generated code is build against
> whatever version of Qt & C++ being used. The only advantage of such a
> construct I could think of would be some widget that is not available in
> an older version of Qt.
>
> What prompts the question Mike?
>
> 73
> Bill
> G4WJS.
>
>
> --
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] QT55

[Bill Somerville]

On 31/12/2015 17:17, Bill Somerville wrote:
> On 31/12/2015 16:54, Michael Black wrote:
>> Wanted to add an audio card checkbox & chooser and was going to use
>> QT55 ability to do so on the audio chooser.
> Hi Mike,
>
> it is possible to add widgets to the existing layouts from code so you
> don't necessarily have to have the whole UI designed in Designer.
> Obviously some layouts like QGridLayout might be awkward but it should
> still be possible. I assume  this is destined for the Audio tab of the
> Settings, that has a QGridLayout called gridLayout_5 (better to ask the
> tab itself, see below) that you can add a new QGroupBox to with your
> widgets inside, something like:
>
> #if Q_VERISION > 0x050500
>   auto your_group_box = new QGroupBox ("Audio Announcements");
>   // build group box contents
>   if (auto audio_layout = qobject_cast
> (ui_->audio_tab->layout ())) {
> audio_layout->addWidget (your_group_box, 1, 0);
>  }
> #endif
I did say grid layouts would be awkward and I was right! The above code 
will replace another widget which is not what you want. There is no 
insertWidget() for grid layouts so what I'd do is change the layout of 
the Configuration tabs in Designer to be a vertical layout since there's 
no need for it to be a grid. Then use:

#if Q_VERISION > 0x050500
  auto your_group_box = new QGroupBox ("Audio Announcements");
  // build group box contents
  if (auto audio_layout = qobject_cast
(ui_->audio_tab->layout ())) {
audio_layout->insertWidget (your_group_box, 1);
 }
#endif


73
Bill
G4WJS.

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] QT55

[Michael Black]

Any thought to letting 1.7.0 be QT 5.5?
Is there a technical reason not to?
I've been running it here and all seems well on Windows 10.
Anybody else using it on another OS?

73
Mike W9MDB
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] QT55

[Michael Black]

Is it possible to put something similar to #ifdef in the ui code?
RRR
Mike W9MDB

On Thu, Dec 31, 2015 at 10:32 AM, Bill Somerville 
wrote:

> On 31/12/2015 16:14, Michael Black wrote:
> > Any thought to letting 1.7.0 be QT 5.5?
> > Is there a technical reason not to?
> > I've been running it here and all seems well on Windows 10.
> > Anybody else using it on another OS?
>
> Hi Mike,
>
> the official WSJT-X v1.6.0 for Windows & OS X is already released built
> with Qt 5.5.
>
> On Linux the version of Qt depends on the distribution. My key testing
> is done on Ubuntu 14.04 LTS which is Qt 5.2.1 and Fedora Core 23 which
> is Qt 5.5.1.
>
> I have elected to use any useful Qt features only available later than
> Qt 5.2 inside #ifdef blocks so that the LTS Ubuntu users are able to build.
>
> So basically we are currently requiring Qt 5.2.1 and support building
> with up Qt 5.5. I haven't tried Qt 5.6 beta yet but I am aware that
> there is a WindowsXP compatibility issue at present that I expect will
> be fixed before Qt 5.6 is released.
>
> 73
> Bill
> G4WJS.
>
>
> --
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] QT55

[Bill Somerville]

On 31/12/2015 16:54, Michael Black wrote:
> Wanted to add an audio card checkbox & chooser and was going to use 
> QT55 ability to do so on the audio chooser.

Hi Mike,

it is possible to add widgets to the existing layouts from code so you 
don't necessarily have to have the whole UI designed in Designer. 
Obviously some layouts like QGridLayout might be awkward but it should 
still be possible. I assume  this is destined for the Audio tab of the 
Settings, that has a QGridLayout called gridLayout_5 (better to ask the 
tab itself, see below) that you can add a new QGroupBox to with your 
widgets inside, something like:

#if Q_VERISION > 0x050500
 auto your_group_box = new QGroupBox ("Audio Announcements");
 // build group box contents
 if (auto audio_layout = qobject_cast 
(ui_->audio_tab->layout ())) {
   audio_layout->addWidget (your_group_box, 1, 0);
}
#endif

73
Bill
G4WJS.

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Spanish translation

[ea2ekh]

> On 31 Dec 2015, at 15:27, Joe Taylor  wrote:
> 
> Hi Borja,
> 
> 
> If these starting points present no serious obstacles for you, we here 
> on the  email list will happy to help you get started!

Ewword would be a problem, but a markup such as this one or LaTeX is not a 
problem ;)


73, Borja EA2EKH
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JT65 decoder status

[Joe Taylor]

On 12/31/2015 1:09 PM, Guy G4DWV/4X1LT wrote:
> Joe Taylor  writes:
>
> 
>
>> Normal operation at HF should set "Aggressive decoding level" to 0.
>> If you try operating on HF with higher values, be sure to set Ftol=1000.
>>With higher values of Aggressive decoding level you will see a few
>> more decodes, and also some false decodes.
> --
>
> Sri, but where does one change the "Ftol=xxx" setting?
> Mni tnx.
> Best wishes to all here for 2016. Have a happy and healthy year with enough
> spare shekels to spend on ham gear.

Set Mode to JT65 (not JT9+JT65).  The Ftol widget is then made visible.
-- Joe, K1JT

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JT65 decoder status

[Bill Somerville]

On 31/12/2015 19:21, Joe Taylor wrote:
> Set Mode to JT65 (not JT9+JT65).  The Ftol widget is then made visible.
You will need to check "Enable VHF/UHF Features" in "Settings->General" 
as well.

73
Bill
G4WJS.

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JT65 decoder status

[Joe Taylor]

Hi Steve and all,

In case you have built WSJT-X v1.7 from r6329 and used it on the HF 
bands, you'll surely see many more false decodes than usual.  As 
committed, the code uses aggressive values for the parameters d_0 and 
r_0.  These values may be appropriate for EME-like conditions, but 
surely not for HF.

On a trial basis, with r6330 I've introduced a table lookup for limits 
on nhard, d_0, and r_0, using the user-selectable "Aggressive decoding 
level" as the table index.

Here's the table, as implemented in jt65_decode.f90:

Aggr  nhard  d_0r_0
-
0   41710.70
1   42720.72
2   43730.74
3   43740.76
4   44760.78
5   45770.80
6   46780.82
7   47800.84
8   48810.86
9   48820.88
10  49830.90

I changed the early-exit condition in ftrsd2.c to nhard_min <= 41, 
ntotal_min <= 71.

Normal operation at HF should set "Aggressive decoding level" to 0.
If you try operating on HF with higher values, be sure to set Ftol=1000. 
  With higher values of Aggressive decoding level you will see a few 
more decodes, and also some false decodes.

Let me know if you have different ideas about how these parameters might 
best be set, for different operating conditions.

-- Joe

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Spanish translation

[ea2ekh]

> On 31 Dec 2015, at 15:53, Bill Somerville  wrote:
> 
> 
> I would suggest, for now, copying the whole content of the 
> ^/branches/wsjtx/doc/user_guide/ directory including the images. It 
> might be worthwhile for technical reasons to move the current sources 
> down one level into an 'English' directory, I could easily add a loop to 
> the CMake script to generate User Guide documents for a list of 
> languages. If everyone is happy with this approach I can make the 
> necessary changes in a few minutes.

Indeed, it's the best approach.

> For now a basic translation of the User Guide seems a great place to 
> start but anyone taking this on must be prepared to take ownership of 
> the translated files for future releases, there is a lot of new 
> functionality on the way that will also need translating.

No problem with that. Making the first translation is the hardest work, 
updating it later is much lighter.



73, Borja EA2EKH



--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JT65 decoder status

[Guy G4DWV/4X1LT]

Joe Taylor  writes:



> Normal operation at HF should set "Aggressive decoding level" to 0.
> If you try operating on HF with higher values, be sure to set Ftol=1000. 
>   With higher values of Aggressive decoding level you will see a few 
> more decodes, and also some false decodes.
--

Sri, but where does one change the "Ftol=xxx" setting?
Mni tnx.
Best wishes to all here for 2016. Have a happy and healthy year with enough
spare shekels to spend on ham gear.





--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JT65 decoder status

[Bill Somerville]

On 31/12/2015 22:04, Michael Black wrote:
> It seems as though once aggressive decoding is turned on you can't 
> decode JT65 with JT9 any more.  All you get is JT9 decodes in the 
> combo mode.
Hi Mike,

for now that is not unreasonable. Aggressive decoding is intended for 
VHF & up where you will not be using JT9. I believe the settings Joe 
suggested above are for those who want to try the JT65 VHF & up settings 
on EME etc.. There will be false decodes on HF, where many strong 
signals are likely, unless aggression is set to zero.

73
Bill
G4WJS.

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JT65 decoder status

[Bill Somerville]

On 31/12/2015 22:32, Michael Black wrote:
> The it's backwardsif you're only supposed to do JT65 with 
> aggressivebut all you can receive is JT9.
>
> I kind of thought Joe's point was to allow some aggressive decoding on HF.

You can try out the JT65 decoder in aggressive mode on HF if you want, 
that's all he is saying. The JT65 decoder in aggressive mode can only be 
used with a frequency tolerance of 1000Hz, you can only set that if you 
are in JT65 only mode with the VHF & up features enabled.

The background here is that the JT65 decoder has different 
characteristics for EME and HF so that both sets of users get what they 
need. Using it at cross purposes is not the intended usage.

73
Bill
G4WJS.

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JT65 decoder status

[Michael Black]

The it's backwardsif you're only supposed to do JT65 with
aggressivebut all you can receive is JT9.

I kind of thought Joe's point was to allow some aggressive decoding on HF.

RRR
Mike W9MDB

On Thu, Dec 31, 2015 at 4:18 PM, Bill Somerville 
wrote:

> On 31/12/2015 22:04, Michael Black wrote:
> > It seems as though once aggressive decoding is turned on you can't
> > decode JT65 with JT9 any more.  All you get is JT9 decodes in the
> > combo mode.
> Hi Mike,
>
> for now that is not unreasonable. Aggressive decoding is intended for
> VHF & up where you will not be using JT9. I believe the settings Joe
> suggested above are for those who want to try the JT65 VHF & up settings
> on EME etc.. There will be false decodes on HF, where many strong
> signals are likely, unless aggression is set to zero.
>
> 73
> Bill
> G4WJS.
>
>
> --
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JT65 decoder status

[Michael Black]

It seems as though once aggressive decoding is turned on you can't decode
JT65 with JT9 any more.  All you get is JT9 decodes in the combo mode.

RRR
Mike W9MDB

On Thu, Dec 31, 2015 at 1:42 PM, Bill Somerville 
wrote:

> On 31/12/2015 19:21, Joe Taylor wrote:
> > Set Mode to JT65 (not JT9+JT65).  The Ftol widget is then made visible.
> You will need to check "Enable VHF/UHF Features" in "Settings->General"
> as well.
>
> 73
> Bill
> G4WJS.
>
>
> --
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JT65 decoder status

[Molnar, George J]

Confirmed here.

Aggressive decodes set to "1", FTol 1000. Returning Aggressive setting 
to "0" restores function.


6330 under Mac OS X 10.11.3

Geo/KF2T


-- Original Message --
From: "Michael Black" 
To: "WSJT software development" 
Sent: 12/31/2015 2:04:34 PM
Subject: Re: [wsjt-devel] JT65 decoder status

It seems as though once aggressive decoding is turned on you can't 
decode JT65 with JT9 any more.  All you get is JT9 decodes in the combo 
mode.


RRR
Mike W9MDB

On Thu, Dec 31, 2015 at 1:42 PM, Bill Somerville 
 wrote:

On 31/12/2015 19:21, Joe Taylor wrote:
> Set Mode to JT65 (not JT9+JT65).  The Ftol widget is then made 
visible.
You will need to check "Enable VHF/UHF Features" in 
"Settings->General"

as well.

73
Bill
G4WJS.

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JT65 decoder status

[Bill Somerville]

On 31/12/2015 23:09, Michael Black wrote:
> OKcapeeshbut does that mean mode should be forced to JT65 and 
> combo mode disabled?  Perhaps with a dialog box to 'splain things?
Hi Mike,

until it is decided if the aggressive mode is of any use on HF, no. If 
it is not useful i.e. creates false decodes and so few extra good 
decodes that it is not worth the confusion caused; then aggression will 
probably be forced to zero for dual mode operation. If it turns out that 
the aggressive option is useful on HF then the frequency tolerance 
setting or behaviour will need to be changed.

For now, just give it a try in JT65 only mode and decide for yourself 
how useful it is.

73
Bill
G4WJS.

--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JT65 decoder status

[Michael Black]

OKcapeeshbut does that mean mode should be forced to JT65 and combo
mode disabled?  Perhaps with a dialog box to 'splain things?

RRR
Mike W9MDB

On Thu, Dec 31, 2015 at 4:51 PM, Bill Somerville 
wrote:

> On 31/12/2015 22:32, Michael Black wrote:
> > The it's backwardsif you're only supposed to do JT65 with
> > aggressivebut all you can receive is JT9.
> >
> > I kind of thought Joe's point was to allow some aggressive decoding on
> HF.
>
> You can try out the JT65 decoder in aggressive mode on HF if you want,
> that's all he is saying. The JT65 decoder in aggressive mode can only be
> used with a frequency tolerance of 1000Hz, you can only set that if you
> are in JT65 only mode with the VHF & up features enabled.
>
> The background here is that the JT65 decoder has different
> characteristics for EME and HF so that both sets of users get what they
> need. Using it at cross purposes is not the intended usage.
>
> 73
> Bill
> G4WJS.
>
>
> --
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel