Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

[Joe Taylor]

Hi Bill and Greg,

Thanks for looking into the font-rendering issue I raised.

> https://dl.dropboxusercontent.com/u/4192709/wsjtx-main.html

With default settings my browsers display your html file very nicely. 
I'd say the 90% setting is an improvement.

To my eyes, the pdf file you posted here
> https://dl.dropboxusercontent.com/u/4192709/wsjtx-main.pdf
has two problems.  The text font is too small, and the margins are too 
big.  I don't consider making a pretty pdf a high priority, however.

> I envisage generating a PDF version of the User Guide for access from
> the project web site rather then shipping it with the application.

If we do a pdf at all, I agree.

-- Joe


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

[wsjt-devel] wspr-15

[Richard Bown]

Hi all
I was asked by a friend who uses wspr-15 on LF about wsjtx
I see on the menu its greyed out, what the position on this mode ?
is it work in progress or have I missed a s/w switch for it ?
Thanks


-- 
-- 
Best wishes /73 
Richard Bown

Email : rich...@g8jvm.com
HTTP  :  http://www.g8jvm.com
nil carborundum a illegitemis
##
Ham Call: G8JVM . QRV: 50-432 MHz + Microwave 23 cms 140W, 13 cms 100W & 3cms 5W
Maidenhead QRA: IO82SP38, LAT. 52 39.720' N LONG. 2 28.171 W
QRV VHF 6mtrs 200W, 4 mtrs 150W, 2mtrs 400W, 70cms 200W
OS: Linux Mint 17.2 x86_64 on a Dell Inspiron N5030 laptop
##
 


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

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

[Bill Somerville]

On 19/11/2015 22:07, Greg Beam wrote:
> If we're not going to ship a PDF with the package, Asccidoctor has a
> module that can be installed via gem to generate PDF's. It's
> implementation is not 100% yet, but it's working for v1.7.0. This
> "should" also work for the v1.6.0-RC version.
>
> To install / test:
>
> * open JTSDK-QT
> gem install --pre asciidoctor-pdf
Hi Greg,

I did have a look at asciidoctor-pdf but its pre-relaease status and the 
fact that it will not install on Ubuntu 14.04 LTS since it has a 
dependency on Ruby 2.0 (via prawn 2.0.2) so it gets messy very quickly.

The asciidoctor-fopub utility is not in the repos at all which makes it 
a bit simpler although it requires both a Java JRE and JDK. Obviously 
not very useful for package building but if I make the WSJT-X CMake PDF 
generation silently fail if the tool is not available, it can at least 
be used to generate a PDF when needed.

The fopub tool uses FOP so has all the FO parameters available for 
tweaking the PDF generation and does seem to work very well.

73
Bill
G4WJS.

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

[wsjt-devel] timecmd error on comma

[Alessandro Gorobey]

Hi All,

only for information.

Script C:\JTSDK\scripts\timecmd.cmd give me errors so a write a small c 
program.
Analyzing it I found the problem.
Simply on my PC echo %time% give 11:13:35,12 (note the comma)
Changing
set options="tokens=1-4 delims=:."
to
set options="tokens=1-4 delims=:.,"
the script work also on locales where separator is comma.

73
Sandro
IW3RAB

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

Re: [wsjt-devel] WSJT-X 1.6 rc Hamlib3 Question

[Bill Somerville]

On 19/11/2015 23:47, Jim Bennett wrote:
Hi - I downloaded and installed v 1.6 RC1 from Joe's site. Got the 
installation done on Ubuntu Linux v14.0 with a little (OK, a lot) of 
help from Greg KI7MT. My radio is a SoftRock Ensemble RXTX. If I 
select Softrock from the drop down list of radios it fails and tells 
me Rig Failure / Unsupported CAT Type. Need to know if my rig is 
supported inHamlib3.


Thanks, Jim / W6JHB

Hi Jim,

are you using HDSDR? If so, is there an option to emulate a TS-2000 for 
CAT control?


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

