Has it been considered to replace the use of shell.f90 (a shellsort) that
fully sorts before finding the kth element? The quickselect algorithm is
much faster as it does only a partial partitioning of the data to find the
kth element.
Jim Record
*AD0YO*
On 12/13/2017 23:29, Black Michael via wsjt-devel wrote:
Along with the below to fix any perl errors you see building hamlib
I found the culprit.
For the moment edit \JTSDK\hamlib3-qt55\lib\pkgconfig\hamlib.pc
Remove the libusb entry on the "Requires.private:" line. Leave the Requries
Bill,
Thank you so much for that advice! I shut off the CI-V transceive setting
and radio is now going through TX-RX cycles without any problems, even
with power set to a finite value. I don't know why that setting was set to
on in my radio - maybe that is the default value; I haven't used that
On 20/12/2017 13:43, Lou Crocker wrote:
Observations:
On selecting Enable Tx in Echo mode, the program keys the rig
repeatedly as expected for several cycles, perhaps from 10 s to a
minute. Then one of three things happens: 1) the program stops
transmittting without an error message, 2) the
Thank you for the suggestion. I do have a powered USB 3.0 hub., I just
tried it and I see the same behavior ("Bus collision...").
I don't have an ethernet cable - just a wifi card in the computer. I just
tested the radio plugging it into a front USB port away from the wifi card,
but I observe the
Sounds like USB power problems to me.
Do you have a powered USB hub you could hook up and test?Can you also unplug
your ethernet and see if that makes any difference? That's just a quick/easy
test to hopefully eliminate that cabling as the problem.
de Mike W9MDB
On Wednesday, December
I know a lot of tweaks have been made to hamlib since the last official
release to work with WSJT-X which means for now I'm using the superbuild
script which builds a bundled checkout of hamlib.
That's pretty much the only thing keeping me from getting WSJT-X into
Fedora proper.
I can ask on the
Hello,
I have observed what appears to be a computer-rig communication error on
transmit. I have observed this when either using Tune or in Echo mode - I
am just setting this system up so I have spent little time transmitting in
other modes (the rig worked fine during one QSO at HF).
Hi Peter,
Unfortunately, take-up and use of WSJT-X by VK and ZL VHF operators --
at least by those who report back to us -- was rather slow during the
"candidate release" periods of v1.8.0-rc1 and -rc2. We can't fix what
we don't know is broken.
The first we heard of this problem was 10
