w4kek/WSJT-X
1
0
Fork 0
mirror of https://github.com/saitohirga/WSJT-X.git synced 2026-06-03 14:34:41 -04:00
Code Issues Packages Projects Releases Wiki Activity

Updates to Release Notes and User Guide.

Browse Source
This commit is contained in:
Joe Taylor
2020-05-05 14:11:54 -04:00
parent 27b94e2cc7
commit 4077526d88
11 changed files with 138 additions and 51 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/user_guide/en/decoder_notes.adoc
+9 -9
View File
@@ -1,10 +1,10 @@
=== AP Decoding
The _WSJT-X_ decoders for JT65, QRA64, and FT8 include optional
procedures that use naturally accumulating information during a
minimal QSO. This _a priori_ (AP) information increases sensitivity
of the decoder by up to 4 dB, at the cost of a slightly higher rate of
false decodes.
The _WSJT-X_ decoders for FT4, FT8, JT65, and QRA64 include optional
procedures that take advantage of naturally accumulating information
during a minimal QSO. This _a priori_ (AP) information increases
sensitivity of the decoder by up to 4 dB, at the cost of a slightly
higher rate of false decodes.
For example: when you decide to answer a CQ, you already know your own
callsign and that of your potential QSO partner. The software
@@ -12,7 +12,7 @@ therefore "`knows`" what might be expected for at least 57 message
bits (28 for each of two callsigns, 1 or more for message type) in the
next received message. The decoder's task can thus be reduced to
determining the remaining 15 bits of the message and ensuring that the
resulting solution is reliable.
resulting solution is consistent with the message's parity symbols.
AP decoding starts by setting AP bits to the hypothesized values, as
if they had been received correctly. We then determine whether the
@@ -20,11 +20,11 @@ remaining message and parity bits are consistent with the hypothesized
AP bits, with a specified level of confidence. Successful AP decodes
are labeled with an end-of-line indicator of the form `aP`, where `P`
is one of the single-digit AP decoding types listed in Table 1. For
example, `a2` indicates that the successful decode used MyCall as
example, `a2` indicates that the successful decode used *MyCall* as
hypothetically known information.
[[FT8_AP_INFO_TABLE]]
.FT8 AP information types
.FT4 and FT8 AP information types
[width="35%",cols="h10,<m20",frame=topbot,options="header"]
|===============================================
|aP | Message components
@@ -47,7 +47,7 @@ _WSJT-X_ auto-sequencer, along with the type of AP decoding that would
be attempted in each state.
[[FT8_AP_DECODING_TYPES_TABLE]]
.FT8 AP decoding types for each QSO state
.FT4 and FT8 AP decoding types for each QSO state
[width="35%",cols="h10,<m20",frame=topbot,options="header"]
|===========================================
|State |AP type