Re: [wsjt-devel] WSJT-X: *Important* - please read if you build WSJT-X from source

[Alessandro Gorobey]

Hi Bill and Greg

from tread I understand that if there is no local modifications simply 
remove source and build directories. Start from zero by script.
I do that from QT55 and compiling wsjtx rc2 and develop.
I obtain the errors that Bill have solved in September 2014 with tune 
button, split etc.
ERR--> Rig split mode setting not consistent with WSJT-X settings.

With with qt55-disable return to QT5.
This hamlib3 are compiled in august 2015
Compile the some programs and all work well.

Rig is Yaesu 857.
The follow is rigctl on the two libs, and differ in revision.
**
(JTSDK-QT 5.5 ) C:\JTSDK\hamlib3-qt55\bin)rigctl -vv
rigctl, Hamlib 3.1~git
Report bugs to 

rig:rig_init called
dummy: _init called
rig_register (1)
rig_register (2)
dummy_init called
rig:rig_open called
dummy_open called
dummy_get_vfo called: VFOA
Opened rig model 1, 'Dummy'
Backend version: 0.5, Status: Beta
*
(JTSDK-QT 5.2 ) C:\JTSDK\hamlib3\bin)rigctl -v
rigctl, Hamlib 3.0~git
Report bugs to 

rig:rig_init called
dummy: _init called
rig_register (1)
rig_register (2)
dummy_init called
rig:rig_open called
dummy_open called
dummy_get_vfo called: VFOA
Opened rig model 1, 'Dummy'
Backend version: 0.5, Status: Beta
***

What do you advise me to do ?

73
Sandro
IW3RAB


Il 18/11/2015 20:31, Bill Somerville ha scritto:
> On 18/11/2015 19:29, Greg Beam wrote:
>> Note: On my box, I had nothing to save / stash, spo Git gave me two
>> messages stating as such.
> That's fine, I only added those in case anyone had local changes such
> that they would not be lost by the hard reset.
>
> 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] wspr-15

[Richard Bown]

On Fri, 20 Nov 2015 11:52:10 -0500
Joe Taylor  wrote:

> Up to now WSPR-15 has not been implemented in any version of WSJT-X.  If 
> there is sufficient interest, this capability could be added to some 
> future release.
> 
>   -- Joe, K1JT


Hi Joe

apparently its quite popular on the LF bands , not that I use them Joe, I tend 
to stay on bands
where the minimum usable antenna gain is 10dB.



> 
> On 11/20/2015 9:49 AM, Richard Bown wrote:
> > Hi all
> > I was asked by a friend who uses wspr-15 on LF about wsjtx
> > I see on the menu its greyed out, what the position on this mode ?
> > is it work in progress or have I missed a s/w switch for it ?
> > Thanks
> >
> >
> 
> --
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel



-- 
-- 
Best wishes /73 
Richard Bown

Email : rich...@g8jvm.com
HTTP  :  http://www.g8jvm.com
nil carborundum a illegitemis
##
Ham Call: G8JVM . QRV: 50-432 MHz + Microwave 23 cms 140W, 13 cms 100W & 3cms 5W
Maidenhead QRA: IO82SP38, LAT. 52 39.720' N LONG. 2 28.171 W
QRV VHF 6mtrs 200W, 4 mtrs 150W, 2mtrs 400W, 70cms 200W
OS: Linux Mint 17.2 x86_64 on a Dell Inspiron N5030 laptop
##
 


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

Re: [wsjt-devel] WSJT-X: *Important* - please read if you build WSJT-X from source

[Bill Somerville]

On 20/11/2015 16:50, Alessandro Gorobey wrote:
> from tread I understand that if there is no local modifications simply
> remove source and build directories.
Hi Sandro,

yes that is fine if a little slower.

73
Bill
G4WJS.

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

Re: [wsjt-devel] WSJT-X: *Important* - please read if you build WSJT-X from source

[Bill Somerville]

