Joe,
Sounds good. Regarding tuning the sfrsd2 erasure probabilities for the HF use
case, I played around with that some and I reached the conclusion that we
should tune the algorithm using statistics derived from vectors that required
soft-symbol decoding (as opposed to using the bulk of our da
Hi STeve,
I think I understand what's going on with the less-than-perfect
selection of candidate frequencies at which to attempt JT65 decoding. I
hope to spend some time on it in the next couple of days. If I don't
get it sorted out then, it may be delayed for about a week. I'll be
away bet
In due course we'll probably change this behavior to something more
"tidy"; we just have had other higher-priority items to work on, in
recent weeks.
-- Joe, K1JT
On 10/5/2015 11:33 AM, Mark Turner wrote:
> As Joe says, that is the normal behaviour of the program.
>
> It does seem to be
... and it is not according to the Region 1 procedure, in which it
specifically sattes that only one report is to be given.
Best 73
Franz (OE3FVU / PE0WGA)
144MHz DX stations meet at www.on4kst.com
-Original Message-
From: Mark Turner [mailto:ei...@yahoo.com]
Sent: Monday, October 5, 2
As Joe says, that is the normal behaviour of the program.
It does seem to be rather unusual though - under normal circumstances,
once one starts sending a report it's generally considered "bad form" to
change it. It's currently quite possible that many different reports
could be received by one
Yes, that is normal behavior.
On 10/5/2015 2:46 AM, Paolo Petrini wrote:
>
> Hello!
>
> Yesterday during a meteor scatter QSO I noticed that the report which is
> automatically sent is changing every time a new burst is arriving. is it
> normal?
> Paolo
>
-
