Hi David,
Thanks for your view of what the issues are.
The incorrect spot can waste a lot of time when the 6m band is "going" so
minimisation of these false reports would be most helpful. I can also agree
on the process, I have done that many times but it takes a few minutes.
Sometimes a spot is
Andrew,
Thanks for the clear explanation of the problem.
As I and others have said, CAT control is not a guarantee of perfect spots.
Changing bands at the wrong instant can still generate bad info (even
accidentally pressing the wrong button on your rig can do that). Similarly,
impossible/wi
Hi,
To illustrate exactly what the problem is have a look at PSK reporter for
the last 24 hours, use 6m, LU5VV FT8 and 24 hours.
This type of false reporting makes the 6M usage difficult because of the
rare propagation on 6m of long distance contacts. It only takes one set of
false reports like
> In passing one might note that CAT control is not a panacea against bad
> reports.
Exactly! The data is never going to be perfect - there are enough intrinsic bad
decodes even on the correct freq that get reported up.
As any careful data consumer knows, you must clean and curate any dataset
David,
to answer your question, anyone who tries to use the data. Neither you
nor I nor anyone else really knows all the uses to which the data set
may be put in future.
As to whether the data set is more or less useful without CAT mediated
reports, that's quite another question!
In passin
> IMHO the errors cause more of a problem ...
What exact "problem" does a small number of inaccurate spots create? By your
own data, the number of non-CAT users is small, hence the number of inaccurate
spots is proportionally small - who is harmed by a small number of inaccurate
data points? W
Do you really want to preclude those of us that choose to not use CAT control
from reporting spots? That seems like a bit of an extreme solution for such a
small problem.
I would think the benefit of having more spots would help the whole community
more than the harm done by a few misplaced sp
Let's see now.
#1 Those using CAT control -- 100% accurate spot reporting#2 Those not using
CAT control -- a small number, and why do we need their spots when accuracy is,
probably, nowhere close to 100%?
So yes...I do want to prevent those from doing pskreporting. IMHO the errors
cause more of
Here's a one-liner that should prevent psk reports if the rig is "None".
https://www.dropbox.com/s/zb920h4s0puibyn/oktopost.patch?dl=1
de Mike W9MDB
On Thursday, October 26, 2017, 3:32:44 AM CDT, Hasan al-Basri
wrote:
If that was fixed, I missed it! It would be wonderful if that's the
A simple patch to change Enable to yellow during transmit, This makes all 3
indicators (Rx Freq, status, and Enable) agree on color meaning.
https://www.dropbox.com/s/npik2sqeyywskf1/enable.patch?dl=1
de Mike W9MDB
--
A simple patch to change Enable to yellow during transmit, This makes all 3
indicators (Rx Freq, status, and Enable) agree on color meaning.
https://www.dropbox.com/s/npik2sqeyywskf1/enable.patch?dl=1
de Mike W9MDB
--
If that was fixed, I missed it! It would be wonderful if that's the case.
I'll have to watch for it. Tnx tip
73, N0AN
Hasan
On Wed, Oct 25, 2017 at 9:17 PM, Gary McDuffie wrote:
>
>
> > On Oct 25, 2017, at 7:51 PM, Hasan al-Basri
> wrote:
> >
> > A radio connection does not prevent false repo
12 matches
Mail list logo