On 20/11/2015 16:50, Alessandro Gorobey wrote:
> I do that from QT55 and compiling wsjtx rc2 and develop.
> I obtain the errors that Bill have solved in September 2014 with tune
> button, split etc.
> ERR--> Rig split mode setting not consistent with WSJT-X settings.
>
> With with qt55-disable return to QT5.
> This hamlib3 are compiled in august 2015
> Compile the some programs and all work well.
>
> Rig is Yaesu 857.
Hi Sandro,

for the FT-817/857/897 I have removed the "advanced" Hamlib rig driver 
we have been using for these rigs. This is unfortunate but is forced on 
us by circumstances out of our control. The background is that these 
rigs have quite limited CAT control command sets but also have an 
extensive undocumented CAT capability, the "advanced" driver makes use 
of these undocumented capabilities. Recently Yaesu contacted the HRD 
developers asking them to remove similar capabilities from HRD which 
they complied with. The concern from Yaesu is that these capabilities 
use an undocumented CAT command that writes directly to rig's EEPROM 
memory and the memory device used by Yaesu is passed end of life and is 
no longer obtainable. The "advanced" Hamlib driver I wrote has never 
been submitted upstream to the Hamlib team, it takes extreme measures to 
minimize writes to EEPROM so as to reduce wear on the memory device 
which I believe limits writes to no more than would be made by the rig 
itself in normal operation and we have had no reports of device failures 
due to WSJT-X. Nevertheless it seems prudent to pre-empt any issues by 
withdrawing the "advanced" driver from WSJT-X.

73
Bill
G4WJS.

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

Re: [wsjt-devel] WSJT-X 1.7.0-devel r6131

[Bill Somerville]

On 20/11/2015 17:39, Cedric wrote:
> I just got a -29dB JT65 decode. I wonder if it's really possible?
Hi Cedric,

it is certainly possible although the development branch contains a lot 
of new code in this area and it is quite possible that the SNR figure 
from the deepest JT65 decodes is not yet accurately calibrated.

73
Bill
G4WJS.

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

[wsjt-devel] Mode display on WSJT-X 1.6.1 r6010

[Charles Suckling]

Hi All

I have been using Echo mode this evening, switching between JT4 and Echo and
notice that mode displayed on bottom of Main window shows last set JT4 mode,
not Echo when Echo is selected.

Same observation if program is closed from Echo and restarted (ie mode shown
as JT4x).

73

Charlie G3WDG

-Original Message-
From: KI7MT [mailto:ki...@yahoo.com] 
Sent: 20 November 2015 18:33
To: WSJT software development
Subject: Re: [wsjt-devel] timecmd error on comma

Hi Sandro,

Thanks for the catch. This is added to SVN and will make it into the
next update.

73's
Greg, KI

On 11/20/2015 03:19 AM, Alessandro Gorobey wrote:
> Hi All,
> 
> only for information.
> 
> Script C:\JTSDK\scripts\timecmd.cmd give me errors so a write a small c 
> program.
> Analyzing it I found the problem.
> Simply on my PC echo %time% give 11:13:35,12 (note the comma)
> Changing
> set options="tokens=1-4 delims=:."
> to
> set options="tokens=1-4 delims=:.,"
> the script work also on locales where separator is comma.
> 
> 73
> Sandro
> IW3RAB


--
___
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] WSJT-X 1.6 rc Hamlib3 Question

[Jim Bennett]

Michael,
Here is that output report:
w6jhb@ubuntu:~$ rigctl -v -m 2509
rigctl, Hamlib 1.2.15.3
Report bugs to 

rig:rig_init called 
rig: loading backend kit
kit: _init called
rig_register (2501)
rig_register (2502)
rig_register (2506)
rig_register (2508)
rig_register (2514)
rig_register (2509)
rig_register (2511)
rig_register (2513)
rig_register (2512)
rig_register (2503)
rig_register (2507)
rig:rig_open called 
find_and_open_device: looking for device 16c0:05dc...usb_set_debug: Setting 
debugging level to 4 (on)
 08bb:29b0, 16c0:05dc, vendor >www.obdev.at< product >DG8SAQ-I2C< -> found
