On 12/04/2017 17:13, Black Michael wrote:
Should we be able to compress this kind of call?
KA1ABC/1 WB9XYZ/1
In r7634 it comes back truncated to 13 chars free text.
KA1ABC/1 WB9X
And this should be compressible too?
W1/KA1ABC WB9XYZ EM49
Isn't the idea that a prefix/suffix is just an "add" to the code word?
Hi Mike,
it is better to view the code word as partitioned into three. Two parts
(28 bit) have a domain big enough to store a base callsign each adhering
to the "standard" callsign format. A handful of spare values are
reserved for CQ, QRZ, DE, CQ NNN, ... . The third part (15 bit) is used
for the grid, unused values are allocated other purposes like slots to
store RO, OOO, 73, report, type 2 prefix or suffix.
You can't "add" to the overall codeword. Neither can you "add" to the
callsign parts as they are dense and the addition is likely to be
another base callsign. The type 2 prefixes and suffixes and the other
suffixes (P, 1-9 and A) are placed in the grid part of the codeword and
only one is stored for one of the callsigns.
Type 1 compound calls can only be used in messages where one callsign
slot has been used for CQ, QRZ, DE, CQ NNN, ... not when both callsign
slots hold actual callsigns. I think this is what you re referring to as
an "add" to the codeword, it is a more restricted case than you imply as
it is using space in a virtually empty domain.
Free text messages use half the codeword space by having one bit
distinguish them from standard messages.
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