USB error: could not get bound driver: No data available
si570xxxusb_open called
si570xxxusb_open: detected PE0FKO-like firmware
si570xxxusb_open: using Xtall at 114.278 MHz
Opened rig model 2509, 'Si570 AVR-USB'
Backend version: 0.2, Status: Beta

Rig command: ^C
w6jhb@ubuntu:~$ 

 

 From: Michael Hartje 
 To: w6jh...@yahoo.com 
 Sent: Thursday, November 19, 2015 11:32 PM
 Subject: WSJT-X 1.6 rc Hamlib3 Question
   
Hello Jim

The output of rigctl -v shows: you did not gave a model number; the 
default is selected instead

for softrock please try

rigctl -v -m 2509

BTW, hopefully, your user account  is member of the group dialout?
(try command groups)

vy73
Michael
DK5HH



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

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

[KI7MT]

Hi Bill,

See below.

On 11/20/2015 05:55 AM, Bill Somerville wrote:
> On 19/11/2015 22:07, Greg Beam wrote:
>> If we're not going to ship a PDF with the package, Asccidoctor has a
>> module that can be installed via gem to generate PDF's. It's
>> implementation is not 100% yet, but it's working for v1.7.0. This
>> "should" also work for the v1.6.0-RC version.
>>
>> To install / test:
>>
>> * open JTSDK-QT
>> gem install --pre asciidoctor-pdf
> Hi Greg,
> 
> I did have a look at asciidoctor-pdf but its pre-relaease status and the 
> fact that it will not install on Ubuntu 14.04 LTS since it has a 
> dependency on Ruby 2.0 (via prawn 2.0.2) so it gets messy very quickly.

Yes, I apologize, I should have stated "On Windows", as 14.04 has Ruby
1.9.3 and prawn requires 2.0.2.

That's why In stated if we're not going to Ship the PDF with the package.

Vivid and above is OK.

> 
> The asciidoctor-fopub utility is not in the repos at all which makes it 
> a bit simpler although it requires both a Java JRE and JDK. Obviously 
> not very useful for package building but if I make the WSJT-X CMake PDF 
> generation silently fail if the tool is not available, it can at least 
> be used to generate a PDF when needed.
> 
> The fopub tool uses FOP so has all the FO parameters available for 
> tweaking the PDF generation and does seem to work very well.


As you stated, if PDF generation is going to become the standard,
DocBook is ( IMHO ) a much better way forward. If that's the case, we to
re-look at a few things as the way we've set up the user guide ( as an
Article) rather than a book is is not ideal for creating PDF's properly.

> 
> 73
> Bill
> G4WJS.
> 

73's
Greg, KI7MT

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

Re: [wsjt-devel] WSJT-X 1.6 rc Hamlib3 Question

[Bill Somerville]

On 20/11/2015 17:06, Jim Bennett wrote:
> Here is that output report:
>
> w6jhb@ubuntu:~$ rigctl -v -m 2509
> rigctl, Hamlib 1.2.15.3
...
> si570xxxusb_open called
> si570xxxusb_open: detected PE0FKO-like firmware
> si570xxxusb_open: using Xtall at 114.278 MHz
> Opened rig model 2509, 'Si570 AVR-USB'
> Backend version: 0.2, Status: Beta
>
> Rig command:
Do you get the same output when using 'rigctl-wsjtx'?

73
Bill
G4WJS.

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

Re: [wsjt-devel] WSJT-X 1.7.0-devel r6131

[Michael Black]

Well hopefully they aren't political numbers :-)

Here's a plot of the db levels I've seen for JT65.  This is 1M rows from my
ALL.TXT and you can see the apparent improvements lately with the larger
group of -26, -27 and -28 decodes.And there are a few -30 decodes too.  But
only 1 before just recently.

histogram-wise I show:
-30 7
-29 15
-28 57
-27 167
-26 520
-25 1267
-24 3146
-23 6592
-22 12491
-21 21449
-20 31833
The rest ardoun around 4 until -1 which has 237,892 entries.

If you want to generate your own you can use the JTSDK tools grep, cut and
sort
For JT65
grep "#" ALL.TXT | cut -c6-8 >time.txt

sort time.csv | uniq -c >timeu.txt
That will give you a complete histogram of what you've seen.
I did some comparisons with a club member which prompted me to get a Pixel
Pro 1B which bumped up my receive level by 7dB

This is since Sep 2014.

​73
Mike W9MDB


On Fri, Nov 20, 2015 at 11:42 AM, Bill Somerville 
wrote:

> On 20/11/2015 17:39, Cedric wrote:
> > I just got a -29dB JT65 decode. I wonder if it's really possible?
> Hi Cedric,
>
> it is certainly possible although the development branch contains a lot
> of new code in this area and it is quite possible that the SNR figure
> from the deepest JT65 decodes is not yet accurately calibrated.
>
> 73
> Bill
> G4WJS.
>
>
> --
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


This
email has been sent from a virus-free computer protected by Avast.
www.avast.com

<#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X 1.7.0-devel r6131

[Joe Taylor]

Any measurement has an associated uncertainty.  More precisely, for any 
measurement there is a probability distribution of "true" values that 
might have given rise to the measured value.  Seeing an occasional 
measured value of -29 dB is nothing to be concerned about.

-- Joe

On 11/20/2015 12:39 PM, Cedric wrote:
> I just got a -29dB JT65 decode. I wonder if it's really possible?
>
> 73, Cedric HB9HFN
>
>
>
>
>
> --
>
>
>
> ___
> 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

[wsjt-devel] WSJT-X 1.7.0-devel r6131

[Cedric]

I just got a -29dB JT65 decode. I wonder if it's really possible?

73, Cedric HB9HFN


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

Re: [wsjt-devel] timecmd error on comma

[KI7MT]

Hi Sandro,

Thanks for the catch. This is added to SVN and will make it into the
next update.

73's
Greg, KI

On 11/20/2015 03:19 AM, Alessandro Gorobey wrote:
> Hi All,
> 
> only for information.
> 
> Script C:\JTSDK\scripts\timecmd.cmd give me errors so a write a small c 
> program.
> Analyzing it I found the problem.
> Simply on my PC echo %time% give 11:13:35,12 (note the comma)
> Changing
> set options="tokens=1-4 delims=:."
> to
> set options="tokens=1-4 delims=:.,"
> the script work also on locales where separator is comma.
> 
> 73
> Sandro
> IW3RAB

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

Re: [wsjt-devel] JT65A Decoding Comparison

[Joe Taylor]

Hi Steve and all,

I've added what I hope is a reasonable EME fading model to the simulated 
data files produced by jt65sim.  The fading characteristic is defined by 
a specified amount of "Doppler spread" (in Hz) applied to the simulated 
signal.  Typical Doppler spreads on popular EME bands are something like 
those in the following table.  (See, for example, Fig 9 of 
http://physics.princeton.edu/pulsar/K1JT/EME2010_K1JT.pdf.)


Band   Doppler
   Spread
(MHz)(Hz)
---
50   0.1
144  0.3
432   1
1296  4
2.3G  8
3.4G 12
5.7G 20
10G  60
24G 170

Doppler spread also occurs for ionospheric propagation at HF, with 
typical values of several tenths of a Hertz.


Anyway... Using this feature in jt65sim, I have compared sensitivities 
of the sfrsd decoder to JT65A signals with 0, 0.3, and 1.0 Hz of Doppler 
spread on the signals.  Results are shown in the attached plot.  With an 
eye toward EME use on UHF and microwave bands, I plan to make similar 
tests for submodes JT65B and JT65C with larger values of Doppler spread.


For future reference, here's a list of things that I think still need to 
be done to the v1.7 JT65 decoder:


1. Decode first at the selected Rx frequency, then across the whole
   passband.  (This is already done for JT9, and in previous versions
   was done also for JT65.)

2. Optional "single decode" behavior (as opposed to multi-decode over
   the full passband)

3. Optimizations of submodes B and C

4. Implement message averaging

5. Implement correlation ("experience-based") decoding

Items 2-5 will be useful mostly at VHF and above.

Have I forgotten anything important here?

-- Joe, K1JT


JT65A__with_Doppler_spread.pdf
Description: Adobe PDF document
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] JT65A Decoding Comparison

[Joe Taylor]

Hi Rex,

Thanks for the reminders!  Your item 6 is included in my item 3 
("Optimizations of submodes B and C).  I agree that the degradation 
facility can be useful; I'll put that on the list.  Also maybe JT65D 
(and even JT65E?) ? I'll think more about these.

-- Joe

On 11/20/2015 2:57 PM, Rex Moncur wrote:
> Hi Joe
>
> If you can fit them in while you are doing it can you:
>
> 6. Add variable bin-width decoding to JT65a, b and c like on JT4
> 7. Add JT65d and possibly JT65e
> 8. The degradation decoding facility in WSJT10 which is useful to establish
> how much we have in reserve.
>
> I think these will be very useful for 10 and 24 GHz tropo-scatter where the
> spreading can be up to 20 Hz or as low as 1 Hz when a duct is present and
> sometimes we see combinations of both with a tropo-scatter extension of a
> duct.
>
> The JT65e mode will be mainly for small station to small station EME at 10
> GHz when the spreading is very low.
>
> 73 Rex VK7MO
>
>
>
> --
> ___
> 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] JT65A Decoding Comparison

[Rex Moncur]

Hi Joe

If you can fit them in while you are doing it can you:

6. Add variable bin-width decoding to JT65a, b and c like on JT4
7. Add JT65d and possibly JT65e
8. The degradation decoding facility in WSJT10 which is useful to establish
how much we have in reserve.

I think these will be very useful for 10 and 24 GHz tropo-scatter where the
spreading can be up to 20 Hz or as low as 1 Hz when a duct is present and
sometimes we see combinations of both with a tropo-scatter extension of a
duct. 

The JT65e mode will be mainly for small station to small station EME at 10
GHz when the spreading is very low.

73 Rex VK7MO



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

Re: [wsjt-devel] JT65A Decoding Comparison

[Rex Moncur]

Hi Joe

I guess the issue with JT65E is whether it is better to focus small station
to small station EME at 10 and 24 GHz on wide bin-width JT9, also with
variable bin-width decoding. JT9 will allow wider spreading with standard
SSB pass bands.  JT9 should be better for single line decodes with more
energy on the message but probably not useful for averaging.  However, with
QSB there might be little in it either way and a focus on JT9 might be the
best way to go for all microwave EME.

Rex

-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu] 
Sent: Saturday, 21 November 2015 7:45 AM
To: WSJT software development
Subject: Re: [wsjt-devel] JT65A Decoding Comparison

Hi Rex,

Thanks for the reminders!  Your item 6 is included in my item 3
("Optimizations of submodes B and C).  I agree that the degradation facility
can be useful; I'll put that on the list.  Also maybe JT65D (and even
JT65E?) ? I'll think more about these.

-- Joe




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

Re: [wsjt-devel] WSJT-X 1.7.0 dev

[David]

Hi Bill.thanks ...i thought as much...the new decoder works well here
will keep trialling it.

73David VK4BDJ

On 21/11/15 07:18, Bill Somerville wrote:
> On 20/11/2015 21:15, David wrote:
>> does the WSJT-X 1.7.0-devlop v 1641 use kvasd or the newer decoder
>> that has been worked on for a while
> Hi David,
>
> the development branch no longer references KVASD.
>
> 73
> Bill
> G4WJS.
>
> --
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>

-- 
73 David VK4BDJ

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

Re: [wsjt-devel] WSJT-X 1.7.0 dev

[Bill Somerville]

On 20/11/2015 21:15, David wrote:
> does the WSJT-X 1.7.0-devlop v 1641 use kvasd or the newer decoder
> that has been worked on for a while
Hi David,

the development branch no longer references KVASD.

73
Bill
G4WJS.

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

[wsjt-devel] WSJT-X 1.7.0 dev

[David]

Hidoes the WSJT-X 1.7.0-devlop v 1641 use kvasd or the newer decoder 
that has been worked on for a while..as im using a vertical and 
signals are fairly weak here if the new decoder is being used it will 
give me some comparison to work by

-- 
73 David VK4BDJ

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

Re: [wsjt-devel] WSJT-X 1.7.0 dev

[Greg Beam]

FWIW:

I don't have / use anything other than verticals, or simple wire 
dipoles, I never have done (ever). It's not easy working big pile-ups 
like the current S79 or VK9 dxe's, but I get there in the end.

The new decoder in v1.7.0 is working FB for me here in MT.

73's
Greg, KI7MT

On 11/20/2015 14:15, David wrote:
> Hidoes the WSJT-X 1.7.0-devlop v 1641 use kvasd or the newer decoder
> that has been worked on for a while..as im using a vertical and
> signals are fairly weak here if the new decoder is being used it will
> give me some comparison to work by
>

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

[wsjt-devel] wsjtx 1.6.0rc1

[Josh Rovero]

After installing rc1 on my Windows 7 box, I find that
it will not talk to HDSDR via hamlib 3.0 -- hamlib times
out.

Any special secrets to resolve this?

-- 
P.J. "Josh" Rovero http://www.roveroresearch.org
Ham Radio: KK1D http://www.roveroresearch.
net
http://www.roveroresearch.info
--
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjtx 1.6.0rc1

[Bill Somerville]

On 20/11/2015 23:54, Josh Rovero wrote:

After installing rc1 on my Windows 7 box, I find that
it will not talk to HDSDR via hamlib 3.0 -- hamlib times
out.

Any special secrets to resolve this?

--
P.J. "Josh" Rovero http://www.roveroresearch.org
Ham Radio: KK1D http://www.roveroresearch. 
net

http://www.roveroresearch.info

Hi Josh,

what version of WSJT-X were you using before and what settings do you 
have on the "Settings->Radio" panel?


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

Re: [wsjt-devel] [UPDATE] - Migration from AsciiDoc to Asciidoctor -Approved

[Bill Somerville]

On 20/11/2015 15:17, Joe Taylor wrote:

Hi Joe,

...
>
>> https://dl.dropboxusercontent.com/u/4192709/wsjtx-main.html
> With default settings my browsers display your html file very nicely.
> I'd say the 90% setting is an improvement.
OK, I will commit that change.
>
> To my eyes, the pdf file you posted here
>> https://dl.dropboxusercontent.com/u/4192709/wsjtx-main.pdf
> has two problems.  The text font is too small, and the margins are too
> big.  I don't consider making a pretty pdf a high priority, however.
I have tweaked the PDF generation and switched to using some nice free 
to use fonts (Google Noto) if they are available. Results are here:

https://dl.dropboxusercontent.com/u/4192709/wsjtx-main%20%28USLetter%29.pdf

and for an A4 paper size:

https://dl.dropboxusercontent.com/u/4192709/wsjtx-main%20%28A4%29.pdf

I had to swap a couple of text vs. image orderings to get more sensible 
page breaks. Having an image after a section title then putting the lead 
para after the image generally works best because the heading is kept 
with the first element i.e. the image, which avoids an ugly orphaning 
the image on a new page when the lead para is short.
>
>> I envisage generating a PDF version of the User Guide for access from
>> the project web site rather then shipping it with the application.
> If we do a pdf at all, I agree.
I will commit the changes to generate the PDFs, they are benign for 
anyone who does not have the tools installed.
>
>   -- Joe
73
Bill
G4WJS.

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